Repository navigation
Suggestions for neutrino data on ObsCore note #1
Description
After a first walk through the ObsCore standard and the HEIG extension we put together the following input to the note:
-
a table of the ObsCore fields and their interpretation for neutrino data here in the Wiki
-
An implementation of the first use case in a containerized version of our DACHS server, with container and implementation available here.
-
on the UCD discussion, the following open issues were added: #42, #41, #44, #45
From this, we will make suggestions on the update of the HEIG note before creating a pull request. This issue serves to collect notes on suggested changes.
UCDs
- Particles: phys.particle.muon, phys.particle.tau, phys.particle.neutrino, phys.particle.pdgid
Activity
shallmann commentedon Apr 24, 2026
As pointed out in the call,
phys.particle.neutrinoalready exists in the standart UCDs. I put a link here for completeness:https://ivoa.net/documents/UCD1+/
From the discussion:
phys.particle.pdgidactually would make sense for us, at least for sims (IRFs)Merge pull request #1 from ivoa/main
loumir commentedon May 20, 2026
I have read the definition of PGDID from: https://github.com/scikit-hep/particle
" PDG ID literals provide (PDGID class) aliases for all particles loaded, with easily recognisable names. "
if you need to describe a variable ( or column) with a PDGID, the corresponding UCD will be "meta.id;phys.particle" . I suppose that your column name or variable name will already mention it is a pgdid .
A naïve question from a non-expert :
Is the "pgdid" used as a standard in the whole domain of particle physics ?