OpenFAST
Deprecate AD14 (rebasing of PR #18)
Removing AD14 and replacing with AD15. This PR supercedes #18 (that PR sat for too long and got a bit stale).
The following models still require work to determine the appropriate tau1_const parameter in the ADv15 input file:
- AWT_YFree_WTurb
- AWT_YFix_WSt
- WP_VSP_WTurb_PitchFail
- WP_VSP_WTurb
- SWRT_YFree_VS_WTurb
5MW_ITIBarge_DLL_WTurb_WavesIrr:
(NOTE: this test was disabled due to numerical instabilities)
Some tuning could be done on this case to get a better match.
AOC_WSt:
AWT_YFix_WSt:
using DBEMT_Mod=2
(Note: channels changed, so the regression test compare does not work)
AWT_YFree_WTurb:
(Note: channels changed, so the regression test compare does not work)
SWRT_YFree_VS_EDC01:
SWRT_YFree_VS_WTurb:
(NOTE: this test had been disabled due to instabilities and taking forever to run -- shorten it to 20 seconds or leave disabled)
UAE_Dnwind_YRamp_WSt:
(NOTE: this test had been disabled due to instabilities)
WP_VSP_WTurb_PitchFail:
Another (annoying) thing I would add, is if we are redoing the baselines, we could prune some output channels and maybe increase the output dt a bit, to potentially reach output binary files of say 200kb. For instance: -use only only blade number for each output channel name (some kind of rotation between blade 1, 2 or 3).
- Remove TTDspTwst which is always zero
Another (annoying) thing I would add, is if we are redoing the baselines, we could prune some output channels and maybe increase the output dt a bit, to potentially reach output binary files of say 200kb. For instance: -use only only blade number for each output channel name (some kind of rotation between blade 1, 2 or 3).
* Remove TTDspTwst which is always zero
There are a few other ADAMS outputs that are always zero and could be removed as well. @andrew-platt and I discussed this when removing the ADAMS coupling code.
Another (annoying) thing I would add, is if we are redoing the baselines, we could prune some output channels and maybe increase the output dt a bit, to potentially reach output binary files of say 200kb.
Also, if we are redoing baselines.... Since we have updated the way the regression test comparisons work, can we use packed binary output instead of the uncompressed binary output that most of the OpenFAST regression tests use? That would also reduce the file size.
@bjonkman and @ebranlard, I agree pruning outputs and switching to the packed binary files is a good idea.
@ebranlard, I agree on switching the name to just AeroDyn in comments and input files. The current version of AeroDyn is significantly different from the original AeroDyn15 -- if we were really following a numbering system we probably should be on AD18 or so by now. So calling it simply AeroDyn is much cleaner going forward. This release is a good time to do that.