-
Notifications
You must be signed in to change notification settings - Fork 571
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
STK::io::create_ioss_region() throw/error #13389
Comments
Oh, this is a test that activates:
If I remove the Let me know how to proceed. |
@spdomin @gsjaardema Tolu tells me that |
It is probably related to the latest SEACAS snapshot into Trilinos. I will see if I can reproduce and get in a fix... The serialize_io was added for one of the HPC systems that had an easily overloaded file system. It specifies the maximum number of ranks that should be hitting the file system (exodus reads/writes) at one time. There are a couple tests in SEACAS that exercise this, but obviously not covering all the cases... |
Dear @gsjaardema - sounds great. Let me know if you need more details on the Nalu test. I pulled my Trinity 4000 node DNS input files and noted that we did not activate this option for our nearly 256K MPI rank sims... I wonder if we still need this option:) |
I havent't heard of anyone using it lately, but it (usually) doesn't cause much overhead in development and there may be customers using it externally that I am not aware of. I may look into deprecating it and see if I get any complaints/comments. I think I know where I messed up and can trigger the error on just an io_shell run, so should have a fix soon... |
Former Nalu failing tests now look clean. |
I have a throw in stk::io::Inputfile::create_ioss_region() in InputFile.cpp:
This is occurring in a Nalu regression tests that has to "realms" - one for multiphysics, and the other for IO output. Otherwise, there is no real specialty about this test. We even have other tests that have this pattern.
The good/bad occurred over the recent fmt issue, so my bisect is problematic.
Good:
NaluCFD/Nalu SHA1: 1ef81b6de5bbf1964d8bec6b0b64810def33b123 Trilinos/develop SHA1: c8548cf7bdc5a50daff9fdf93d493228a74a3973
Bad:
NaluCFD/Nalu SHA1: 1ef81b6de5bbf1964d8bec6b0b64810def33b123 Trilinos/develop SHA1: 4b4c11941eb02f08372ba993bd4d54fcb0625ffa
Here are a few snapshots of the call stack:
@alanw0 or @gdsjaar - has anything in STK::io recently changed?
The text was updated successfully, but these errors were encountered: