You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* ADIOS2: v2.7.0+
Increase ADIOS2 dependency to v2.7.0+
* CI: Newer Spack Version
This one does not yet have E4S caches, so build times might go
up a bit.
* [Draft] Remove Work-Arounds for ADIOS2<2.7.0
* Activate ADIOS2 SSC test
* Update some comments on ADIOS2 workarounds
* Only run SSC tests if ADIOS2 has been built with SSC
To do this, add .ssc as a possible file ending and enlist it under the
file endings.
* Activate tests for new ADIOS2 schema on MSVC
This also fixes broken array placement new in MSVC
* Update documentation in adios2.rst
Co-authored-by: Franz Pöschel <franz.poeschel@gmail.com>
Copy file name to clipboardExpand all lines: docs/source/backends/adios2.rst
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,8 +22,11 @@ Steps
22
22
23
23
ADIOS2 is optimized towards organizing the process of reading/writing data into IO steps.
24
24
In order to activate steps, it is imperative to use the :ref:`Streaming API <usage-streaming>` (which can be used for either file-based or streaming-based workflows).
25
-
With ADIOS2 release 2.6.0 containing a bug (fixed in development versions, see `PR #2348 <https://github.com/ornladios/ADIOS2/pull/2348>`_) that disallows random-accessing steps in file-based engines, step-based processing must currently be opted in to via use of the :ref:`JSON parameter<backendconfig>` ``adios2.engine.usesteps = true`` when using a file-based engine such as BP3 or BP4.
26
-
With these ADIOS2 releases, files written in such a way may only be read using the streaming API.
25
+
26
+
ADIOS2 release 2.6.0 contained a bug (fixed in ADIOS 2.7.0, see `PR #2348 <https://github.com/ornladios/ADIOS2/pull/2348>`_) that disallows random-accessing steps in file-based engines.
27
+
With this ADIOS2 release, files written with steps may only be read using the streaming API.
28
+
In order to keep compatibility with older codes reading ADIOS2 files, step-based processing must currently be opted in to via use of the :ref:`JSON parameter<backendconfig>` ``adios2.engine.usesteps = true`` when using a file-based engine such as BP3 or BP4.
29
+
27
30
Upon reading a file, the ADIOS2 backend will automatically recognize whether it has been written with or without steps, ignoring the JSON option mentioned above.
28
31
Steps are mandatory for streaming-based engines and trying to switch them off will result in a runtime error.
0 commit comments