-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ServoDyn: StC controls, and cable controls for MD and SD #664
Conversation
We want to initialize SD and MD before SrvD so that we can pass channel info over to SrvD about the cable tensioning control signals.
Also revise glue code for appropriate resizing of arrays for control channel info
Example of ServoDyn summary file from a fictional architecture test:
Note that in this example case, cable control channels 7 & 9 were requested from MoorDyn. Channels 1,2,3,4,5,6, & 8 were not, but the array is sized from 1:max(chanRequestNumber). |
@andrew-platt , after a quick look, the only things that stood out to me are these items:
|
@andrew-platt, I used this PR with ROSCO via the bladed interface and was able to read the version of the extended avrSwap and write a control input to the mooring line control. Exciting to see all the extra sensors and possibilities! |
This is manually transcribed from work by Mandar Phadnis (CU Boulder) in 2020
3a2c04e
to
b4a2fad
Compare
b4a2fad
to
d956e39
Compare
The reference position, reference orientation, translational displacement, and orientation at init are now passed to SrvD for all the StC instances. It is possible to do this with less info since some orientations could be assumed at init, but for throroughness we pass all of it to ServoDyn to use in initializing the StC instances. This in some ways future-proofs for when arbitrary initial orientations are added to the code (if ever)
9a183ad
to
03e8dd6
Compare
Invalid unit numbers could be passed to the CLOSE intrinsic causing a segfault
…release on linux FAST_Farm_Types would not complete compilation with: - ifort 2021.4.0 20210910 (from oneapi) - Intel Xeon X7350 chipset with 256 GB of memory - killed compilation after 33 hours It isn't clear exactly what fails in the -O3 optimization -- the -qopt-report=5 option yielded a very long report, but I only spent a few hours trying to figure it out. Need to move on to something else.
Test was reconfigured and bugs found in the StC implemantion that changed results.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I quickly reviewed the updated documentation; please find a few comments below.
Also, where are extended avrSWAP array mappings documented?
docs/source/user/servodyn-stc/ExampleFiles/NRELOffshrBsline5MW_StC.dat
Outdated
Show resolved
Hide resolved
Added documentation for the extended Bladed DLL interface. So finally ready to merge. |
This PR is not ready for merging. Feedback is requested from end users
Feature description
This pull request adds the following capabilities:
Related issue, if one exists
#646 -- status request about this project
#565 -- MoorDyn initial cable implementation
#537 -- SubDyn cable capabilities added
#395 -- Flap controls added to AD15
Impacted areas of the software
This change affects the ServoDyn module and the cable controls added to MoorDyn and SubDyn in prior pull requests.
Additional supporting information
StC_DOF_MODE
=1 or 2). A control channel set can be requested from each of the StC input files. The StC instance will then pass the local displacement and velocity in X, Y, and Z to the controller. The controller then can change the stiffness, damping, brake force, and external force in each of the local X, Y, and Z directions. This is then passed to each StC that requested a control channel. This is related to ServoDyn Structural control submodule (formerly TMD) #607.Test results
Input files for ServoDyn change with this PR (additional lines). There are no specific test cases for this set of features as no publicly available models using these features.
Now that summary files are produced by ServoDyn, it might be worth rerunning the baselines and adding those files to the regression test results.
Checklist of items to address