-
Notifications
You must be signed in to change notification settings - Fork 286
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
ExodusII_IO_Helper: do not crash when outputting subdomains without elements #3949
Comments
I'd like to provide some more details on how to reproduce the error. Please consider the Moose input file from @Wendy-Ji posted here idaholab/moose#28485 (comment)
Running this input file gives the error mentioned:
The backtrace using gdb looks like:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear libmesh community,
This issue requests to make
write_element_data()
(and sister methods) more resistent to missing subdomains.As you know, Moose uses libmesh intensively also for the output of Exodus files. In addition, the so-called [MeshModifiers] have recently been extended, which allow elements to be moved from one subdomain/block to another subdomain/block. From my point of view this is a very important und highly welcomed feature. It also allows models to be handled on the basis of entire subdomains by simply moving all elements of a subdomain/block. For this purpose, moose offers the handy TimedSubdomainModifier. With this capability one effect araises: Some of the subdoamins/blocks will be empty for some time steps.
In connection with this functionality, issues for error messages from libmesh have been appearing more frequently recently, which look like this (where
[SOME ID]
is an integer pointing to one of the now empty subdomains):Some of the issues seeing this error:
The approach to leave one element in a subdomain just to avoid this error is a bit of a hack and increases model complexity. I'd like to avoid that.
The error message states the error is thrown in libmesh. According to a backtrace I did with gdb Moose is calling libmesh in line 343 of Exodus.C (method
Exodus::outputElementalVariables()
).https://github.com/idaholab/moose/blob/82b674a17dca177b6c140de82e9f4ceb14f097ad/framework/src/outputs/Exodus.C#L333-L343
As discussed over here with @GiudGiud, Moose could try remove the non-existing block from the element data before sending it to the exodus writer. That would be a little hacky. We assume that the better fix would be in libmesh, modifying
write_element_data
(and sister methods is needed) to not die on missing subdomains.Would it be an option for libmesh to make
write_element_data
(and sister methods) more resistent to missing subdomains?Jörg
The text was updated successfully, but these errors were encountered: