Skip to content

change pdgid definition // fix some typos and references in the neutr… #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
shallmann wants to merge 1 commit into
base: main
Choose a base branch
from
+6 −6
Open

change pdgid definition // fix some typos and references in the neutr… #55

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion HighEnergyObsCoreExt.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -535,7 +535,7 @@ \subsubsection{Physical Quantities}

The messengers for \gls{HEA} observations may include particles other than the ones currently described in the UCD list. Because some instruments can now distinguish electrons from positrons\footnote{For example, the Fermi-LAT instrument.}, as well antiprotons from protons\footnote{For example, the AMS-2 experiment.}, we also propose to add {\em phys.particle.positron\/} and {\em phys.particle.antiproton\/}, as well as {\em phys.particle.cosmicray\/} and unify them all under the {\em phys.particle\/} UCD hierarchy.

For particle detectors, a wide range of different particles might have to be described. As is customary in particle physics, we propose to facilitate the use of the Particle Data Group Identifier\footnote{see \url{https://www.phy.bnl.gov/twister/bee/particles/}} as reference for any particle, describing {\em e.g.\/}, $\nu_{\tau}$ and $\bar{\nu}_{\tau}$ as {\em phys.particle.pdgid16\/} and {\em phys.particle.pdgid18\/} respectively.
For particle detectors, a wide range of different particles might have to be described. As is customary in particle physics, we propose to facilitate the use of the Particle Data Group Identifier\footnote{see \url{https://www.phy.bnl.gov/twister/bee/particles/}} as reference for any particle, describing {\em e.g.\/}, $\nu_{\tau}$ and $\bar{\nu}_{\tau}$ as {\em phys.particle.pdgid+16\/} and {\em phys.particle.pdgid-16\/} respectively.

One should note that electrons are denoted by the UCD {\em phys.electron\/} in the current version of the UCD list \citep{2024ivoa.spec.1218C} and are inappropriately not grouped under the {\em phys.particle\/} hierarchy. This causes some inconsistencies that could be solved by marking {\em phys.electron\/} (and {\em phys.electron.degen\/}) as obsolete or not recommended, and adding the term {\em phys.particle.electron\/} to the UCD list.

Expand Down
10 changes: 5 additions & 5 deletions UseCases.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -305,14 +305,14 @@ \subsubsection{Use Case --- Search for all ANTARES neutrino events for a given d
SELECT * FROM ivoa.obscore
NATURAL JOIN ivoa.obscore_hea
WHERE
(CONTAINS(POINT(s_ra, s_dec), CIRCLE, 98.24, 5.81, 5.0) = 1)
(CONTAINS(POINT(s_ra, s_dec), CIRCLE(98.24, 5.81, 5.0)) = 1)
AND (dataproduct_type IN ('event-bundle', 'event-list', 'response-function'))
AND (obs_collection = 'ANTARES-2017-PS')
\end{verbatim}

\subsubsection{Use Case --- Retrieve the instrument response functions for a combined KM3NeT \& CTA sensitivity study for a point source.}

{\em To study the combined future sensitivity for a source that is expected to emit gamma rays and neutrinos, retrieve general IRFs from both instruments to perform a sensitivity study for a source like Vela X as in \textbf{arXiv:2309.03007}, considering only track-like events due to their better angular resolution.}
{\em To study the combined future sensitivity for a source that is expected to emit gamma rays and neutrinos, retrieve general IRFs from both instruments to perform a sensitivity study for a source like Vela X as in \textbf{\hyperref[https://doi.org/10.1140/epjc/s10052-023-12279-z]{Eur. Phys. J. C. 84, 112 (2024)}}, considering only track-like events due to their better angular resolution.}

\medskip
\noindent Find all IRF datasets satisfying:
Expand All @@ -328,7 +328,7 @@ \subsubsection{Use Case --- Retrieve the instrument response functions for a com
SELECT * FROM ivoa.obscore
NATURAL JOIN ivoa.obscore_hea
WHERE
(CONTAINS(POINT(s_ra, s_dec), CIRCLE, 0.8, -45.19, 5.0) = 1)
(CONTAINS(POINT(s_ra, s_dec), CIRCLE(0.8, -45.19, 5.0)) = 1)
AND (dataproduct_type = 'response-function'))
AND (instrument_name = '%ARCA%')
AND (t_min >= 61406)
Expand Down Expand Up @@ -366,7 +366,7 @@ \subsubsection{Use Case --- Calculate the probability for a source class to be e
\noindent Find all neutrino datasets satisfying:
\begin{enumerate}[(i)]
\item dataproduct\_type = ``response-function'',
\item messenger contains ``pdgid-16'' or ``pdgid-18'',
\item messenger contains ``pdgid-16'' or ``pdgid+16'',
\item obs\_mode = ``wide-array'',
\item analysis\_mode = ``pointsource''.
\end{enumerate}
Expand All @@ -376,7 +376,7 @@ \subsubsection{Use Case --- Calculate the probability for a source class to be e
NATURAL JOIN ivoa.obscore_hea
WHERE
(dataproduct_type = 'response-function')
AND (messenger = '%pdgid-16%' OR messenger = '%pdgid-18%')
AND (messenger = '%pdgid-16%' OR messenger = '%pdgid+16%')
AND (obs_mode LIKE '%wide-array%')
AND (analysis_mode LIKE '%pointsource%')
\end{verbatim}
Expand Down