The use of xlmwrite inside the campbell_diagram_data function to generate the excel sheet is not working on Mac OS. xlmwrite function works for Windows OS and may be Linux OS. Instead writetable function can be used but the cell data should be first converted to table data. I think this problem can be avoided if a flag is used to check OS type and accordingly call appropriate function, either xlmwrite or writetable, to write the excel sheet.

The function CampbellMatchModeNames which is called in runCampbell script is not defined. The code to this function is not committed to the repository.

Hi,

I've been trying to generate the Campbell Diagram for the IEA3.4MW turbine.

The Excel files generated by campbell_diagram_data.m are not compatible with the Plot_CampbellData.m function, nor do they match the format described in Plot_CampbellData.m.

Should the Excel which is an input to Plot_CampbellData.m function be manually generated?

Thank you

Hello everybody,

Trust that everyone is doing well. Thank you in advance for any feedback that you provide me on this issue.

We trying to convert some V7 files to V8 but have come across this 'unrecognized field name "BldPropHdr"' error which we can't quite get past (see attached).

Is anyone familiar with this BldPropHdr?

Thank you all again.

Olivier Maudhuit

The clone link (git clone https://github.com/OpenFAST/MATLAB-mbc) provided in the documentation does not work. I think this should be changed to git clone https://github.com/OpenFAST/matlab-toolbox

Hello, I would like to simulate a damage scenario by reducing the stiffness of one of the blades in the middle of a running simulation. How feasible that is?

Dear openfast team, 
I am facing some issues with the MATLAB-toolbox for Campbell diagram. As I am completely new to this field, these issues may be superficial. Any guidance would be really helpful .

I want to see the frequency and damping of  blade without other parts of wind turbine at different wind speeds (roter speed is always 0).To do this, I set FlapDOF1=True,FlapDOF2=True, EdgeDOF=True with no other DOFs and rotor speed is always 0. Are these Settings feasible?

Another follow-up question. When I set only one blade(NumBl=1), I get some warnings from the "fx_mbc3()" function. Is there any way on how to set only one blade?

The third thing- very sorry for my clumsiness- as I turned BeamDny feature ON (CompElast=2), it is hard for me to identify the modes from one operating point to the next in the "Summary.txt" file with the wind speeds up. And Compared with ED , no blade changes are visible in VTK files with BeamDny feature ON. I don't sure if it's my setup or the program. Any suggestions/guidance?

Dear openfast team,
i wanted to ask you what's the procedure to upload the output file generated from the openfast simulation in Matlab.
Thank you

1. The InflowWind.dat, ServoDyn.dat, and ElastoDyn.dat files required to run runCampbell.m script are missing inside the TemplateFiles directory.
2. WriteVTKmodes and WriteFASTfiles are assigned twice. It can be understood if WriteVTKmodes is set true then VTK files will be generated. However, I see the purpose of using WriteFASTfiles flag is redundant because without generating the FAST input files and running FAST there will be no *.lin output file, which in turn is required by the fx_mbc3 at lines 173 or 182 inside the runCampbell.m script.
3. As mentioned in one of my last issue (#17), xlmwrite function at line numbers 188, 230 and 231 does not work on Mac OS. I think an alternative solution to xlmwrite is needed here.
4. The code from line number 198 does not work without the Campbell data being generated at 184 if WriteFASTfiles flag is set false.
5. The system commands like copy, used in line 180, are OS-dependent. Also the file fort.51 used in the copy command is missing. I was expecting fort.51 file would be generated by runCampbell script but it does not create this file.

We have more and more python-scripts available to deal with OpenFAST simulations, but no repository for it.
Some options would be to either:

1. Create a python-toolbox repository
2. Rename matlab-toolbox to openfast-toolbox. Then we could either gather code by:
   2.1 language (e.g. a folder matlab and a folder python at the root
   2.2 functionality (e.g. folders io , mbc, areoacoustics, preprocessors.

If you think of other options, I can add them to this post. I'd be happy to hear the opinion of people listening to this channel (for instance: @bjonkman, @andrew-platt , @jjonkman , @ptrbortolotti, @nikhar-abbas, @gbarter, @kshaler, @evan-gaertner, @ewquon)

Hopefully we can come up with some kind of consensus on what to do about matlab/python. Then I'd suggest we sit down and decide on an architecture. On the python side, I'd like to aim for a repository with unit tests and continuous integration, and a couple of examples. Hopefully we can find a balance between adding a lot of inconsistent scripts and having a too restrictive framework that no one dares using or pushing to.

I believe the repository should stay fairly small and OpenFAST-focused: read/write files, generate cases, postprocess them. Some of these steps might involve generic tools, which we can extract from other repositories without actively developing on them. Otherwise things might run out of proportion.

But that's already too much details.. I just want to start a discussion on where to put our python scripts. Let me know your thoughts.

Examples of repositories with potential overlap

• DTU Wind energy toolbox https://gitlab.windenergy.dtu.dk/toolbox/WindEnergyToolbox
• ROSCO_toolbox https://github.com/NREL/ROSCO_toolbox
• WISDEM https://github.com/wisdem/wisdem
  Some of my repos that I'm happy to move around:
• Wind energy IO: https://github.com/ebranlard/weio
• FASTlib: https://github.com/ebranlard/welib/tree/master/welib/fastlib
  and more

Hello everyone,

I don't quite understand how to use the matlab runFAST.m function.
I would like to know how to modify which parameters to make it work properly.

This is the source code:

function status = runFAST(FASTfilenames, FASTexe, varargin)
% Run a set of FAST simulations using FAST exe.
%
% TODO , parallelization...
%
% INPUTS
% - FASTfilenames: list of fullpath (relative or absolute) to fst flies
% - FASTexe: fullpath (relative or absolute) to an openfast executable
%
% OPTIONAL INPUTS:
% - varargin is a set of ('key', value) pairs.
% Look at opts below for the different options, and default values.
%
% OUPUTS:
% - status: array of status for each simulation

% --- Optional arguments
OptsFields={'flag',};
opts=struct();
% Default values
opts.flag = '' ; % Extra flag passed as command line argument
% Values input by users % NOTE: inputParser not available in Octave
if mod(length(varargin),2)~=0; error('Varargin should have an even number of values, for key/values pairs'); end
for iVar = 1:2:length(varargin)
i = find( strcmp( OptsFields, varargin{iVar}) == 1);
if ~isempty(i)
opts.(OptsFields{i}) = varargin{iVar + 1};
else
warning('Optional key %s not supported by function %s',varargin{iVar},mfilename)
end
end
% --- Inputs sanity
if ispc()
FASTexe = strrep(FASTexe,'/','');
end

status=zeros(1,length(FASTfilenames));

% --- Creating a list of commands
commands=cell(1,length(FASTfilenames));
for isim = 1:length(FASTfilenames)
FASTfile = FASTfilenames{isim};
if ispc()
FASTfile = strrep(FASTfile,'/','');
end
sCmd= [FASTexe ' ' opts.flag ' ' FASTfile];
commands{isim}=sCmd;
end

% --- Running
status = runCommands(commands);

Thank you for your answers.

The documentation says addpath( getpath('AbsolutePathToToolbox') ) to add the path to matlab-toolbox in Matlab. I think the command should be instead addpath( genpath('AbsolutePathToToolbox') )

Hello everyone,

I don't quite understand how to use the matlab ReadFASTMesh function. Does the fileID correspond to a .vtk file? How to generate a mesh file?
If anyone ever has a mesh file so I can analyze the structure.

Thank you for your answers.

Regards,

Tom

Hi,

OpenFAST/openfast#480 (comment)

I saw the above link.

Currently, can I plot the Campbell diagram by using SubDyn?

Or should I modify the source code(writeLinearizationFiles.m) to use SubDyn(or HydroDyn)

Thank you.

Best regards,

how use getPSD.m

Hello
I am trying to execute the mfile scripts but getting the errors 'could not locate openfast3.0_x64s.exe in _ExampleData folder'.
I tried locating the file but there is no such file.
It will be great to get a response.
Thanks

fx_getMats code matData.WindSpeed(iFile) = data(iFile).WindSpeed appeared a bug : Cannot perform assignment because the number of elements on the left and right sides is different

But all 36 .lin files can be generated

The detailed information is shown in the following diagram

My OpenFAST version is 3.5.2
Matlab workspace

The campbell_diagram_data.m script provides a useful representation of the eigensolution so as to enable users to interpret the eigenvectors and eigenvalues resulting from the MBC3 analysis in terms of the full system natural frequencies, damping ratios, and mode shapes. However, the script has not been updated to reflect recent improvements to OpenFAST involving linearization of SubDyn, MoorDyn, AeroDyn, and the structural control (StC) submodel of ServoDyn. A few improvements are warranted:

• For the ElastoDyn and BeamDyn states, only the displacement states are included in the eigenvectors because the velocity states contain redundant information. However, both the displacement and velocity states from MoorDyn are currently included. These velocity states should be removed from the reported eigenvectors.

• The script applies scaling to the blade and tower translation states of ElastoDyn and BeamDyn so as to ensure all states represented in the eigenvector have similar units (radians). That is, the blade translation states are scaled by one over the blade length and the tower translation states are scaled by one of the tower length, effectively converting the translation in meters to an equivalent slope in radians. Similar scaling should be added for the platform transnational displacements in ElastoDyn (based on the tower length) and the mooring line translational states in MoorDyn (based on the water depth). Likewise, a scaling of the C-B mode states in SubDyn and the StC states in ServoDyn should be developed.

• Aerodynamic states from the DBEMT and UA submodels of AeroDyn can now be included in the linearized state-space matrices derived from OpenFAST. It is desired to account for the effect of these aerodynamic states on the frequencies and damping of the structure, but not to have aerodynamic modes themselves show up in the eigensolution. A way to eliminate the aerodynamic modes from showing up in the eigensolution should be developed.

Dear openfast team,
I use the "changeFASTInputDeck.m" to extract data from HydroDyn Input File, but the new "HydroDyn. dat" generate some errors.
The "PLATFORM ADDITIONAL STIFFNESS AND DAMPING" in old input files is shown below:
---------------------- PLATFORM ADDITIONAL STIFFNESS AND DAMPING -------------- [unused with PotMod=0 or 2]
0 AddF0 - Additional preload (N, N-m) [If NBodyMod=1, one size 6NBody x 1 vector; if NBodyMod>1, NBody size 6 x 1 vectors]
0
0
0
0
0
0 0 0 0 0 0 AddCLin - Additional linear stiffness (N/m, N/rad, N-m/m, N-m/rad) [If NBodyMod=1, one size 6NBody x 6NBody matrix; if NBodyMod>1, NBody size 6 x 6 matrices]
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0 AddBLin - Additional linear damping(N/(m/s), N/(rad/s), N-m/(m/s), N-m/(rad/s)) [If NBodyMod=1, one size 6NBody x 6NBody matrix; if NBodyMod>1, NBody size 6 x 6 matrices]
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0 AddBQuad - Additional quadratic drag(N/(m/s)^2, N/(rad/s)^2, N-m(m/s)^2, N-m/(rad/s)^2) [If NBodyMod=1, one size 6NBody x 6*NBody matrix; if NBodyMod>1, NBody size 6 x 6 matrices]
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0

!!!!!however, the new input files that generated through "Matlab2FAST.m" is shown below(PLATFORM ADDITIONAL STIFFNESS AND DAMPING part, too):
---------------------- PLATFORM ADDITIONAL STIFFNESS AND DAMPING -------------- [unused with PotMod=0 or 2]
0 AddF0 - Additional preload (N, N-m) [If NBodyMod=1, one size 6NBody x 1 vector; if NBodyMod>1, NBody size 6 x 1 vectors]
0, 0, 0, 0, 0, 0 AddCLin - Additional linear stiffness (N/m, N/rad, N-m/m, N-m/rad) [If NBodyMod=1, one size 6NBody x 6NBody matrix; if NBodyMod>1, NBody size 6 x 6 matrices]
0, 0, 0, 0, 0, 0 AddBLin - Additional linear damping(N/(m/s), N/(rad/s), N-m/(m/s), N-m/(rad/s)) [If NBodyMod=1, one size 6NBody x 6NBody matrix; if NBodyMod>1, NBody size 6 x 6 matrices]
0, 0, 0, 0, 0, 0 AddBQuad - Additional quadratic drag(N/(m/s)^2, N/(rad/s)^2, N-m(m/s)^2, N-m/(rad/s)^2) [If NBodyMod=1, one size 6NBody x 6*NBody matrix; if NBodyMod>1, NBody size 6 x 6 matrices]

Some of the following parameters are also different, I'm not sure if it's my setup or the program. Any suggestions/guidance? Thank you!!!

how to install on matlab ?