Skip to content

Dakota issue 10: define HDF5 and multi-call safety #20

Description

@JavierGOrdonnez

Parent epic: #12
Source: ITISFoundation/mmux_python#3

Current status: Not addressed / intentionally avoided. The package has no HDF5 handling or multi-call safety contract.

Acceptance criteria:

  • Decide whether HDF5 is unsupported, isolated per run, or supported with a safe ownership model.
  • Document the decision and add a regression test if support is introduced.
  • Ensure concurrent calls cannot overwrite shared HDF5 artifacts.

Metadata

Metadata

Assignees

No one assigned

    Labels

    epic:dakota-issuesChild of epic #12 (Dakota technical issues from mmux_python#3)status:not-startedNot addressed yettriage:needs-testingmmux_python#3 triage category E - potential issue, needs testing

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions