Improve User-Specified Wave-Kinematics File Formatting Requirements for WaveMod = 6 #118
Comments
ebranlard
added a commit
to ebranlard/openfast
that referenced
this issue
Feb 7, 2019
…aveMod=6 (Should Fix OpenFAST#118)
|
I've added some checks for this format (see merge request #239 above). For now, the file is allowed to have more lines and more columns than required, but not less (before it could). I can add test to check for strict equality of number of lines and columns if needed. |
rafmudaf
added a commit
that referenced
this issue
Mar 27, 2019
Adding safety on number of lines and number of fields per line when WaveMode=6 (Should Fix #118)
|
|
rafmudaf
pushed a commit
to rafmudaf/openfast
that referenced
this issue
Apr 8, 2019
…aveMod=6 (Should Fix OpenFAST#118)
rafmudaf
pushed a commit
to rafmudaf/openfast
that referenced
this issue
Apr 9, 2019
…aveMod=6 (Should Fix OpenFAST#118)
Merged
|
Hi all, I am facing issue with externally generated wave kinematics WaveMod=6 in OpenFAST-v2.4.0 as I am getting wave elevations of zero in output file. I have attached the relevant input files. Kindly suggest me on this. Thanks, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The data format of the various user-specified wave-kinematics input files (.Elev, .Vxi, .Vyi, .Vzi, .Axi, .Ayi, .Azi, and .DynP) used with the WaveMod = 6 option in HydroDyn are very finicky, with very specific requirements regarding data format, white space, etc. This has caused many users trouble. HydroDyn should be made more robust so that the data format requirements are more user-friendly. More information can be found in the following forum topic: https://wind.nrel.gov/forum/wind/viewtopic.php?f=4&t=1690.
The text was updated successfully, but these errors were encountered: