Skip to content

GitLab

  • Menu
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 139
    • Issues 139
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 15
    • Merge requests 15
  • 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
  • #478

Closed
Open
Created Jan 20, 2021 by Markus Scheidgen@mscheidgOwner

Different PBC in new vs old crystal parser

The new crystal parsers assigns (true, true, true) to many (or all) calcs' periodic boundary conditions, where the old parser was assigning (false, false, false). As a result many calcs become bulk or without system type that have been molecules on the old system.

You can compare the production (https://nomad-lab.eu/prod/rae/gui/search?visualization=system&dft.code_name=Crystal) with the reprocessing NOMAD installation (https://nomad-lab.eu/prod/rae/reprocess/gui/search?dft.code_name=Crystal&visualization=system)

An example calc where you see the different PBC: 6GPEE6tsj4sVMHkjuhboMyi5f_9u

@himanel1 could you investigate, it the new behaviour is indeed intended/correct?

Assignee
Assign to
Time tracking