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

Meaning of NACA Variable "ma" #20

Closed
jwethan opened this issue Jul 19, 2023 · 3 comments
Closed

Meaning of NACA Variable "ma" #20

jwethan opened this issue Jul 19, 2023 · 3 comments

Comments

@jwethan
Copy link

jwethan commented Jul 19, 2023

I'm working on a new adaptation of the code to simulate heaving and passive pitching foils. I'm trying to implement code to treat the pitching about the leading edge as a torsional spring in response to the moment imposed by the fluid. I am using the NACA geometry as the body and I was wondering what the variable "ma" is holding in the NACA file. It's used in the Body "react" function in computing the dynamics, what does it represent? Seems like it has something to due with the shape inertias but I'm not sure.

All help is appreciated, thanks.

@weymouth
Copy link
Owner

weymouth commented Jul 19, 2023

It is the body's added mass.

@jwethan
Copy link
Author

jwethan commented Jul 20, 2023

I may be confused, but why does it have 3 different components? The z-component of the PVector is used to calculate the new ddotphi in the rotational dynamics, what is that accounting for?

ddotphi = M + ma.z*ddotphi/(I0 + ma.z);

I don't see the need for it in my equations, so I'm wondering if I am missing something.

Why are both the moment of inertia calculated from Body getArea() and ma.z needed?

Thanks for the help.

@weymouth
Copy link
Owner

Apologies. It is the added mass. The linear inertia due to accelerating the surrounding water from translation in x or y or rotation around z.

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

No branches or pull requests

2 participants