Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • nomad-FAIR nomad-FAIR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 115
    • Issues 115
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nomad-lab
  • nomad-FAIRnomad-FAIR
  • Issues
  • #534

Closed
Open
Created Apr 22, 2021 by Markus Scheidgen@mscheidgOwner

Reduce the spectra metainfo complexity

The spectra metainfo (used by eels and xps parser, on branch experiment, 205aab5a) in nomad.datamodel.metainfo.common_experimental defines too many details. We should try a different approach. It is basically always a set of channels (counts, energies, etc.), which are arrays with the same number of values. Currently, it defines a quantity for all possible channels (probably not exhaustive). We should reduce this to the most common channels (count, energy) and provide a higher dimensional quantity to store all other channels. The description for those other channels (name, id, unit) could be stored in a repeating sub section.

Assignee
Assign to
Time tracking