-
Notifications
You must be signed in to change notification settings - Fork 34
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
stress extrapolation #1179
stress extrapolation #1179
Conversation
phi_f.AddDomainIntegral(Dimension<dim>{}, DependsOn<i...>{}, f, mesh); | ||
mfem::Vector b = phi_f(0.0, solution_fields ...); | ||
|
||
mfem::CGSolver cg(MPI_COMM_WORLD); |
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.
mfem::CGSolver cg(MPI_COMM_WORLD);
This was the offending line of code that caused the incorrect results in parallel. Originally, I created the CGSolver
without the parallel communicator which made each processor solve its own problem in isolation, rather than together.
I believe the parallel issue is fixed now, and this is ready for review. |
Is the L2 field equivalent to the volume averaging trick I've been using for a while in LiDO? That is, integrating the stress in each element and dividing by element volume |
Yes, the volume averaging trick is equivalent to specifying |
Awesome, once this propagates to LiDO I'll update our serac visualization operator to use it so we can plot smoother fields. Thanks @samuelpmish! |
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.
This is a great feature! Thanks @samuelpmishLLNL !
src/serac/physics/tests/fit_test.cpp
Outdated
|
||
Empty internal_variables{}; | ||
|
||
sigma_J2 = fit< dim, output_space(input_space) >([&](double /*t*/, [[maybe_unused]] auto position, [[maybe_unused]] auto displacement_){ |
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.
Should this be added as a default output to the solid mechanics solver or should we leave it up to users to define their favorite stress measure of choice?
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.
My vote is to limit the scope of this PR to just adding the feature and discuss potential changes to the physics modules later on.
No description provided.