Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • Project Juggler Project Juggler
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 23
    • Merge requests 23
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • EIC
  • Project JugglerProject Juggler
  • Issues
  • #104
Closed
Open
Issue created Aug 17, 2022 by Christopher Dilks@c.dilksDeveloper

Incomplete metadata from `PodioOutput`

Calling

podio::EventStore::get<edm4hep::MCParticleCollection>("MCParticles");

using output of an algorithm where MCParticles is one of the collections that was just passed from input to output, fails with the claim that the collection MCParticles is not found. This same algorithm also produces a new collection DRICHPID, and the following call is successful:

podio::EventStore::get<eicd::CherenkovParticleIDCollection>("DRICHPID");

Despite these differences, both collections are in the store, according to podio::EventStore::getCollectionIDTable()->print();. The underlying issue is likely incomplete metadata, in particular the CollectionTypeInfo branch.

Assignee
Assign to
Time tracking