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 110
    • Issues 110
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • 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
  • #557

Closed
Open
Created Jun 08, 2021 by Alvin Noe Ladines@ladinesaDeveloper

Metainfo root sections

This is a sub issue of the main issue #419 (closed) to discuss the root section structure.

We should decide on the structure of the metainfo root section to ensure consistency in defining sub sections. At the moment, we have under section_run which I suppose should correspond to computational entries. For flexility and future inclusion of other codes other than DFT, I suggest the following structure:

  • Computational (previously Run)

    • HartreeFock
    • ConfigurationInteraction
    • PerturbationTheory
    • DensityFunctionalTheory
    • TightBinding
    • EmpiricalPotentials
    • ...

Allowing sub section for various computational methods should avoid inconsistency in the definition of quantities for example the energies which are of course different for each method. What do you think @himanel1 and @mscheidg

Edited Jun 08, 2021 by Alvin Noe Ladines
Assignee
Assign to
Time tracking