Closed amineeva-GWT closed 2 weeks ago
Hi, thanks for the heads up here!
If you add the channels you want to this dictionary, does it work?
For the WEIS team or future self: a better solution we should implement would be to update/standardize the reading of the output channels. InflowWind uses an older version. Updating that fast_out_vars
dict is tedious.
This is the newer version I like better: https://github.com/WISDEM/WEIS/blob/9d80ce8517a9a4b814082626bd2159d9acfcba30/weis/aeroelasticse/FAST_reader.py#L154
Yes, adding them directly to the dictionary creates outputs for those variables. Thanks for your help!
Thanks for following up! I'll re-open this until we implement the more permanent fix.
@mayankchetan , can we close this since OpenFAST will handle I/O writing soon?
Yes, we expect to release openfast_io
with the v4.0 release and then I'll have it integrated into WEIS soon after
Description
I'm successfully running an OpenFast simulation using WEIS, but am only getting data from some outputs I list in the InflowFile.dat file. Specifically, in the InflowFile.dat file it seems that any output variables with names longer than 9 characters are somehow not being read by WEIS. However, they show up in the .out files when I run the same .fst file directly through OpenFast.
Steps to reproduce issue
Current behavior
This seems like a WEIS issue rather than an OpenFast one because I'm getting outputs when running directly through OpenFast. Something to note is that these variables have names that are longer than 9 characters, which goes against the output channel rules listed in the following outlist parameter document: https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fopenfast.readthedocs.io%2Fen%2Fmain%2F_downloads%2F3f19498a5dc774461e022b671ff01ec6%2FOutListParameters.xlsx&wdOrigin=BROWSELINK
Expected behavior
Hopefully, WEIS should recognize and track all outputs.