ADIOS2 Engine Used at Runtime
Open
backend: ADIOS2
feature request
frontend: C++17
frontend: Python3
- Dominant language
- C++
- Stars
- 161
- Forks
- 59
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 7
Description
After we opened a series, it would be good if we could query the exact ADIOS2 engine that is being used. We already have a general backend query (MPI/no-MPI HDF5 or ADIOS2 or JSON) and adding one more string on the ADIOS2 engine as a separate API would be useful when we need to specify options or work-arounds in downstream codes.
Contributor guide
Research direction
No file or test is named. Start by tracing the Series API's existing general backend query and the ADIOS2 engine selection path. Done means a separate API reports the exact ADIOS2 engine used after opening a series, with coverage showing the returned value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100