Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revise OpenFAST output file numbering scheme in main OpenFAST file #656

Open
andrew-platt opened this issue Feb 1, 2021 · 1 comment
Open

Comments

@andrew-platt
Copy link
Collaborator

andrew-platt commented Feb 1, 2021

The output file designations for OpenFAST is a bit confusing at present.

1 -  text
2 -  binary
3 -  text+binary
4 -  uncompressed binary
5 -  uncompressed binary+text
The sample input files say OutFileFmt = 0 is uncompressed binary (which is odd, because0 is
typically reserved for "None"), but this is actually treated as OutFileFmt = 5 by the source code.  

I propose we change to the following:

0 - none (for cases when results are passed directly back to a calling code)
1 - text
2 - binary
2u - uncompressed binary
3 - text + binary
3u - text + uncompressed binary
4 - future format #1 (TBD)
8 - future format #2 (TBD)

In the above, 3 and 3u are simply additive combinations of 1 and 2/2u. Similarly a later option 7u would be 4 + 1 + 2u.

@andrew-platt
Copy link
Collaborator Author

The issue with the currently output format specification was noticed by @jjonkman.

@andrew-platt andrew-platt changed the title Revise OpenFAST output file Revise OpenFAST output file numbering scheme in main OpenFAST file Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant