Skip to content
GitLab
Projects Groups Snippets
  • /
  • 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 224
    • Issues 224
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

On Monday, 27th March 9 a.m., the user backend of GitLab will get a reconfiguration. A new login to the web interface may be necessary.

  • nomad-labnomad-lab
  • nomad-FAIRnomad-FAIR
  • Issues
  • #366
Closed
Open
Issue created Jul 01, 2020 by Markus Scheidgen@mscheidgOwner

Bad DOS value normalization

We assume that VASP, Exciting, and FHI-aims are all producing dos values a like. Which does not seem to be true. In the encyclopedia this discussion exists: encyclopedia-gui#111 , it highlights all the differences. Therefore, also the normalized value is wrong, because the normalizer is applying the same treatment for all codes. Does the encyclopdia pre-processing/normalizer do something different?

@mkuban, @himanel1, @temokmx, maybe you have more input on that.

@mkuban, if you find some examples that highlight this, please add it to the discussion here!

Assignee
Assign to
Time tracking