Skip to content
GitLab
Projects Groups Topics 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
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 245
    • Issues 245
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 46
    • Merge requests 46
  • 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, June 12, 2023, from 9.00 to 10.00 am there will be a maintenance with a short downtime of the GitLab service.

  • nomad-labnomad-lab
  • nomad-FAIRnomad-FAIR
  • Issues
  • #832
Closed
Open
Issue created May 12, 2022 by Lauri Himanen@himanel1Maintainer8 of 8 checklist items completed8/8 checklist items

Improved support for complex structural topologies

Currently, materials are classified using a very simple labeling (bulk, 2D, surface, etc.) and any further topological data is not supported by the search or shown in the overview. As we are now adding support for MD topologies (given by the parser) and automatically detected topologies (through MatID and the work Thea is pursuing), we need to start thinking about how we deal with much more complex topological data. This issue deals with the first step of handling topological data that focuses on topologies extracted from MD and displaying them in the overview page.

Metainfo:

  • Full topologies need to have a place in the archive (implemented by @jrudz).
  • Simplified/searchable version of the topology needs metainfo in the results.material.topology

Parsing:

  • The MD parsers should be able to output the original topologies (implemented by @jrudz).

Normalization:

  • ResultsNormalizer needs to create the topology according to AtomsGroup information stored in the run.

Overview:

  • A new type of material card for entries with a topology:
    • Support for browsing through the topology
    • Meaningful visualization of the selected part of the topology (requires significant changes in the
    • Display information about different aspects of the topology within tabs.
Edited Jun 01, 2022 by Lauri Himanen
Assignee
Assign to
Time tracking