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
Copy file name to clipboardExpand all lines: NEWS.rst
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ Building openPMD-api now requires a compiler that supports C++17 or newer.
11
11
12
12
Python 3.10 is now supported.
13
13
openPMD-api now depends on `toml11 <https://github.com/ToruNiina/toml11>`__ 3.7.0+.
14
+
pybind11 2.9.1 is now the minimally supported version for Python support.
14
15
15
16
The following backend-specific members of the ``Dataset`` class have been removed: ``Dataset::setChunkSize()``, ``Dataset::setCompression()``, ``Dataset::setCustomTransform()``, ``Dataset::chunkSize``, ``Dataset::compression``, ``Dataset::transform``.
16
17
They are replaced by backend-specific options in the JSON-based backend configuration.
Copy file name to clipboardExpand all lines: README.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ See [the openPMD standard](https://github.com/openPMD/openPMD-standard) for deta
27
27
28
28
This library provides a reference API for openPMD data handling.
29
29
Since openPMD is a schema (or markup) on top of portable, hierarchical file formats, this library implements various backends such as HDF5, ADIOS1, ADIOS2 and JSON.
30
-
Writing & reading through those backends and their associated files is supported for serial and [MPI-parallel](https://www.mpi-forum.org/docs/) workflows.
30
+
Writing & reading through those backends and their associated files are supported for serial and [MPI-parallel](https://www.mpi-forum.org/docs/) workflows.
31
31
32
32
## Usage
33
33
@@ -104,7 +104,7 @@ Required:
104
104
105
105
Shipped internally in `share/openPMD/thirdParty/`:
Copy file name to clipboardExpand all lines: docs/source/details/backendconfig.rst
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,7 @@ Parameters that are directly passed through to an external library and not inter
35
35
36
36
The configuration string may refer to the complete ``openPMD::Series`` or may additionally be specified per ``openPMD::Dataset``, passed in the respective constructors.
37
37
This reflects the fact that certain backend-specific parameters may refer to the whole Series (such as storage engines and their parameters) and others refer to actual datasets (such as compression).
38
+
Dataset-specific configurations are (currently) only available during dataset creation, but not when reading datasets.
38
39
39
40
A JSON/TOML configuration may either be specified as an inline string that can be parsed as a JSON/TOML object, or alternatively as a path to a JSON/TOML-formatted text file (only in the constructor of ``openPMD::Series``):
40
41
@@ -129,6 +130,29 @@ Explanation of the single keys:
129
130
This workaround is enabled on a per-dataset level.
130
131
The workaround can be completely deactivated by specifying ``{"adios2": {"use_span_based_put": true}}`` or it can alternatively be activated indiscriminately for all datasets by specifying ``{"adios2": {"use_span_based_put": false}}``.
131
132
133
+
Operations specified inside ``adios2.dataset.operators`` will be applied to ADIOS2 datasets in writing as well as in reading.
134
+
Beginning with ADIOS2 2.8.0, this can be used to specify decompressor settings:
135
+
136
+
.. code-block:: json
137
+
138
+
{
139
+
"adios2": {
140
+
"dataset": {
141
+
"operators": [
142
+
{
143
+
"type": "blosc",
144
+
"parameters": {
145
+
"nthreads": 2
146
+
}
147
+
}
148
+
]
149
+
}
150
+
}
151
+
}
152
+
153
+
In older ADIOS2 versions, this specification will be without effect in read mode.
154
+
Dataset-specific configurations are (currently) only possible when creating datasets, not when reading.
155
+
132
156
Any setting specified under ``adios2.dataset`` is applicable globally as well as on a per-dataset level.
133
157
Any setting under ``adios2.engine`` is applicable globally only.
0 commit comments