In general, the forces in fixed objects (bodies, rods, points) are not reported back from MoorDyn in output files. This should be resolved, as fixed objects are used to model anchors and their forces need to be accessible to users. This should be as simple as adjusting the logic in Time.cpp to include fixed objects in the doRHS calculations, or if we want to more closely match what is in MD-F, adding in a ground->doRHS() call at the end of the Time->CalcStateDeriv function :
|
for (auto obj : points) { |
A side note, not really sure why the line ground->setDependentStates(); is in there. This step is already covered in Time->Update.
Related discussion on NREL forum: https://forums.nrel.gov/t/forces-in-a-shared-anchor/9356/7
In general, the forces in fixed objects (bodies, rods, points) are not reported back from MoorDyn in output files. This should be resolved, as fixed objects are used to model anchors and their forces need to be accessible to users. This should be as simple as adjusting the logic in
Time.cppto include fixed objects in the doRHS calculations, or if we want to more closely match what is in MD-F, adding in aground->doRHS()call at the end of theTime->CalcStateDerivfunction :MoorDyn/source/Time.cpp
Line 131 in d87820d
A side note, not really sure why the line
ground->setDependentStates();is in there. This step is already covered inTime->Update.Related discussion on NREL forum: https://forums.nrel.gov/t/forces-in-a-shared-anchor/9356/7