-
Notifications
You must be signed in to change notification settings - Fork 126
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
check engine type #3719
Comments
The Engine::Type() method returns what you want:
|
(I'm not sure what to think about the trace, but lets take this one step at a time...) |
Thanks @eisenhauer That helped me a lot! And, it turned out that the engine type in our test DOES change during the simulation. Sorry that I don't have a minimum example yet to reproduce the problem; but my understanding of our code is that we store an and
It appears to me that only the first iteration gets the correct engine type from the XML file. The subsequent iterations fall back to the default I wonder if this is due to some lifetime logic in adios2? Note that in our case, for different checkpoint filenames, the |
I'll make another issue for the change of engine issue. So closing this one. |
@eisenhauer sorry, a follow-up question: is the following way to set and check engine/parameters correct: io_ = ad.DeclareIO(io_name_);
io_.SetEngine("BP5");
io_.SetParameter("SubStreams", "0");
auto params = io_.Parameters();
std::cout << "Substreams = " << params["SubStreams"] << std::endl; |
Sorry for the delayed response, but yes, that's the right way to set and check engine parameters. |
Hi, in the C++ interface, what is the routine to find out the engine type?
PS: In my case, I set the engine to
BP5
for my output in the XML file but got an error that showsBP4Writer::EndStep
is called.(I've checked the validity of the XML file by setting the engine in the XML file to an invalid value like BPx and then it gives an error, indicating that the XML file is indeed picked up).
The debug trace relevant to adios2 can be found here.
The text was updated successfully, but these errors were encountered: