runFAST Matlab/Simulink issue (main thread)

[Viper19103]

When running the runfast.m file in ROSCO, what is the reason for the following error?

[dzalkind]

Hi, I cannot tell what the issue is without more information about your setup.

What example are you trying to run? What branch or version of ROSCO? Have there been any changes?

Have you been able to review the solutions here? #231

Best, Dan

[Viper19103]

I am running the ROSCO controller that came with ROSCO2.4.1, unchanged, and this problem occurred after running runfast.m

[dzalkind]

It's difficult for us to support older versions of the code. Please update and try some of the solutions proposed by others in the issue I cited. Most of the solutions involved the setting up of the OutList variable in the matlab script before Simulink was run.

We regularly test other examples in ROSCO not involving Matlab/Simulink.

[Viper19103]

This is also a problem with the latest version

[Melancho7ee]

Dear @Viper19103 ,

I encountered similar errors as you did. Although I have added this variable BldPitch1 to the output of ElastoDyn, I still get the same error as you did after running runFAST.m.

I recommend to do as follows (The following is based on ROSCO 2.8.0 I am using):

1. Starting from line 36 of runFAST.m, comment out the codes afterwards.

%% Premake OutList for Simulink

OutList = {'Time'};
OutList = [OutList;
    Param.IWP.OutList;
    Param.EDP.OutList;
    Param.ADP.OutList;
    Param.SvDP.OutList;
    ];

2. After completing the above processing, run runFAST.m.
3. Directly open the ROSCO.mdl, then run it at least twice.
4. Note the error messages that appear during these Simulink runs. They may be the true errors that you need to solve.

Personally, I can solve this problem after performing the above debugging process. However, I'm not sure if your problem is the same as mine. The above contents are for your reference.

Best regards,

[dzalkind]

I'll be directing all Matlab/Simulink issues here.

[dzalkind]

#398 discussions can continue here

[williamjussiau]

Hello,

1. For some reason, some versions of Simulink to not support this instruction and indeed raise a syntax error. Here, I surprisingly fixed it with find + strcmpi (recommended over strmatch):

u(find(strcmpi('your_variable_name', OutList)))

I personally find easier (e.g. for maintenance) to define indices of the variables to extract in the main Matlab script.

2. Also, in some cases, we need to make sure OutList is a cell array of strings. You might need to unravel each Param.*.OutList with {:} in this previous comment

3. I figured that some of the issues may be due to changes in OpenFAST API, with the files in the ROSCO repository not updated to the latest OpenFAST version. I personnally still have a problem running with Simulink, due to file formatting and input-output size problems. I will keep you updated if I find a good solution.