Skip to content
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

New MoorDyn features in the works #261

Open
RyanDavies19 opened this issue Oct 18, 2024 · 0 comments
Open

New MoorDyn features in the works #261

RyanDavies19 opened this issue Oct 18, 2024 · 0 comments

Comments

@RyanDavies19
Copy link
Collaborator

RyanDavies19 commented Oct 18, 2024

Hi @sanguinariojoe and @AlexWKinley,

I wanted to make sure you all are in the loop on some developments coming soon here. We are planning to open a PR in the near future that adds a viscoelastic model for synthetic lines and a VIV model for dynamic cables to MD-C. The viscoelastic stuff will just be to match what's in OpenFAST: OpenFAST/openfast#2459

The VIV stuff is a bit more involved, we have a paper in the works now that we are hoping to submit for review this month.

The big reason I wanted to bring this up is that both of these require an additional state variable that needs to be integrated each timestep. I've done this in a hackish way, by introducing another state called Misc that is a line-type state handled every time a line state is handled. Misc.pos[0] contains the state for VIV, Misc.pos[1] contains the state for viscoelastic stuff. This leaves 4 other unused states that are integrated (Misc.pos[2], Misc.vel[0:2]), which is not very efficient. Before I went and changed how we handled states I thought it would be good to discuss with you all thoughts on the best way to do this. I can't imagine this is the last time an additional state will be added, so having an approach to handle this would be good. My initial thought was to add a new Misc state type that only has the number of states needed, but the overwritten operators and time integration schemes are pretty rigid to the pos and vel states being vec3 or vec6. Let me know your thoughts on this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant