Replies: 1 comment 2 replies
-
Can I ask about your desired usage here? You are mixing APIs. Generally we have a published/documented API produced by ADIOS' external bindings, but there also exists an internal API which isn't externally documented, may change between minor releases, etc. This internal API is only installed because ADIOS supports the external development of engines and transports which might be dlopen'd and installed at run-time. ("Supports" might be a strong word, since this is an undocumented feature that might be considered experimental.) The 'core' and 'helper' include files and namespaces are part of these internal APIs. Externally, we don't expose an API to retrieve the MPI_Comm because it is received from the application, not generated by us. If it weren't in general use by the application, the app probably wouldn't have initialized ADIOS with MPI. |
Beta Was this translation helpful? Give feedback.
-
See the MWE on how I am trying to fetch the MPI_Comm associated with the adios.
I see an error GetComm not a member of adios2::ADIOS
What is the correct way?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions