The "RotorApexOffsetPos" array was not assigned valid REAL values on line #59 - Issue with openfast_toolbox

Wind & Water Computer-Aided Engineering Software Tools
1

Hi, I have a slight problem in running openfast_toolbox with the latest versio of OpenFAST and IEA 15WM UMaine. I konw the cause, but not sure what the solution is.
OpenFAST version: 4.0.2
IEA 15MW UMaine semisub: downloaded few days ago
I set up a spreadsheet to run a series of analyses with openfast_toolbox, and everything goew well up to this point:

Running InflowWind.

FAST_InitializeAll:InflowWind_Init:InflowWind_ParseInputFileInfo:ParseSiAry:
 >> A fatal error occurred when parsing data from
 "WorkingDir/IEA-15-240-RWT/IEA-15-240-RWT_InflowFile_0_3_3.dat".
 >> The "RotorApexOffsetPos" array was not assigned valid REAL values on line #59.
 >> The text being parsed was :
    "0.0                    RotorApexOffsetPos - Offset of the lidar from hub height (m)"

 OpenFAST encountered an error during module initialization.
 Simulation error level: FATAL ERROR

 Aborting OpenFAST.

I checked the file IEA-15-240-RWT_InflowFile.dat that I have in the IEA/IEA-15-240-RWT, and at line #59 I have the following:

0.0 0.0 0.0            RotorApexOffsetPos  - Offset of the lidar from hub height (m)

but when OpenFAST toolbox copy this file in the WorkingDir, at line 59 I have this:

0.0                    RotorApexOffsetPos - Offset of the lidar from hub height (m)

So, it seems that the openfast_toolbox script is stripping the Y/Z offset values (0.0 0.0 ) from RotorApexOffsetPos , leaving only 0.0 . This violates OpenFAST’s requirement for three values in array-type parameters. The issue seems to stem from how the script parses and writes input files, particularly for multi-value entries.
Has anyone encountered this error?
Also, not sure why the parameters of the LIDAR are read even if I set SensorType to 0.
@Andrew.Russell maybe can help?
Maurizio

2

By the way, I found a quick fix, although not a solution - and not sure if it is messing up something else.
In the original InflowWind input file, putting 0.0,0.0,0.0 rather than 0.0 0.0 0.0 seems to solve the issue.

1 Like
3

Hi Maurizio,
Thanks for bringing this issue to our attention. We have a pending PR fixing this issue: Allow space-separated entry by default by rthedin · Pull Request #45 · OpenFAST/openfast_toolbox · GitHub. You can get that branch or use your workaround in the meantime before the PR is merged. Your workaround does not have any negative implications. Please read the PR description for more information.

Thanks for reporting this.

1 Like