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 142
    • Issues 142
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 24
    • Merge requests 24
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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
  • nomad-lab
  • nomad-FAIRnomad-FAIR
  • Issues
  • #778
Closed
Open
Created Mar 31, 2022 by Lauri Himanen@himanel1Maintainer

Plug-and-play metainfo not working on v1.1.0

When trying to run the infrastructure for v1.1.0 (eb5f18f7), the dynamically imported ElasticSearch extensions from EELSDBParser (results.properties.spectroscopy.eels) are not working.

When launching the app with no ES indices, the mapping does not contain the EELS quantities, and also the API will fail upon trying to fetch this information. The parsing of EELS entries goes through fine.

This issue is also preventing the addition of the nexus ES annotations, as they would rely on the same plug-and-play metainfo extension mechanism that EELSDBParser is using.

Problem seems to be in nomad/parsing/parsers.py, where the EELSDBParser is no longer imported at the top, but only imported dynamically later through MatchingParserInterface.mainfile_parser.

Assignee
Assign to
Time tracking