-
Notifications
You must be signed in to change notification settings - Fork 27
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
Stiffness matrix and translation #8
Comments
Actually it seems that the |
Looking at this a bit more, here's my current understanding: stiffness: I think there was a bit of a problem here, which I've submitted a fix for with #22 (note however that what I've done is not yet propagated back to the hydrostatics: these look like they are currently calculated relative to a point on a vertical line passing through origin but with the correct vertical position: This section uses the x and y location of the origin ( meshmagick/meshmagick/hydrostatics.py Lines 605 to 621 in 0d214f9
This section uses the vertical location of the cog ( meshmagick/meshmagick/hydrostatics.py Lines 653 to 655 in 0d214f9
Thus, it might be appropriate to change this method so that it calculates based on COG, right? meshmagick/meshmagick/hydrostatics.py Line 599 in 0d214f9
This line would be changed to |
related to #1 |
I just released v3.0 which should fix these issues. Note however that I have totally refactored the hydrostatics module using only functions with no class. The code is far more simple and the number of lines of code has lowered. The stiffness matrix and metacentric stuffs are now expressed on a line passing though COG/buoyancy centre. Positions such as buoyancy centre are expressed in the initial frame. It allows to directly compare results to other commercial software such as Maat Hydro. |
I'm not actually sure if this is a bug or a feature that I don't understand:
The inertia matrix is invariant when the body is translated in the
x
direction.I would have expected the same to be true for the stiffness matrix.
Are the rotation dofs defined around the same axis in both cases ?
The text was updated successfully, but these errors were encountered: