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: STANDARD.md
+14-10Lines changed: 14 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,9 @@ for changes in keywords).
48
48
Hierarchy of the Data File
49
49
--------------------------
50
50
51
-
The used hierarchical data file format must provide the capability to
51
+
For simplificty, we call the storage concept of a specific data format that implements the openPMD hierarchy "files", even if they are implemented in-memory or by other means.
52
+
53
+
The used hierarchical data format must provide the capability to
52
54
53
55
- create groups and sub-groups (in-file directories)
54
56
- create multi-dimensional, homogeneous array-based data structures
@@ -85,7 +87,10 @@ Each file's *root* group (path `/`) must at least contain the attributes:
85
87
to create a real path from it replace all occurrences
86
88
of `%T` with the integer value of the iteration, e.g.,
87
89
`/data/%T` becomes `/data/100`
88
-
- allowed value: fixed to `/data/%T/` for this version of the standard
90
+
- allowed values:
91
+
- see *Iterations and Time Series* below
92
+
- for `fileBased` and `groupBased`, this is fixed to `/data/%T/`
93
+
- for `stepBased` this is fixed to `/data/`
89
94
- note: all the data that is formatted according to the present
90
95
standard (i.e. both the meshes and the particles) is to be
91
96
stored within a path of the form given by `basePath` (e.g. in
@@ -195,9 +200,8 @@ standard:
195
200
Iterations and Time Series
196
201
--------------------------
197
202
198
-
Iterations can be encoded in either the file name of each master-file of a
199
-
time step or in groups of the same file. (Here, an *iteration* refers
200
-
to a single simulation cycle.)
203
+
Iterations can be encoded in either the file name of each individual files, in groups of the same file, or in data sets & attributes (with supported data formats).
204
+
(Here, an *iteration* might refer to a single measurement or simulation cycle.)
201
205
202
206
The chosen style shall not vary within a related set of iterations.
203
207
@@ -212,6 +216,7 @@ Each file's *root* group (path `/`) must further define the attributes:
212
216
- allowed values:
213
217
-`fileBased` (multiple files)
214
218
-`groupBased` (one file)
219
+
-`stepBased` (one file with internally encoding, if supported by the data format)
215
220
216
221
-`iterationFormat`
217
222
- type: *(string)*
@@ -225,17 +230,16 @@ Each file's *root* group (path `/`) must further define the attributes:
225
230
- examples:
226
231
- for `fileBased`:
227
232
-`filename_%T.h5` (without file system directories)
228
-
- for `groupBased`:
233
+
- for `groupBased`: (fixed value)
229
234
-`/data/%T/` (must be equal to and encoded in the `basePath`)
235
+
- for `stepBased`: (fixed value)
236
+
-`slowest varying index`
230
237
231
238
232
239
Required Attributes for the `basePath`
233
240
--------------------------------------
234
241
235
-
In addition to holding information about the iteration, each series of
236
-
files (`fileBased`) or series of groups (`groupBased`) should have
237
-
attributes that describe the current time and the last
238
-
time step.
242
+
In addition to holding information about the iteration, each series of files (`fileBased`), series of groups (`groupBased`) or internally encoded iterations (`stepBased`) should have attributes that describe the current time and the last time step.
0 commit comments