Skip to content

fix documentation of HDF5 backend options#65

Open
olivhoenen wants to merge 1 commit into
iterorganization:developfrom
olivhoenen:doc/fix_hdf5_options
Open

fix documentation of HDF5 backend options#65
olivhoenen wants to merge 1 commit into
iterorganization:developfrom
olivhoenen:doc/fix_hdf5_options

Conversation

@olivhoenen

Copy link
Copy Markdown
Collaborator

Found some inconsistencies between the doc and the code in https://github.com/iterorganization/IMAS-Core/blob/develop/src/hdf5/hdf5_utils.cpp#L732

Note that open_read_only was described be never added to the code (cf. https://git.iter.org/projects/IMAS/repos/al-core/pull-requests/56/overview). Maybe these commits can be added in the new repo?

@prasad-sawantdesai prasad-sawantdesai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also update docs/source/user_guide/configuration.rst

https://github.com/iterorganization/IMAS-Core/blob/develop/docs/source/user_guide/configuration.rst?plain=1#L100
(default is 100)?


``hdf5_read_buffering``
During a ``get`` operation, field data read from HDF5 is buffered in memory
before being returned to the caller.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hdf5_read_buffering
During a get operation, supported 0D and 1D field data read from HDF5 is
buffered in memory before being returned to the caller. Slice and time range
reads, as well as fields with higher dimensionality, are read directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants