ROSCO Case Using OpenFAST Turbine Path Errors

Wind & Water Controls
1

Hi all,

I’m attempting to run the ROSCO example 20_active_wake_control.py using an OpenFast NREL 5MW turbine. However, I get an error where the Cp table cannot be loaded. I have generated a Cp_Ct_Cq.txt file using 02_ccblade.py and modified the .yaml file to point to the location of the rotor performance file. The example runs as expected when using the default case (Nrel 2p8 turbine). For some reason, Rosco still points towards the old Cp file location and I get the following error:

Loading rotor performance data from text file: [...]/ROSCO/Examples/Test_Cases/Test_Cases/NREL-5MW/Cp_Ct_Cq.NREL5MW.txt
WARNING: Cp table not loaded!

I can’t find where it is getting this path from, especially since it is accidentally referencing Test_Cases twice. Does anyone have insight into what may be causing this? I did a grep search through the entire ROSCO folder for the repeated Test_Cases path to make sure I didn’t mistype a path somewhere and it found nothing.

2

Dear @Ben.Pelson,

The file name and path to the rotor performance table is set in the ROSCO input (DISCON.IN) file via input parameter PerfFileName.

Best regards,

3

I’ve ensured my file is pointing to the correct DISCON and the DISCON is pointing to the correct Cp_Ct_Cq using PerfFileName, but running the code still gives the error:

KeyError: 'Cp'

Using ofTools in rosco.toolbox...

ASDF [...]/ROSCO/Examples/Test_Cases/5MW_Land_DLL_WTurb_wNacDrag/NRELOffshrBsline5MW_Onshore_ElastoDyn.dat

SDFASDF [...]/ROSCO/Examples/Test_Cases/5MW_Land_DLL_WTurb_wNacDrag/../5MW_Baseline/NRELOffshrBsline5MW_Blade.dat

"default"

Loading rotor performace data from text file: [...]/ROSCO/Examples/Test_Cases/Test_Cases/NREL-5MW/Cp_Ct_Cq.NREL5MW.txt

WARNING: Cp table not loaded!

(This error repeats a few times).

4

Hi Ben,

I think your issue is still related to the software not finding the Cp surface.

I’m not sure where it’s failing without more information or a stack trace.

Can you try absolute paths in your DISCON and tuning yaml?

I hope this helps.

Best, Dan

5

Please try tracking the OpenFAST file paths that the tuning yaml references to the DISCON and verify the path of the Cp surface in that DISCON.