-
Notifications
You must be signed in to change notification settings - Fork 239
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
LIE/HM part 2: Data structure #1538
Conversation
@wenqing can you please review this? |
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.
Looks good.
{ | ||
} | ||
|
||
typename HMatricesType::HMatrixType H_u; |
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.
Note: Default-constructing these matrices might fail miserably if they are of dynamic size. Currently that probably doesn't matter, because displacement-related stuff is always fixed size.
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.
yes, it's fixed size matrix. but isn't Jenkins testing both Eigen dynamic size matrix and fixed size matrix cases?
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 see, I was confused.
If you resize the matrices in your assembler, or assign to them as a whole, not component-wise, s.t. they have a proper size in the end, there will be no problem.
OpenGeoSys development has been moved to GitLab. |
a part of #1535, depends on #1537
This PR focuses on data structures used in LIE/HM, i.e. process data and integration point data