Skip to content

Commit

Permalink
Snapshot naming, Remove Specs Mapping
Browse files Browse the repository at this point in the history
  • Loading branch information
ax3l committed Apr 7, 2021
1 parent c81864a commit 7823519
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 10 deletions.
9 changes: 1 addition & 8 deletions FORMAT_ADIOS.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,14 +35,7 @@ Thus, implementations should cast the data to and from `unsigned char` instead.

## `stepBased` Encoding of Iterations

In order to correlate openPMD iterations with ADIOS steps, the *root* group (path `/`) in ADIOS must contain a variable:

- `__step__`
- type: 1-dimensional array containing N *(int)* elements, where N is the number of ADIOS steps
- description: for each ADIOS step, this variable needs to be updated with the corresponding openPMD iteration.
- note: ADIOS steps are absolute and not every ADIOS step or openPMD iteration contains an update for each declared openPMD record.
- advice to implementers: [decide on this] an openPMD iteration for different openPMD records might be spread over multiple ADIOS steps.
An iteration of an openPMD record must correspond to exactly one ADIOS step.
The `iterationEncoding` mode `stepBased` must be implemented via ADIOS steps.

## Datasets

Expand Down
17 changes: 15 additions & 2 deletions STANDARD.md
Original file line number Diff line number Diff line change
Expand Up @@ -216,7 +216,7 @@ Each file's *root* group (path `/`) must further define the attributes:
- allowed values:
- `fileBased` (multiple files)
- `groupBased` (one file)
- `stepBased` (one file with internally encoding, if supported by the data format)
- `stepBased` (one file with internal encoding for iterations, if supported by the data format)

- `iterationFormat`
- type: *(string)*
Expand All @@ -227,13 +227,26 @@ Each file's *root* group (path `/`) must further define the attributes:
for `fileBased` formats the iteration must be included
in the file name;
the format depends on the selected `iterationEncoding` method
- note: it is not required that every openPMD iteration contains an update for each declared openPMD record (see below)
- examples:
- for `fileBased`:
- `filename_%T.h5` (without file system directories)
- for `groupBased`: (fixed value)
- `/data/%T/` (must be equal to and encoded in the `basePath`)
- for `stepBased`: (fixed value)
- `slowest varying index`
- data-format internal convention
- *slowest varying index* of data

### `stepBased` Encoding of Iterations

In order to correlate openPMD iterations with an index of data-format internal updates/steps or an index in the slowest varying dimension of an array, the *root* group (path `/`) must contain an additional variable once `stepBased` is chosen for `iterationEncoding`:

- `snapshot`
- type: 1-dimensional array containing N *(int)* elements, where N is the number of updates/steps in the file format
- description: for each update/step in a file format, this variable needs to be updated with the corresponding openPMD iteration.
- note: in some data formats, updates/steps are absolute and not every update/step contains an update for each declared openPMD record
- advice to implementers: an openPMD iteration might be spread over multiple updates/steps, but not vice versa.
In such a scenario, an individual openPMD record's update/step must appear exactly once per iteration.


Required Attributes for the `basePath`
Expand Down

0 comments on commit 7823519

Please sign in to comment.