-
Notifications
You must be signed in to change notification settings - Fork 55
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
Problems with only minor symmetry stiffness matrix? #39
Comments
@mrp089 I don't recall all instances. Do a simple `grep -i cctovoigt' in the folder to search for all function calls and add the extra logical argument to them. |
It looks like there are no other uses of |
Yes, the matrix is a As you see, when you don't have major symmetry, you need to assemble the full |
Thanks for the overview! Our My concern is that other parts of the code "downstream" still assume that |
Dm is used to assemble the local stiffness matrix in From my previous comment, once you assemble the full subroutines subroutines and make sure that there are correctly applied. For e.g., check if the correct row-column component of Bm is acting on D and vice-versa. From my understanding, simply creating a full Dm matrix should be sufficient. But you may verify the expressions just to make sure. |
I looked at your commit mrp089@5796f6e and it appears that the 3D assembly for Dm is correct. However, the 2D one looks incorrect to me. It should be,
Please verify. |
Thanks for checking @vvedula22, you're absolutely correct! And thank you for pointing out the lines for the multiplications. I'll check if they generalize for a full |
Part of #32. Our G&R model creates a tangential stiffness matrix that only has minor and no major symmetries. It thus has
36
unique entries (instead of21
with major symmetries). I extendedCCTOVOIGT
to handle that in mrp089@5796f6e.@vvedula22 Are you aware of any other places where
svFSI
might assume a stiffness matrix with major symmetries?The text was updated successfully, but these errors were encountered: