I am trying to visualize the first 15 modes of a floating wind turbine. I am following the directions presented in AnalyzeModeShapes.m, but with a different wind turbine model. I was able to replicate the same steps for my model up to line 10. The next command
system([ openFASTexe ' -VTKLin ElastoDyn-Modes.viz']);
creates several .vtp files for visualization, but only for modes 3 - 15 (which I can open with ParaView with no problems). No .vtp files are created for modes 1 and 2, and no error messages are printed on the screen. What could possibly be the reason for this?
Some additional information:
- Running AnalyzeModeShapes.m for the 5MW_Land model in r-test generates .vtp files for modes 1-15.
- Other than a different EDfile, the main differences between the .fst file in r-test (5MW_Land_ModeShapes.fst) and the .fst of my model is that CompHydro, CompSub and CompMooring are set to 1, 1, 3, respectively, and the corresponding input files for these solvers are provided.
- I am able to run time simulations and linearization for my model with no issues
- I am using the same ElastoDyn-Modes.viz provided in r-test, except for lines 4 and 5 that have been changed to point to the appropriate files for my model.
- I am using the main branch of r-test and matlab-toolbox
Any help with this would be appreciated!
I have never run mode shape visualizations with other than onshore turbines. Can you maybe try to progressively add/remove the HydroDyn/MoorDyn/SubDyn modules, to see if this is an issue with one of the module?
Thanks a lot,
Hi Emmanuel, by progressively adding the modules, I was able to identify the problem arises when the MoorDyn is enabled and the platform has all 6 degrees of freedom (PtfmSgDOF, PtfmSwDOF, PtfmHvDOF, PtfmRDOF, PtfmPDOF, PtfmYDOF). These two modes that are missing are the sway and surge of the platform. Any idea why I can’t visualize them?
Do you know what the damped frequencies of those two modes are? There is a check that if the mode shape requires more than 500 vtk files it doesn’t create them. You could remove the lines
if (nt > 500) cycle and see if that works.
Their frequencies are 0.0323 and 0.032 Hz. I wasn’t aware of this limitation in the number of vtk files. Where do I exactly find the line
if (nt > 500) cycle ?
Based on your comment, I also tried to reduce VTK_fps in the .fst file from 30 to 15 and it solves the problem too.
if (nt > 500) cycle statement is hardcoded within OpenFAST (
A frequency of ~0.032 Hz requires around 30 seconds for a full mode. At 30 fps, this would require 900 frames. Your reduction to 15 fps is a good method to get around the 500 frame limit for these low frequency modes, but may limit what high frequency modes can be visualized (it is not immediately obvious from the code what the minimum number of frames for a mode shape is).