OpenFAST C++ Interface Not Writing Velocity Data Files

[mchurchf]

C++ Interface Velocity Data Write Out Line Needs to Be Uncommented
The OpenFAST C++ interface has been set up to write out aerodyn node velocity data each time step to an hdf5 file. That happens at:

openfast/glue-codes/openfast-cpp/src/OpenFAST.cpp

Line 235 in f2419c5

//writeVelocityData(velNodeDataFile, iTurb, nt_global, cDriver_Input_from_FAST[iTurb], cDriver_Output_to_FAST[iTurb]);

As you can see, by going to this line, the call to writeVelocityData is currently commented. It should be uncommented for proper behavior. As it is right now, the velocity data file is opened, but since it is not written to, it is filled with zeros. This is especially problematic because the user will not readily notice that anything has gone wrong because the file exists, and OpenFAST will even read it for restarts, but it will be reading zero velocity. When doing production OpenFAST-coupled CFD runs, the user may not notice a problem until the expensive run is complete and he/she goes to analyze the data.

To Fix
Uncomment the line shown here:

openfast/glue-codes/openfast-cpp/src/OpenFAST.cpp

Line 235 in f2419c5

//writeVelocityData(velNodeDataFile, iTurb, nt_global, cDriver_Input_from_FAST[iTurb], cDriver_Output_to_FAST[iTurb]);

and the problem is fixed.

Expected behavior
The expected behavior is that the hdf5 velocity data files are written to as the C++ interface sends velocity data from the external C++ code (like a CFD solver) to OpenFAST. One can see that as the solvers run, the size of the hdf5 velocity data files increase over time. If you use something like h5dump to view the file contents, you should see non-zero values (unless you are doing a zero motion case).