From f2bbf9fbeeeec6c2922b343e12cac29e1cee5e8d Mon Sep 17 00:00:00 2001 From: Jutta Schnabel Date: Wed, 4 Feb 2026 07:53:22 +0100 Subject: [PATCH 01/23] tentatively adding two use cases from which to develop the neutrino requirements --- UseCases.tex | 43 +++++++++++++++++++++++++++++++++++++------ 1 file changed, 37 insertions(+), 6 deletions(-) diff --git a/UseCases.tex b/UseCases.tex index e68e72f..07b84ad 100644 --- a/UseCases.tex +++ b/UseCases.tex @@ -262,6 +262,27 @@ \subsubsection{Use Case --- Get all the \glspl{IRF} for a given CTAO observation \end{verbatim} +\subsubsection{Use Case --- Search for all ANTARES neutrino events in the direction of the Crab nebula} + +{\em Identify all neutrino events observed by ANTARES in a search cone around the Crab nebula.\/} + +\medskip +\noindent Find all datasets satisfying: +\begin{enumerate}[(i)] + \item dataproduct\_type = ``'', + \item dataproduct\_subtype = ``'', + \item obs\_collection = ``ANTARES'', + \item tmin $\geq 62502$ ({\em i.e.\/}, 2010-01-01), + \item tmax $\leq 62866$ ({\em i.e.\/}, 2020-12-31), + \item target\_name = ``Crab''. +\end{enumerate} + +\begin{verbatim} +SELECT * FROM ivoa.obscore +NATURAL JOIN ivoa.obscore_hea +WHERE +\end{verbatim} + \subsection{Advanced Data Products} \subsubsection{Use Case --- Search for Chandra Source Catalog position error MCMC draws for X-ray detections in the vicinity of Gaia DR3 486718823701242368} @@ -361,10 +382,20 @@ \subsubsection{Use Case --- Search for the CTAO flux light curves of PKS 2155-30 SELECT * FROM ivoa.obscore NATURAL JOIN ivoa.obscore_hea WHERE -(dataproduct_type = 'timeseries') -AND (dataproduct_subtype = 'flux') -AND (obs_collection = 'CTAO-DR1') -AND (target_name = 'PKS 2155-304') -AND (tmin >= 62502) -AND (tmax <= 62866) +\end{verbatim} + +\subsubsection{Use Case --- Search for the \glspl{IRF} for a given direction and observation duration regardless of a neutrino event observation} + +{\em With the detector taking data, a given search might result in a non-observation of neutrinos although the detector could have observed events. The sensitivity of the detector towards a given neutrino flux is then calculated from IRFs to set an upper limit on a neutrino flux model.\/} + +\medskip +\noindent Find all datasets satisfying: +\begin{enumerate}[(i)] + \item dataproduct\_type = , +\end{enumerate} + +\begin{verbatim} +SELECT * FROM ivoa.obscore +NATURAL JOIN ivoa.obscore_hea +WHERE \end{verbatim} From 1ee1f68d16ae312e20dc664f6718ca6f5408e056 Mon Sep 17 00:00:00 2001 From: Jutta Schnabel Date: Fri, 20 Mar 2026 11:00:30 +0100 Subject: [PATCH 02/23] Adding first idea of neutrino use cases --- UseCases.tex | 84 +++++++++++++++++++++++++++++++++++++++++++++------- 1 file changed, 74 insertions(+), 10 deletions(-) diff --git a/UseCases.tex b/UseCases.tex index 07b84ad..59a454e 100644 --- a/UseCases.tex +++ b/UseCases.tex @@ -261,26 +261,90 @@ \subsubsection{Use Case --- Get all the \glspl{IRF} for a given CTAO observation AND (obs_collection = 'CTAO-DR1') \end{verbatim} +\subsubsection{Use Case --- Search for all ANTARES neutrino events in the direction of a point source} -\subsubsection{Use Case --- Search for all ANTARES neutrino events in the direction of the Crab nebula} +{\em Using the ANTARES 2007-2017 point source data set, retrieve all events, background estimate, and detector acceptance to calculate the neutrino flux from that point source as in \textit{G. Illuminati for the ANTARES Collaboration, PoS(ICRC2019)920}./} -{\em Identify all neutrino events observed by ANTARES in a search cone around the Crab nebula.\/} +\medskip +\noindent Find all ANTARES datasets satisfying: +\begin{enumerate}[(i)] +\item Position inside 2 degrees from (266.4168,−29.0078), +\item dataproduct_type = event-list'' or bkgrate'' or aeff'', \item obs\_collection = ANTARES-2017-PS'', +\item o_ucd contains ``phys.neutrino''. +\end{enumerate} + +\begin{verbatim} +SELECT * FROM ivoa.obscore +NATURAL JOIN ivoa.obscore_hea +WHERE +(CONTAINS(POINT(s_ra, s_dec), CIRCLE, 266.4168, -29.0078, 2.0) = 1) +AND (dataproduct_type IN ('event-list', 'bkgrate', 'aeff')) +AND (obs_collection = 'ANTARES-2017-PS') +AND (o_ucd LIKE '%phys.neutrino%') +\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 sensitivity for a source that is expected to emit gamma rays and neutrinos, retrieve the IRFs from both instruments to perform a sensitivity study as in \textit{arXiv:2309.03007}./} \medskip -\noindent Find all datasets satisfying: +\noindent Find all IRF datasets satisfying: \begin{enumerate}[(i)] - \item dataproduct\_type = ``'', - \item dataproduct\_subtype = ``'', - \item obs\_collection = ``ANTARES'', - \item tmin $\geq 62502$ ({\em i.e.\/}, 2010-01-01), - \item tmax $\leq 62866$ ({\em i.e.\/}, 2020-12-31), - \item target\_name = ``Crab''. +\item Position inside 5 degrees from (18h 36m, +04d 00m), +\item dataproduct_type = aeff'' or edisp'' or psf'', \item obs\_collection IN (KM3NeT-ARCA-DR1'', ``CTAO-DR1''). \end{enumerate} \begin{verbatim} SELECT * FROM ivoa.obscore -NATURAL JOIN ivoa.obscore_hea +NATURAL JOIN ivoa.obscore_hea WHERE +(CONTAINS(POINT(s_ra, s_dec), CIRCLE, 279.0, 4.0, 5.0) = 1) +AND (dataproduct_type IN ('aeff', 'edisp', 'psf')) +AND (obs_collection IN ('KM3NeT-ARCA-DR1', 'CTAO-DR1')) +\end{verbatim} + +\subsubsection{Use Case --- Search for neutrino events and IRFs for a point source for all available neutrino data.} + +{\em Identify all neutrino events in a search cone around a point source to performed a combined neutrino flux study./} + +\medskip +\noindent Find all neutrino datasets satisfying: +\begin{enumerate}[(i)] +\item Position inside 1 degree from (83.633, 22.014), +\item o_ucd contains phys.neutrino'', \item dataproduct\_type = event-bundle'' or event-list'', \item access\_format = datalink''. +\end{enumerate} + +\begin{verbatim} +SELECT * FROM ivoa.obscore +NATURAL JOIN ivoa.obscore_hea +WHERE +(CONTAINS(POINT(s_ra, s_dec), CIRCLE, 83.633, 22.014, 1.0) = 1) +AND (o_ucd LIKE '%phys.neutrino%') +AND (dataproduct_type IN ('event-bundle', 'event-list')) +AND (access_format LIKE '%datalink%') +\end{verbatim} + +\subsubsection{Use Case --- Retrieve neutrino events and IRFs to calculate the neutrino flux from the Fermi Bubbles.} + +{\em Identify all neutrino events in the region of the Fermi Bubbles and calculate the sensitivity as in \textit{arXiv:1308.5260}./} + +\medskip +\noindent Find all neutrino datasets satisfying: +\begin{enumerate}[(i)] +\item s_region intersects with a polygon defining the Fermi Bubbles, +\item dataproduct_type = event-bundle'', \item o\_ucd contains phys.neutrino'', +\item energy_min >= 1.6e−10 (approx. 1 GeV). +\end{enumerate} + +\begin{verbatim} +SELECT * FROM ivoa.obscore +NATURAL JOIN ivoa.obscore_hea +WHERE +(INTERSECTS(s_region, +POLYGON(0.0, 0.0, 10.0, 20.0, -10.0, 20.0, 0.0, 50.0)) = 1) +AND (dataproduct_type = 'event-bundle') +AND (o_ucd LIKE '%phys.neutrino%') +AND (energy_min >= 1.6e-10) \end{verbatim} \subsection{Advanced Data Products} From d7c79d719b4a785a1eb7493d02505ee5efdc0d7a Mon Sep 17 00:00:00 2001 From: Jutta Schnabel Date: Fri, 20 Mar 2026 11:06:38 +0100 Subject: [PATCH 03/23] cosmetic changes --- UseCases.tex | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/UseCases.tex b/UseCases.tex index 59a454e..1bf9d6d 100644 --- a/UseCases.tex +++ b/UseCases.tex @@ -268,9 +268,10 @@ \subsubsection{Use Case --- Search for all ANTARES neutrino events in the direct \medskip \noindent Find all ANTARES datasets satisfying: \begin{enumerate}[(i)] -\item Position inside 2 degrees from (266.4168,−29.0078), -\item dataproduct_type = event-list'' or bkgrate'' or aeff'', \item obs\_collection = ANTARES-2017-PS'', -\item o_ucd contains ``phys.neutrino''. + \item Position inside 2 degrees from (266.4168,−29.0078), + \item dataproduct_type = event-list'' or bkgrate'' or aeff'', + \item obs\_collection = ANTARES-2007-2017'', + \item o_ucd contains ``phys.neutrino''. \end{enumerate} \begin{verbatim} @@ -290,8 +291,9 @@ \subsubsection{Use Case --- Retrieve the instrument response functions for a com \medskip \noindent Find all IRF datasets satisfying: \begin{enumerate}[(i)] -\item Position inside 5 degrees from (18h 36m, +04d 00m), -\item dataproduct_type = aeff'' or edisp'' or psf'', \item obs\_collection IN (KM3NeT-ARCA-DR1'', ``CTAO-DR1''). + \item Position inside 5 degrees from (18h 36m, +04d 00m), + \item dataproduct_type = aeff'' or edisp'' or psf'', + \item obs\_collection IN (KM3NeT-ARCA-DR1'', ``CTAO-DR1''). \end{enumerate} \begin{verbatim} @@ -310,8 +312,10 @@ \subsubsection{Use Case --- Search for neutrino events and IRFs for a point sour \medskip \noindent Find all neutrino datasets satisfying: \begin{enumerate}[(i)] -\item Position inside 1 degree from (83.633, 22.014), -\item o_ucd contains phys.neutrino'', \item dataproduct\_type = event-bundle'' or event-list'', \item access\_format = datalink''. + \item Position inside 1 degree from (83.633, 22.014), + \item o_ucd contains phys.neutrino'', + \item dataproduct\_type = event-bundle'' or event-list'', + \item access\_format = datalink''. \end{enumerate} \begin{verbatim} @@ -331,9 +335,9 @@ \subsubsection{Use Case --- Retrieve neutrino events and IRFs to calculate the n \medskip \noindent Find all neutrino datasets satisfying: \begin{enumerate}[(i)] -\item s_region intersects with a polygon defining the Fermi Bubbles, -\item dataproduct_type = event-bundle'', \item o\_ucd contains phys.neutrino'', -\item energy_min >= 1.6e−10 (approx. 1 GeV). + \item s_region intersects with a polygon defining the Fermi Bubbles, + \item dataproduct_type = event-bundle'', \item o\_ucd contains phys.neutrino'', + \item energy_min >= 1.6e−10 (approx. 1 GeV). \end{enumerate} \begin{verbatim} From 6880f308172fc16ca028c94c8e985e4685fe63a0 Mon Sep 17 00:00:00 2001 From: Jutta Schnabel Date: Fri, 20 Mar 2026 15:52:07 +0100 Subject: [PATCH 04/23] minor edits in quotes --- UseCases.tex | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/UseCases.tex b/UseCases.tex index 1bf9d6d..b72a079 100644 --- a/UseCases.tex +++ b/UseCases.tex @@ -269,7 +269,7 @@ \subsubsection{Use Case --- Search for all ANTARES neutrino events in the direct \noindent Find all ANTARES datasets satisfying: \begin{enumerate}[(i)] \item Position inside 2 degrees from (266.4168,−29.0078), - \item dataproduct_type = event-list'' or bkgrate'' or aeff'', + \item dataproduct_type = ``event-list'' or ``bkgrate'' or ``aeff'', \item obs\_collection = ANTARES-2007-2017'', \item o_ucd contains ``phys.neutrino''. \end{enumerate} @@ -292,8 +292,8 @@ \subsubsection{Use Case --- Retrieve the instrument response functions for a com \noindent Find all IRF datasets satisfying: \begin{enumerate}[(i)] \item Position inside 5 degrees from (18h 36m, +04d 00m), - \item dataproduct_type = aeff'' or edisp'' or psf'', - \item obs\_collection IN (KM3NeT-ARCA-DR1'', ``CTAO-DR1''). + \item dataproduct_type = ``aeff'' or ``edisp'' or ``psf'', + \item obs\_collection IN (``KM3NeT-ARCA'', ``CTAO-DR1''). \end{enumerate} \begin{verbatim} @@ -314,8 +314,8 @@ \subsubsection{Use Case --- Search for neutrino events and IRFs for a point sour \begin{enumerate}[(i)] \item Position inside 1 degree from (83.633, 22.014), \item o_ucd contains phys.neutrino'', - \item dataproduct\_type = event-bundle'' or event-list'', - \item access\_format = datalink''. + \item dataproduct\_type = ``event-bundle'' or ``event-list'', + \item access\_format = ``datalink''. \end{enumerate} \begin{verbatim} @@ -336,8 +336,7 @@ \subsubsection{Use Case --- Retrieve neutrino events and IRFs to calculate the n \noindent Find all neutrino datasets satisfying: \begin{enumerate}[(i)] \item s_region intersects with a polygon defining the Fermi Bubbles, - \item dataproduct_type = event-bundle'', \item o\_ucd contains phys.neutrino'', - \item energy_min >= 1.6e−10 (approx. 1 GeV). + \item dataproduct_type = ``event-bundle'', \item o\_ucd contains ``phys.neutrino'' \end{enumerate} \begin{verbatim} @@ -348,7 +347,6 @@ \subsubsection{Use Case --- Retrieve neutrino events and IRFs to calculate the n POLYGON(0.0, 0.0, 10.0, 20.0, -10.0, 20.0, 0.0, 50.0)) = 1) AND (dataproduct_type = 'event-bundle') AND (o_ucd LIKE '%phys.neutrino%') -AND (energy_min >= 1.6e-10) \end{verbatim} \subsection{Advanced Data Products} From cc198edbac173a1852eb6eb0b94c702ef847d278 Mon Sep 17 00:00:00 2001 From: Mireille LOUYS <33840665+loumir@users.noreply.github.com> Date: Thu, 13 Nov 2025 18:14:14 +0100 Subject: [PATCH 05/23] building up vocabulary for response-function here is a draft for a VEP (vocabulary enhanced proposal) to be discussed and refined and submitted to the semantics group for approval. --- VEP-25_response-function.txt | 98 ++++++++++++++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 VEP-25_response-function.txt diff --git a/VEP-25_response-function.txt b/VEP-25_response-function.txt new file mode 100644 index 0000000..ed0d55a --- /dev/null +++ b/VEP-25_response-function.txt @@ -0,0 +1,98 @@ +Vocabulary: http://www.ivoa.net/rdf/response-type +Author: Mireille Louys for HEIG IG +Date: 2025-11-13 + +New Term: response-function +Action: Addition +Label: response-function +Description: +A data product type describing instrumental response functions for calibration and analysis. + +Relationships: response-function is a top level term. +Usually related to an event-list data product in high energy astrophysics. + +Used-in: Data sets made accessible via the Chandra CS2 catalog + +Rationale: +The distribution of event-list data in multi-messenger astronomy. +For example, Chandra primary products distributed via the Chandra +Data Archive include around half a dozen different types of products neces- +sary to analyse Chandra data (for example, L2 event-list, Aspect solution, +bad pixel map, spacecraft ephemeris, V&V Report). +For VHE gamma rays and neutrinos, the DL3 event-lists should manda- +torily be associated to their associated IRFs files. The links between the +event-list and these IRFs should be well defined in the event-bundle. +---------- +New Term: Point Spread Function +Action: Addition +Label: psf +Description: A dataset that records the probability density function of +spatial/angular spreading of incident photons from a point source caused +by the instrument (detector and/or mirror and/or analysis) + +Relationships: narrower than #response-function + +Used-in: CTA example? + + +---------- +New Term: Effective Area +Action: Addition +Label: aeff +Description: A dataset that records the “effective area” of a telescope +and/or instrument. The effective area is the geometric area +of the telescope and/or instrument reduced by efficiency factors +such as reflectivity and vignetting, among other effects + +Relationships: narrower than #response-function +---------- +New Term: Ancillary Response File +Action: Addition +Label: arf +Description: A dataset that records the +combined telescope/instru- +ment effective area and +detector quantum efficiency as +a function of energy + +Relationships: narrower than #response-function + +Used-in: XMM data products ? + +---------- +New Term: Background Rate +Action: Addition +Label: bkgrate +Description: A dataset that models the rate of residual events that are +not from the expected source type (e.g. for gamma-ray instrument it +measures residual non-gamma-ray events coming. + +Relationships: narrower than #response-function + +---------- +New Term: Energy Dispersion +Action: Addition +Label: edisp +Description: A dataset that records the +probability density of detecting an event with an energy estimator given the true +energy of the event. + +Relationships: narrower than #response-function + +Used-in: HESS data products ? + +---------- +New Term: Redistribution Matrix File +Action: Addition +Label: rmf +Description: A dataset that records the probability density function +mapping from energy space into detector pulse height (or position) space + +Relationships: narrower than #response-function + +Used-in: Chandra response data products ? + +Reference: +- IVOA Note: https://github.com/ivoa/HighEnergyObsCoreExt section 5.1.5 +- IVOA Note Virtual Observatory and High Energy Astrophysics Version 1.0 +https://ivoa.net/documents/Notes/VOHE/20241112/VOHE-Note-draft_1.0.pdf \ No newline at end of file From 348e55345c7041b8707551fa226d3e28fcc7a08a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Kh=C3=A9lifi?= Date: Fri, 24 Apr 2026 17:21:48 +0200 Subject: [PATCH 06/23] Update VEP-25_response-function.txt --- VEP-25_response-function.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VEP-25_response-function.txt b/VEP-25_response-function.txt index ed0d55a..a181dbb 100644 --- a/VEP-25_response-function.txt +++ b/VEP-25_response-function.txt @@ -42,7 +42,7 @@ Label: aeff Description: A dataset that records the “effective area” of a telescope and/or instrument. The effective area is the geometric area of the telescope and/or instrument reduced by efficiency factors -such as reflectivity and vignetting, among other effects +such as reflectivity and vignetting, cuts efficiency, among other effects Relationships: narrower than #response-function ---------- From 8165841b3a7d9cd438ac18a685aad0d55b476530 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Kh=C3=A9lifi?= Date: Fri, 24 Apr 2026 17:21:55 +0200 Subject: [PATCH 07/23] Update VEP-25_response-function.txt --- VEP-25_response-function.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VEP-25_response-function.txt b/VEP-25_response-function.txt index a181dbb..1e0e16e 100644 --- a/VEP-25_response-function.txt +++ b/VEP-25_response-function.txt @@ -65,7 +65,7 @@ Action: Addition Label: bkgrate Description: A dataset that models the rate of residual events that are not from the expected source type (e.g. for gamma-ray instrument it -measures residual non-gamma-ray events coming. +measures residual non-gamma-ray events coming). Relationships: narrower than #response-function From 313c295930eabdb69bd73c2ab0ce2179db18340a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Kh=C3=A9lifi?= Date: Fri, 24 Apr 2026 17:22:04 +0200 Subject: [PATCH 08/23] Update VEP-25_response-function.txt --- VEP-25_response-function.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VEP-25_response-function.txt b/VEP-25_response-function.txt index 1e0e16e..9a880c3 100644 --- a/VEP-25_response-function.txt +++ b/VEP-25_response-function.txt @@ -79,7 +79,7 @@ energy of the event. Relationships: narrower than #response-function -Used-in: HESS data products ? +Used-in: HESS test data release (https://doi.org/10.5281/zenodo.1421099) ---------- New Term: Redistribution Matrix File From f10fd3e61c021780f15be63b22b6b431d187cde5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Kh=C3=A9lifi?= Date: Fri, 24 Apr 2026 17:22:15 +0200 Subject: [PATCH 09/23] Update VEP-25_response-function.txt --- VEP-25_response-function.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/VEP-25_response-function.txt b/VEP-25_response-function.txt index 9a880c3..fedb0b7 100644 --- a/VEP-25_response-function.txt +++ b/VEP-25_response-function.txt @@ -69,6 +69,7 @@ measures residual non-gamma-ray events coming). Relationships: narrower than #response-function +Used-in: HESS test data release (https://doi.org/10.5281/zenodo.1421099) ---------- New Term: Energy Dispersion Action: Addition From fbf030e1d84caa636711ca3bfcdecd6da65dc076 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Kh=C3=A9lifi?= Date: Fri, 24 Apr 2026 17:22:26 +0200 Subject: [PATCH 10/23] Update VEP-25_response-function.txt --- VEP-25_response-function.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/VEP-25_response-function.txt b/VEP-25_response-function.txt index fedb0b7..596642c 100644 --- a/VEP-25_response-function.txt +++ b/VEP-25_response-function.txt @@ -45,6 +45,9 @@ of the telescope and/or instrument reduced by efficiency factors such as reflectivity and vignetting, cuts efficiency, among other effects Relationships: narrower than #response-function + +Used-in: HESS test data release (https://doi.org/10.5281/zenodo.1421099) + ---------- New Term: Ancillary Response File Action: Addition From 0fccfda1ba1ca04f185842e0029bb01655d828e5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Kh=C3=A9lifi?= Date: Fri, 24 Apr 2026 17:22:34 +0200 Subject: [PATCH 11/23] Update VEP-25_response-function.txt --- VEP-25_response-function.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VEP-25_response-function.txt b/VEP-25_response-function.txt index 596642c..95023e7 100644 --- a/VEP-25_response-function.txt +++ b/VEP-25_response-function.txt @@ -32,7 +32,7 @@ by the instrument (detector and/or mirror and/or analysis) Relationships: narrower than #response-function -Used-in: CTA example? +Used-in: HESS test data release (https://doi.org/10.5281/zenodo.1421099) ---------- From 3ad6145ee6fffac141493d3daed6e975da211c10 Mon Sep 17 00:00:00 2001 From: BONNAREL FRANCOIS Date: Tue, 3 Feb 2026 09:59:01 +0100 Subject: [PATCH 12/23] adding DataLink table example in UseCase --- UseCases.tex | 36 ++++++++++++++++++++++++++++++------ 1 file changed, 30 insertions(+), 6 deletions(-) diff --git a/UseCases.tex b/UseCases.tex index b72a079..e150f19 100644 --- a/UseCases.tex +++ b/UseCases.tex @@ -86,7 +86,7 @@ \subsubsection{Use Case --- Search for event bundles via DataLink that include C \item Target name = ``Cas A'' or position inside 2.5 arcmin from (350.8584, $+58.8113$), \item dataproduct\_type = ``event-bundle'', \item obs\_collection = ``VERITAS-DR1'', - \item access\_format = ``datalink''. + \item access\_format = ``application/fits''. \end{enumerate} \begin{verbatim} @@ -97,10 +97,10 @@ \subsubsection{Use Case --- Search for event bundles via DataLink that include C CONTAINS(POINT(s_ra, s_dec), CIRCLE, 350.8584, +58.8113, 0.042) = 2) AND (dataproduct_type = 'event-bundle') AND (obs_collection = 'VERITAS-DR1') -AND (access_format = ’application/x-votable+xml;content=datalink’) +AND (access_format = ’application/fits’) \end{verbatim} -Then, for each row of the output, we get the ``access\_url'' of the DataLink to provide access to the data. +Then, for each row of the output, we get the ``access\_url'' of the Obscore table to provide access to the data. \subsubsection{Use Case --- Search for event bundles that include Cas A for X-ray spectrophotometric evolution studies} @@ -128,12 +128,12 @@ \subsubsection{Use Case --- Search for event bundles that include Cas A for X-ra \subsubsection{Use Case --- Search for event lists and their \glspl{IRF} of CTAO South observations at energies above 10 TeV for blind search of PeVatrons from a data release using DataLink} -{\em Identify all event bundles (event lists and their associated \glspl{IRF}) taken by CTAO South that contains events above 10 TeV. Data taken with the Small Size Telescopes or Medium Size Telescopes can be then selected. \/} +{\em Identify all event lists and their associated \glspl{IRF} taken by CTAO South that contains events above 10 TeV. Data taken with the Small Size Telescopes or Medium Size Telescopes can be then selected. \/} \medskip \noindent Find all CTAO datasets satisfying: \begin{enumerate}[(i)] - \item dataproduct\_type = ``event-bundle'', + \item dataproduct\_type = ``event-list'', \item obs\_collection = ``CTAO-DR1'', \item access\_format = ``datalink'', \item instrument\_name contains ``CTAO-S'', @@ -144,7 +144,7 @@ \subsubsection{Use Case --- Search for event lists and their \glspl{IRF} of CTAO \begin{verbatim} SELECT * FROM ivoa.obscore NATURAL JOIN ivoa.obscore_hea -WHERE (dataproduct_type = 'event-bundle') +WHERE (dataproduct_type = 'event-list') AND (obs_collection = 'CTAO-DR1') AND (access_format = 'application/x-votable+xml;content=datalink') AND (instrument_name LIKE 'CTAO-S') @@ -179,6 +179,30 @@ \subsubsection{Use Case --- Search for event lists and their \glspl{IRF} of CTAO EVENT_FILE['OBS_ID'] = GET RAW['accessURL'] \end{verbatim} +Table \ref{tab:datalink1} displays an example of the DataLink response table attached to such an event-list discovery. Mandatory FIELDS service\_def and error\_messsage are omitted because they are empty + +\begin{landscape} +\begin{longtable}{|p{2.4cm}|p{3.3cm}|p{2.0cm}|p{2.4cm}|p{2.3cm}|p{2.4cm}|p{2.7cm}|} +\sptablerule +\textbf{ID} &\textbf{\footnotesize access\_url} &\textbf{\footnotesize semantics}&\textbf{\footnotesize description} &\textbf{\footnotesize content\_type} &\textbf{\footnotesize content\_length} &\textbf{\footnotesize content\_qualifier}\cr +\sptablerule +{\tiny ivo://xxx/yyy/zzz\#ttt} & {\tiny https://xxx.yyy/zzz/ttt1.ext1} & \#this & {\footnotesize event-list} {\tiny ivo://xxx/yyy/zzz\#ttt} & text/xml & 1000000 & event-list \cr +\sptablerule +{\tiny ivo://xxx/yyy/zzz\#ttt} & {\tiny https://xxx.yyy/zzz/ttt2.ext2} & \#calibration & {\footnotesize Effective AREA of event-list} {\tiny ivo://xxx/yyy/zzz\#ttt} & text/csv & 10000 & aeff \cr +\sptablerule +{\tiny ivo://xxx/yyy/zzz\#ttt} & {\tiny https://xxx.yyy/zzz/ttt3.ext3} & \#calibration & {\footnotesize Energy dispersion of event-list} {\tiny ivo://xxx/yyy/zzz\#ttt} & text/csv & 10000 & edisp \cr +\sptablerule +{\tiny ivo://xxx/yyy/zzz\#ttt} & {\tiny https://xxx.yyy/zzz/ttt4.ext4} & \#calibration & {\footnotesize Point spread function of event-list } {\tiny ivo://xxx/yyy/zzz\#ttt} & image/fits & 50000 & psf \cr +\sptablerule +{\tiny ivo://xxx/yyy/zzz\#ttt} & {\tiny https://xxx.yyy/zzz/ttt5.ext5} & \#calibration & {\footnotesize Background rate of event-list } {\tiny ivo://xxx/yyy/zzz\#ttt} & text/csv & 1000 & bkgrate \cr +\sptablerule + +\caption{DataLink response table attached to an event-list record in ObsCore.} + + +\label{tab:datalink1} +\end{longtable} +\end{landscape} \subsubsection{Use Case --- Search for spatially resolved spectropolarimetric observations of the Crab with spectral resolution R > 100} From 00cbf2104a15ea96e61969b0770021c0a49ca63d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20Bonnarel?= <52417996+Bonnarel@users.noreply.github.com> Date: Tue, 3 Feb 2026 18:11:17 +0100 Subject: [PATCH 13/23] Update UseCases.tex --- UseCases.tex | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/UseCases.tex b/UseCases.tex index e150f19..a2f8a26 100644 --- a/UseCases.tex +++ b/UseCases.tex @@ -179,7 +179,9 @@ \subsubsection{Use Case --- Search for event lists and their \glspl{IRF} of CTAO EVENT_FILE['OBS_ID'] = GET RAW['accessURL'] \end{verbatim} -Table \ref{tab:datalink1} displays an example of the DataLink response table attached to such an event-list discovery. Mandatory FIELDS service\_def and error\_messsage are omitted because they are empty +Table \ref{tab:datalink1} displays an example of the DataLink response table attached to such an event-list discovery. +The obs\_publisher\_did of the single discovered event-list is repeated in the ID column of the DataLink table. +Mandatory FIELDS service\_def and error\_messsage are omitted because they are empty \begin{landscape} \begin{longtable}{|p{2.4cm}|p{3.3cm}|p{2.0cm}|p{2.4cm}|p{2.3cm}|p{2.4cm}|p{2.7cm}|} From 7a0c48a18aac977b60e1ce448a3622a748e0022c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20Bonnarel?= <52417996+Bonnarel@users.noreply.github.com> Date: Thu, 5 Feb 2026 16:55:07 +0100 Subject: [PATCH 14/23] Update UseCases.tex change in description of the effective area in the DataLink table --- UseCases.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UseCases.tex b/UseCases.tex index a2f8a26..1887df3 100644 --- a/UseCases.tex +++ b/UseCases.tex @@ -190,7 +190,7 @@ \subsubsection{Use Case --- Search for event lists and their \glspl{IRF} of CTAO \sptablerule {\tiny ivo://xxx/yyy/zzz\#ttt} & {\tiny https://xxx.yyy/zzz/ttt1.ext1} & \#this & {\footnotesize event-list} {\tiny ivo://xxx/yyy/zzz\#ttt} & text/xml & 1000000 & event-list \cr \sptablerule -{\tiny ivo://xxx/yyy/zzz\#ttt} & {\tiny https://xxx.yyy/zzz/ttt2.ext2} & \#calibration & {\footnotesize Effective AREA of event-list} {\tiny ivo://xxx/yyy/zzz\#ttt} & text/csv & 10000 & aeff \cr +{\tiny ivo://xxx/yyy/zzz\#ttt} & {\tiny https://xxx.yyy/zzz/ttt2.ext2} & \#calibration & {\footnotesize Effective AREA of the telescope/instrument associated with the event-list} {\tiny ivo://xxx/yyy/zzz\#ttt} & text/csv & 10000 & aeff \cr \sptablerule {\tiny ivo://xxx/yyy/zzz\#ttt} & {\tiny https://xxx.yyy/zzz/ttt3.ext3} & \#calibration & {\footnotesize Energy dispersion of event-list} {\tiny ivo://xxx/yyy/zzz\#ttt} & text/csv & 10000 & edisp \cr \sptablerule From 2f9d5053235d8ab3fb88203fa23246988f316df5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Kh=C3=A9lifi?= Date: Fri, 24 Apr 2026 17:19:47 +0200 Subject: [PATCH 15/23] Update UseCases.tex --- UseCases.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UseCases.tex b/UseCases.tex index 1887df3..171668e 100644 --- a/UseCases.tex +++ b/UseCases.tex @@ -84,7 +84,7 @@ \subsubsection{Use Case --- Search for event bundles via DataLink that include C \noindent Find all VERITAS datasets satisfying: \begin{enumerate}[(i)] \item Target name = ``Cas A'' or position inside 2.5 arcmin from (350.8584, $+58.8113$), - \item dataproduct\_type = ``event-bundle'', + \item dataproduct\_type = ``event-list'', \item obs\_collection = ``VERITAS-DR1'', \item access\_format = ``application/fits''. \end{enumerate} From bc84e960815ef1a162754f8764676c8c9a792015 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Kh=C3=A9lifi?= Date: Fri, 24 Apr 2026 17:19:55 +0200 Subject: [PATCH 16/23] Update UseCases.tex --- UseCases.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UseCases.tex b/UseCases.tex index 171668e..53e5a28 100644 --- a/UseCases.tex +++ b/UseCases.tex @@ -86,7 +86,7 @@ \subsubsection{Use Case --- Search for event bundles via DataLink that include C \item Target name = ``Cas A'' or position inside 2.5 arcmin from (350.8584, $+58.8113$), \item dataproduct\_type = ``event-list'', \item obs\_collection = ``VERITAS-DR1'', - \item access\_format = ``application/fits''. + \item access\_format = ``datalink''. \end{enumerate} \begin{verbatim} From df1b15454e5e01f9e5b1aa88fe77baee4c55609c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Kh=C3=A9lifi?= Date: Fri, 24 Apr 2026 17:20:03 +0200 Subject: [PATCH 17/23] Update UseCases.tex --- UseCases.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UseCases.tex b/UseCases.tex index 53e5a28..b169096 100644 --- a/UseCases.tex +++ b/UseCases.tex @@ -97,7 +97,7 @@ \subsubsection{Use Case --- Search for event bundles via DataLink that include C CONTAINS(POINT(s_ra, s_dec), CIRCLE, 350.8584, +58.8113, 0.042) = 2) AND (dataproduct_type = 'event-bundle') AND (obs_collection = 'VERITAS-DR1') -AND (access_format = ’application/fits’) +AND (access_format = ’application/x-votable+xml;content=datalink’) \end{verbatim} Then, for each row of the output, we get the ``access\_url'' of the Obscore table to provide access to the data. From b27adf924bed0558b57c2858521697f630e26844 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Kh=C3=A9lifi?= Date: Fri, 24 Apr 2026 17:20:15 +0200 Subject: [PATCH 18/23] Update UseCases.tex --- UseCases.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UseCases.tex b/UseCases.tex index b169096..107859a 100644 --- a/UseCases.tex +++ b/UseCases.tex @@ -95,7 +95,7 @@ \subsubsection{Use Case --- Search for event bundles via DataLink that include C WHERE (target_name = 'Cas A' OR CONTAINS(POINT(s_ra, s_dec), CIRCLE, 350.8584, +58.8113, 0.042) = 2) -AND (dataproduct_type = 'event-bundle') +AND (dataproduct_type = 'event-list') AND (obs_collection = 'VERITAS-DR1') AND (access_format = ’application/x-votable+xml;content=datalink’) \end{verbatim} From 87437b8989574a26c64360b56d29bbdce9a92e01 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Kh=C3=A9lifi?= Date: Thu, 12 Feb 2026 15:51:11 +0100 Subject: [PATCH 19/23] Update --- HighEnergyObsCoreExt.tex | 27 ++++++++++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/HighEnergyObsCoreExt.tex b/HighEnergyObsCoreExt.tex index 13510de..afdc2ec 100644 --- a/HighEnergyObsCoreExt.tex +++ b/HighEnergyObsCoreExt.tex @@ -8,7 +8,20 @@ % interest groups. \ivoagroup{High Energy Interest Group} -\author{I. Evans, M. Servillat, B. Kh\'elifi, J. Evans, M. Louys, M. Kettenis, F. Bonnarel, L. Michel, C. Boisson, M. Cresitello-Dittmar, O. Ates, K. Kosack, and The IVOA High Energy Interest Group} +\author{ + I. Evans (SAO/CXC, \href{mailto:ievans@cfa.harvard.edu}{ievans@cfa.harvard.edu}, + M. Servillat (LUX - ObsParis, \href{mailto:mathieu.servillat@obspm.fr}{mathieu.servillat@obspm.fr}, + B. Khélifi (APC - Université de Paris/CNRS, \href{mailto:khelifi@in2p3.fr}{khelifi@in2p3.fr}), + J. Evans (SAO/CXC, \href{mailto:janet@cfa.harvard.edu}{janet@cfa.harvard.edu}), + M. Louys (CDS and ICube - Université de Strasbourg, \href{mailto:mireille.louys@unistra.fr}{mireille.louys@unistra.fr}), + M. Kettenis (Joint Institute for VLBI ERIC, \href{mailto:kettenis@jive.eu}{kettenis@jive.eu}), + F. Bonnarel (IVOA, \href{mailto:francois.bonnarel@gmail.com}{francois.bonnarel@gmail.com}), + L. Michel (SSC-XMM/SVOM - Strasbourg Observatory, \href{mailto:laurent.michel@astro.unistra.fr}{laurent.michel@astro.unistra.fr}), + C. Boisson (LUX - ObsParis, \href{mailto:catherine.boisson@obspm.fr}{catherine.boisson@obspm.fr}), + M. Cresitello-Dittmar (SAO/CXC, \href{mailto:mdittmar@cfa.harvard.edu}{mdittmar@cfa.harvard.edu}), + O. Ates (LUX - ObsParis, \href{mailto:onur.ates@obspm.fr}{onur.ates@obspm.fr}), + K. Kosack (IRFU - CEA/Université Paris-Saclay , \href{mailto:karl.kosack@cea.fr}{karl.kosack@cea.fr}), +} \editor{Ian Evans, Mathieu Servillat, Bruno Kh\'elifi, Janet Evans} @@ -27,6 +40,18 @@ \usepackage{amsmath} \usepackage{amssymb} \usepackage[nopostdot,style=super,nonumberlist,toc]{glossaries} +\usepackage{hyperref} +\usepackage{hyperref} +\usepackage{hyperref} +\usepackage{hyperref} +\usepackage{hyperref} +\usepackage{hyperref} +\usepackage{hyperref} +\usepackage{hyperref} +\usepackage{hyperref} +\usepackage{hyperref} +\usepackage{hyperref} +\usepackage{hyperref} \newacronym{IVOA}{IVOA}{International Virtual Observatory Alliance} \newacronym{VO}{VO}{Virtual Observatory} From 0eb806ec619a17221c3118e8d34975c20e771542 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bruno=20Kh=C3=A9lifi?= Date: Fri, 24 Apr 2026 17:04:42 +0200 Subject: [PATCH 20/23] Update --- HighEnergyObsCoreExt.tex | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/HighEnergyObsCoreExt.tex b/HighEnergyObsCoreExt.tex index afdc2ec..c6fcc47 100644 --- a/HighEnergyObsCoreExt.tex +++ b/HighEnergyObsCoreExt.tex @@ -10,17 +10,19 @@ \author{ I. Evans (SAO/CXC, \href{mailto:ievans@cfa.harvard.edu}{ievans@cfa.harvard.edu}, - M. Servillat (LUX - ObsParis, \href{mailto:mathieu.servillat@obspm.fr}{mathieu.servillat@obspm.fr}, - B. Khélifi (APC - Université de Paris/CNRS, \href{mailto:khelifi@in2p3.fr}{khelifi@in2p3.fr}), + M. Servillat (LUX - Observatoire de Paris, \href{mailto:mathieu.servillat@obspm.fr}{mathieu.servillat@obspm.fr}, + B. Khélifi (APC - Université de Paris Cité/CNRS, \href{mailto:khelifi@in2p3.fr}{khelifi@in2p3.fr}), J. Evans (SAO/CXC, \href{mailto:janet@cfa.harvard.edu}{janet@cfa.harvard.edu}), M. Louys (CDS and ICube - Université de Strasbourg, \href{mailto:mireille.louys@unistra.fr}{mireille.louys@unistra.fr}), M. Kettenis (Joint Institute for VLBI ERIC, \href{mailto:kettenis@jive.eu}{kettenis@jive.eu}), F. Bonnarel (IVOA, \href{mailto:francois.bonnarel@gmail.com}{francois.bonnarel@gmail.com}), L. Michel (SSC-XMM/SVOM - Strasbourg Observatory, \href{mailto:laurent.michel@astro.unistra.fr}{laurent.michel@astro.unistra.fr}), - C. Boisson (LUX - ObsParis, \href{mailto:catherine.boisson@obspm.fr}{catherine.boisson@obspm.fr}), + C. Boisson (LUX - Observatoire de Paris, \href{mailto:catherine.boisson@obspm.fr}{catherine.boisson@obspm.fr}), M. Cresitello-Dittmar (SAO/CXC, \href{mailto:mdittmar@cfa.harvard.edu}{mdittmar@cfa.harvard.edu}), O. Ates (LUX - ObsParis, \href{mailto:onur.ates@obspm.fr}{onur.ates@obspm.fr}), - K. Kosack (IRFU - CEA/Université Paris-Saclay , \href{mailto:karl.kosack@cea.fr}{karl.kosack@cea.fr}), + K. Kosack (IRFU - CEA/Université Paris-Saclay, \href{mailto:karl.kosack@cea.fr}{karl.kosack@cea.fr}), + J. Schnabel (ECAP, \href{mailto:jutta.schnabel@fau.de}{jutta.schnabel@fau.de}), + S. Hallmann (DESY Zeuthen, \href{mailto:steffen.hallmann@desy.de}{steffen.hallmann@desy.de}), } \editor{Ian Evans, Mathieu Servillat, Bruno Kh\'elifi, Janet Evans} From 5d67c5eb35b2fea66f86bb13d0547e2234f0b415 Mon Sep 17 00:00:00 2001 From: Jutta Schnabel Date: Fri, 15 May 2026 20:31:03 +0200 Subject: [PATCH 21/23] Update with neutrino use cases --- HighEnergyObsCoreExt.tex | 29 ++++++++-------- UseCases.tex | 74 +++++++++++++++++++++------------------- 2 files changed, 54 insertions(+), 49 deletions(-) diff --git a/HighEnergyObsCoreExt.tex b/HighEnergyObsCoreExt.tex index c6fcc47..1855c75 100644 --- a/HighEnergyObsCoreExt.tex +++ b/HighEnergyObsCoreExt.tex @@ -21,8 +21,8 @@ M. Cresitello-Dittmar (SAO/CXC, \href{mailto:mdittmar@cfa.harvard.edu}{mdittmar@cfa.harvard.edu}), O. Ates (LUX - ObsParis, \href{mailto:onur.ates@obspm.fr}{onur.ates@obspm.fr}), K. Kosack (IRFU - CEA/Université Paris-Saclay, \href{mailto:karl.kosack@cea.fr}{karl.kosack@cea.fr}), - J. Schnabel (ECAP, \href{mailto:jutta.schnabel@fau.de}{jutta.schnabel@fau.de}), - S. Hallmann (DESY Zeuthen, \href{mailto:steffen.hallmann@desy.de}{steffen.hallmann@desy.de}), + J. Schnabel (ECAP, FAU Erlangen-N{\"u}rnberg, \href{mailto:jutta.schnabel@fau.de}{jutta.schnabel@fau.de}), + S. Hallmann (ECAP, FAU Erlangen-N{\"u}rnberg, \href{mailto:steffen.hallmann@fau.de}{steffen.hallmann@desy.de}), } \editor{Ian Evans, Mathieu Servillat, Bruno Kh\'elifi, Janet Evans} @@ -136,11 +136,11 @@ \section{Introduction} \section{High Energy Astrophysics Data} -\gls{HEA} data include observations obtained using photon detectors covering X-ray (from $\sim$0.1 keV to $\sim$120 keV) through gamma-ray (from 120 keV up to $\gtrsim$ PeV) energies, as well as cosmic-ray and astrophysical neutrino ($\gtrsim$ TeV) detectors, or other messengers related to \gls{HEA} phenomena. The domain is now sufficiently mature to provide open data that are science-ready and work with open analysis tools ({\em e.g.\/}, CIAO \citep{2006SPIE.6270E..1VF} or Gammapy \citep{gammapy:2023}). The science output of the \gls{HEA} domain already includes advanced products such as images, cubes, spectra, and time series such as light curves and time-resolved spectra. Additional data products include fitted sky models with spatial, spectral, and/or temporal component(s), along with their confidence intervals or confidence limits, and covariance matrices. Finally, multiple \gls{HEA} instruments produce source catalogs and surveys covering up to the full the sky, which include maps of photon or particle flux, exposure, sensitivity, and aperture-photometry likelihood profiles. +\gls{HEA} data include observations obtained using photon detectors covering X-ray (from $\sim$0.1 keV to $\sim$120 keV) through gamma-ray (from 120 keV up to $\gtrsim$ PeV) energies, as well as cosmic-ray and astrophysical neutrino ($\gtrsim$ GeV) detectors, or other messengers related to \gls{HEA} phenomena. The domain is now sufficiently mature to provide open data that are science-ready and work with open analysis tools ({\em e.g.\/}, CIAO \citep{2006SPIE.6270E..1VF} or Gammapy \citep{gammapy:2023}). The science output of the \gls{HEA} domain already includes advanced products such as images, cubes, spectra, and time series such as light curves and time-resolved spectra. Additional data products include fitted sky models with spatial, spectral, and/or temporal component(s), along with their confidence intervals or confidence limits, and covariance matrices. Finally, multiple \gls{HEA} instruments produce source catalogs and surveys covering up to the full the sky, which include maps of photon or particle flux, exposure, sensitivity, and aperture-photometry likelihood profiles. -Observations of the universe at the highest energies are based on techniques that are radically different compared to the UV through radio domains. \gls{HEA} observatories\footnote{For example, Chandra, XMM-Newton, Fermi, H.E.S.S., MAGIC, VERITAS, HAWC, LHAASO, IceCube, Auger and soon CTAO and KM3NeT, SWGO.} are generally designed to detect particles ({\em e.g.\/}, individual photons, cosmic-rays, or neutrinos) with the ability to estimate multiple observables for those particles. These detection techniques all rely on {\em event counting\/}\footnote{As opposed to signal integrating ({\em e.g.\/}, using a detector that accumulates the total photon signal during an exposure).}, where an event has some probability of being due to the interaction of a particle from an astrophysical source with the detectors, but also has some probability of being from instrumental or background effects. The data corresponding to an event are first an instrumental signal, which is then calibrated and processed to estimate physical quantities such as a time of arrival, point-of-origin on the sky, and an energy proxy associated with the event. Several other intermediate and qualifying characteristics may be associated with a detected event, depending on the detection technique. The ensemble of events detected over a given time interval and spatial field-of-view is referred to as an {\em event list\/}, which we designate an {\bf event-list} in this document. +Observations of the universe at the highest energies are based on techniques that are radically different compared to the UV through radio domains. \gls{HEA} observatories\footnote{For example, Chandra, XMM-Newton, Fermi, H.E.S.S., MAGIC, VERITAS, HAWC, LHAASO, IceCube, ANTARES, Auger and soon CTAO and KM3NeT, SWGO.} are generally designed to detect particles ({\em e.g.\/}, individual photons, cosmic-rays, or neutrinos) with the ability to estimate multiple observables for those particles. These detection techniques all rely on {\em event counting\/}\footnote{As opposed to signal integrating ({\em e.g.\/}, using a detector that accumulates the total photon signal during an exposure).}, where an event has some probability of being due to the interaction of a particle from an astrophysical source with the detectors, but also has some probability of being from instrumental or background effects. The data corresponding to an event are first an instrumental signal, which is then calibrated and processed to estimate physical quantities such as a time of arrival, point-of-origin on the sky, and an energy proxy associated with the event. Several other intermediate and qualifying characteristics may be associated with a detected event, depending on the detection technique. The ensemble of events detected over a given time interval and spatial field-of-view is referred to as an {\em event list\/}, which we designate an {\bf event-list} in this document. -Though {\bf event-list}s {\em may\/} include estimators for calibrated physical values, they typically still have to be corrected for the photometric, spectral, spatial, and/or temporal responses of the telescope and detector combination to yield scientifically interpretable information. The mappings between physical measurements of the source properties and the observables are called Instrument Response Functions (\glspl{IRF}\footnote{We try to avoid using the term \gls{IRF} in a normative sense since historical usage across the broad \gls{HEA} community (and from facility to facility) varies. In some cases, \gls{IRF} has been used to mean specifically the X-ray product of the \gls{ARF} and \gls{RMF}, whereas in other cases \gls{IRF} has been used more generally to mean any instrumental response function regardless of type.}). Some \glspl{IRF} are probabilistic in nature\footnote{For example, the energy matrix is a probability density function.}, and in addition may depend on the set of events selected for analysis by the end user. They are usually not invertible, so methods such as forward-folding fitting (using source models with any combination of spectral, spatial, temporal, and/or polarization components that are estimated) are needed to estimate physical properties, such as the true flux of particles from a source arriving at the instrument, given the measured observable quantities. The \glspl{IRF} generally evolve over time with the instrument and observation characteristics, and are usually defined for a specific time interval and may be decomposed into a standard set of independent components (see \S~3.1.5 of \citep{2024ivoa.note.heig}), such as the spatial point-spread function or the energy-migration matrix, where each component may be stored or computed separately. Since both \glspl{IRF} and {\bf event-list}s are required to analyze \gls{HEA} data, some \gls{IVOA} standards must be modified in order to expose both of them via the \gls{VO}. +Though {\bf event-list}s {\em may\/} include estimators for calibrated physical values, they typically still have to be corrected for the photometric, spectral, spatial, and/or temporal responses of the telescope and detector combination to yield scientifically interpretable information. The mappings between physical measurements of the source properties and the observables are called Instrument Response Functions (\glspl{IRF}\footnote{We try to avoid using the term \gls{IRF} in a normative sense since historical usage across the broad \gls{HEA} community (and from facility to facility) varies. In some cases, \gls{IRF} has been used to mean specifically the X-ray product of the \gls{ARF} and \gls{RMF}, whereas in other cases \gls{IRF} has been used more generally to mean any instrumental response function regardless of type.}). Some \glspl{IRF} are probabilistic in nature\footnote{For example, the energy matrix is a probability density function.}, and in addition may depend on the set of events selected for analysis by the end user. They are usually not invertible, so methods such as forward-folding fitting (using source models with any combination of spectral, spatial, temporal, and/or polarization components that are estimated) are needed to estimate physical properties, such as the true flux of particles from a source arriving at the instrument, given the measured observable quantities. The \glspl{IRF} generally evolve over time with the instrument and observation characteristics, and are usually defined for a specific time interval and may be decomposed into a standard set of independent components (see \S~3.1.5 of \citep{2024ivoa.note.heig}), such as the spatial point-spread function or the energy-migration matrix or different messenger particle types, where each component may be stored or computed separately. Since both \glspl{IRF} and {\bf event-list}s are required to analyze \gls{HEA} data, some \gls{IVOA} standards must be modified in order to expose both of them via the \gls{VO}. In the following, the current ObsCore standard will be discussed in \S~\ref{sec:obscore}, focusing on attributes that need to be modified. Then, we propose the creation of a \gls{HEA} extension of ObsCore in \S~\ref{sec:obscoreext}, as some attributes are very specific to our domain. In these two sections, the discussion focuses on the attribute definitions rather on the attribute values. In \S~\ref{sec:voc}, enhancement of vocabulary is proposed for some ObsCore attributes, DataLink semantics, UCDs, and MIME-types. @@ -221,7 +221,7 @@ \subsection{{\em s\_ra\/}/{\em s\_dec}} We propose that the attributes {\em s\_ra\/}/{\em s\_dec\/} be redefined to be the ICRS right ascension and ICRS declination of ``a reference position (typically the center)'' of an observation on the sky, rather than the ICRS right ascension and ICRS declination of ``the center'' of the observation. For some facilities, the center (RA, Dec) may have a specific meaning (such as the location of the optical axis of the telescope), which often is not useful for advanced data products that may be extracted from a cut-out from the progenitor observation. Some facilities also allow an instrument to be displaced from the center of the focal plane, which means that the definition of ``the center'' of an observation may be unclear (especially when not tracking at sidereal rate or for facilities for which the PSF varies strongly across the telescope field of view). Since these cases effectively displace the observation field-of-view, ObsCore attributes such as {\em s\_fov\/} that are implicitly referenced to ({\em s\_ra\/}, {\em s\_dec\/}) will continue to behave as expected using the revised definition. -For non-pointing instruments (which may include all-sky instruments such as KM3NeT or HAWC), these fields are poorly defined (as is the case, generally for observations that are drift scans). For the time duration of the observation, one can compute an effective center position of the exposure skymap and the maximum radius of the covered area ({\em i.e.\/}, for an all-sky instrument this would be $2\pi\,\rm Sr$ solid angle in Alt/Az, which can be converted into a rotated area in RA/Dec). However, the utility of such a characterization depends on both the duration of the observation and the use case. +For non-pointing instruments (which may include all-sky instruments such as KM3NeT or HAWC), these fields are poorly defined (as is the case, generally for observations that are drift scans). For the time duration of the observation, one can compute an effective center position of the exposure skymap and the maximum radius of the covered area ({\em i.e.\/}, for an all-sky instrument this would be $2\pi\,\rm Sr$ solid angle in Alt/Az, which can be converted into a rotated area in RA/Dec). However, the utility of such a characterization depends on both the duration of the observation and the use case, and can be assumed to describe the center of the exposure skymap for typical aggregated datasets with observation duration spanning weeks up to years. \subsection{{\em s\_calib\_status}} @@ -229,7 +229,7 @@ \subsection{{\em s\_calib\_status}} Under the (reasonable) assumption that an end-user searching for {\bf event-bundle} datasets is typically querying based on the properties of the primary {\bf event-list}, we suggest that those values also be used for the {\bf event-bundle}. However, the data provider should ultimately decide which value best describes their {\bf event-bundle} dataset. -For dataset types that do not encode sky coordinates, we suggest setting this value to ``NULL''. +For dataset types that do not encode sky coordinates or observations without dedicated spacial axes like non-pointing observatories, we suggest setting this value to ``NULL''. \subsection{{\em t\_calib\_status}} @@ -288,9 +288,9 @@ \subsection{{\em t\_intervals}} \subsection{{\em energy\_min\/}/{\em energy\_max\/}} -The existing attributes {\em em\_min\/} and {\em em\_max\/} that define the coverage of the spectral axis (defined as wavelength expressed in units of m) are not user friendly for \gls{HEA} where datasets are generally selected according to an energy range ({\em i.e.\/}, inverse wavelength) in units of eV (or scaled units of eV, for example keV, MeV, GeV, TeV, PeV). Unlike the radio domain where $\lambda = c/\nu$, where $c$ is an almost universally remembered physical constant, the conversion $\lambda = hc/E$ is not simple for the user to express. As the spectral range covered by \gls{HEA} data is many decades larger than for other wavebands, the accurate numerical representations of typical \gls{HEA} spectral ranges as {\em em\_min\/}/{\em em\_max\/} requires quantities with many digits of precision and exponents ranging from $\sim\!10^{-5}$--$10^{-22}$. Since specification of the spectral range is largely fundamental to data discovery in the \gls{HEA} regime, we propose to add attributes {\em energy\_min\/} and {\em energy\_max\/} that specify the minimum and maximum spectral range values in units of eV\null. Note that the sense of these attributes is {\em opposite\/} that of {\em em\_min\/} and {\em em\_max\/} because of the inverse wavelength relationship between energy and wavelength, so numerical comparisons must be transposed ({\em e.g.\/}, $E>E_{\rm thresh}$ becomes $\lambdaE_{\rm thresh}$ becomes $\lambda= 2032) +AND (event_type = ``track``) \end{verbatim} -\subsubsection{Use Case --- Search for neutrino events and IRFs for a point source for all available neutrino data.} +\subsubsection{Use Case --- Study the combined neutrino flux for the Galactic plane} -{\em Identify all neutrino events in a search cone around a point source to performed a combined neutrino flux study./} +{\em Identify all neutrino data sets in the region of the Galactic plane to perform a combined neutrino flux study extending a study like the IceCube \textbf{Observation of high-energy neutrinos from the Galactic plane. DOI: 10.1126/science.adc9818}.}, using event lists and IRFs of datasets optimized for the analysis of diffuse neutrino emission. \medskip \noindent Find all neutrino datasets satisfying: \begin{enumerate}[(i)] - \item Position inside 1 degree from (83.633, 22.014), - \item o_ucd contains phys.neutrino'', - \item dataproduct\_type = ``event-bundle'' or ``event-list'', - \item access\_format = ``datalink''. + \item messenger = ``neutrino'', + \item dataproduct\_type = ``event-bundle'', + \item analysis\_mode = ``diffuse'' \end{enumerate} +% diffuse \begin{verbatim} SELECT * FROM ivoa.obscore NATURAL JOIN ivoa.obscore_hea WHERE -(CONTAINS(POINT(s_ra, s_dec), CIRCLE, 83.633, 22.014, 1.0) = 1) -AND (o_ucd LIKE '%phys.neutrino%') -AND (dataproduct_type IN ('event-bundle', 'event-list')) -AND (access_format LIKE '%datalink%') +(dataproduct_type = 'event-bundle') +AND (messenger = '%neutrino%') +AND (analysis_mode = 'diffuse') \end{verbatim} -\subsubsection{Use Case --- Retrieve neutrino events and IRFs to calculate the neutrino flux from the Fermi Bubbles.} +\subsubsection{Use Case --- Calculate the probability for a source class to be emitters of tau neutrinos} -{\em Identify all neutrino events in the region of the Fermi Bubbles and calculate the sensitivity as in \textit{arXiv:1308.5260}./} +{\em Using a catalog of potential sources, calculate the probability of measuring a $\nu_{\tau}$ neutrino flux from a stacking of all sources of that type with 10 years of data taking with widely spaced, i.e. high energy detectors like ARCA.} \medskip \noindent Find all neutrino datasets satisfying: \begin{enumerate}[(i)] - \item s_region intersects with a polygon defining the Fermi Bubbles, - \item dataproduct_type = ``event-bundle'', \item o\_ucd contains ``phys.neutrino'' + \item dataproduct\_type = ``response-function'', + \item messenger contains ``pdgid16'' or ``pdgid18'', + \item obs\_mode = ``wide-array'' + \item analysis\_mode = ``pointsource'' \end{enumerate} \begin{verbatim} SELECT * FROM ivoa.obscore NATURAL JOIN ivoa.obscore_hea WHERE -(INTERSECTS(s_region, -POLYGON(0.0, 0.0, 10.0, 20.0, -10.0, 20.0, 0.0, 50.0)) = 1) -AND (dataproduct_type = 'event-bundle') -AND (o_ucd LIKE '%phys.neutrino%') +(dataproduct_type = 'response-function') +AND (messenger = '%pdgid16%' OR messenger = '%pdgid18%') +AND (obs_mode LIKE '%wide-array%') +AND (analysis_mode LIKE '%pointsource%') \end{verbatim} \subsection{Advanced Data Products} From 09e6e610028fe937fed453ed54468b5b6438feb7 Mon Sep 17 00:00:00 2001 From: Jutta Schnabel Date: Fri, 15 May 2026 20:35:47 +0200 Subject: [PATCH 22/23] removing VEP file --- VEP-25_response-function.txt | 102 ----------------------------------- 1 file changed, 102 deletions(-) delete mode 100644 VEP-25_response-function.txt diff --git a/VEP-25_response-function.txt b/VEP-25_response-function.txt deleted file mode 100644 index 95023e7..0000000 --- a/VEP-25_response-function.txt +++ /dev/null @@ -1,102 +0,0 @@ -Vocabulary: http://www.ivoa.net/rdf/response-type -Author: Mireille Louys for HEIG IG -Date: 2025-11-13 - -New Term: response-function -Action: Addition -Label: response-function -Description: -A data product type describing instrumental response functions for calibration and analysis. - -Relationships: response-function is a top level term. -Usually related to an event-list data product in high energy astrophysics. - -Used-in: Data sets made accessible via the Chandra CS2 catalog - -Rationale: -The distribution of event-list data in multi-messenger astronomy. -For example, Chandra primary products distributed via the Chandra -Data Archive include around half a dozen different types of products neces- -sary to analyse Chandra data (for example, L2 event-list, Aspect solution, -bad pixel map, spacecraft ephemeris, V&V Report). -For VHE gamma rays and neutrinos, the DL3 event-lists should manda- -torily be associated to their associated IRFs files. The links between the -event-list and these IRFs should be well defined in the event-bundle. ----------- -New Term: Point Spread Function -Action: Addition -Label: psf -Description: A dataset that records the probability density function of -spatial/angular spreading of incident photons from a point source caused -by the instrument (detector and/or mirror and/or analysis) - -Relationships: narrower than #response-function - -Used-in: HESS test data release (https://doi.org/10.5281/zenodo.1421099) - - ----------- -New Term: Effective Area -Action: Addition -Label: aeff -Description: A dataset that records the “effective area” of a telescope -and/or instrument. The effective area is the geometric area -of the telescope and/or instrument reduced by efficiency factors -such as reflectivity and vignetting, cuts efficiency, among other effects - -Relationships: narrower than #response-function - -Used-in: HESS test data release (https://doi.org/10.5281/zenodo.1421099) - ----------- -New Term: Ancillary Response File -Action: Addition -Label: arf -Description: A dataset that records the -combined telescope/instru- -ment effective area and -detector quantum efficiency as -a function of energy - -Relationships: narrower than #response-function - -Used-in: XMM data products ? - ----------- -New Term: Background Rate -Action: Addition -Label: bkgrate -Description: A dataset that models the rate of residual events that are -not from the expected source type (e.g. for gamma-ray instrument it -measures residual non-gamma-ray events coming). - -Relationships: narrower than #response-function - -Used-in: HESS test data release (https://doi.org/10.5281/zenodo.1421099) ----------- -New Term: Energy Dispersion -Action: Addition -Label: edisp -Description: A dataset that records the -probability density of detecting an event with an energy estimator given the true -energy of the event. - -Relationships: narrower than #response-function - -Used-in: HESS test data release (https://doi.org/10.5281/zenodo.1421099) - ----------- -New Term: Redistribution Matrix File -Action: Addition -Label: rmf -Description: A dataset that records the probability density function -mapping from energy space into detector pulse height (or position) space - -Relationships: narrower than #response-function - -Used-in: Chandra response data products ? - -Reference: -- IVOA Note: https://github.com/ivoa/HighEnergyObsCoreExt section 5.1.5 -- IVOA Note Virtual Observatory and High Energy Astrophysics Version 1.0 -https://ivoa.net/documents/Notes/VOHE/20241112/VOHE-Note-draft_1.0.pdf \ No newline at end of file From b6d0ff9ea9ddfcb848ed15ef789389acce77a382 Mon Sep 17 00:00:00 2001 From: Jutta Schnabel Date: Fri, 15 May 2026 20:38:00 +0200 Subject: [PATCH 23/23] removing multiple hrefs --- HighEnergyObsCoreExt.tex | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/HighEnergyObsCoreExt.tex b/HighEnergyObsCoreExt.tex index 1855c75..9b0f821 100644 --- a/HighEnergyObsCoreExt.tex +++ b/HighEnergyObsCoreExt.tex @@ -43,17 +43,6 @@ \usepackage{amssymb} \usepackage[nopostdot,style=super,nonumberlist,toc]{glossaries} \usepackage{hyperref} -\usepackage{hyperref} -\usepackage{hyperref} -\usepackage{hyperref} -\usepackage{hyperref} -\usepackage{hyperref} -\usepackage{hyperref} -\usepackage{hyperref} -\usepackage{hyperref} -\usepackage{hyperref} -\usepackage{hyperref} -\usepackage{hyperref} \newacronym{IVOA}{IVOA}{International Virtual Observatory Alliance} \newacronym{VO}{VO}{Virtual Observatory}