Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • est est
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • workflow
  • ewoksapps
  • estest
  • Issues
  • #7
Closed
Open
Issue created Jul 01, 2019 by payno@paynoOwner

Move xas_obj to hdf5 container

All the treatment should be stored in a hdf5 with one NXProcess for each treatment. With input, output, order and configuration of the process. It should at least be an option. We could have something like

xas_obj.link_to_h5(h5file)

If a XASObject is link to an hdf5 file then the process function should store input, output as NXProcess.

Edited Jul 11, 2019 by payno
Assignee
Assign to
Time tracking