diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index b9c3e52..6bf5156 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -7,7 +7,7 @@ name: Check the IVOA document env: - doc_name: HighEnergyObsCoreExt + doc_name: HighEnergyObsCoreExt on: pull_request: diff --git a/.github/workflows/preview.yml b/.github/workflows/preview.yml index 4d0c7d2..40741ff 100644 --- a/.github/workflows/preview.yml +++ b/.github/workflows/preview.yml @@ -30,7 +30,7 @@ jobs: - name: Setup dependencies run: | - sudo apt update + sudo apt update sudo apt install texlive-latex-base texlive-latex-recommended \ texlive-latex-extra texlive-fonts-recommended \ librsvg2-bin latexmk \ @@ -38,6 +38,7 @@ jobs: - name: Build the document run: make biblio ${{ env.doc_name }}-draft.pdf + run: make ${{ env.doc_name }}-draft.pdf - name: Check the output run: | diff --git a/HighEnergyObsCoreExt.tex b/HighEnergyObsCoreExt.tex index c6fcc47..3adc5d5 100644 --- a/HighEnergyObsCoreExt.tex +++ b/HighEnergyObsCoreExt.tex @@ -9,19 +9,19 @@ \ivoagroup{High Energy Interest Group} \author{ - I. Evans (SAO/CXC, \href{mailto:ievans@cfa.harvard.edu}{ievans@cfa.harvard.edu}, - 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 - 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}), - J. Schnabel (ECAP, \href{mailto:jutta.schnabel@fau.de}{jutta.schnabel@fau.de}), + I. Evans (SAO/CXC, \href{mailto:ievans@cfa.harvard.edu}{ievans@cfa.harvard.edu},\\ + 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 - 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}),\\ + 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}), } @@ -37,24 +37,27 @@ \usepackage{lscape} %\usepackage{minted} \setlength {\marginparwidth }{2cm} + \usepackage{todonotes} \usepackage{array} \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} + +% mireille : in order to flag changes to fill +\newcommand{\TODO}[1]{% + \noindent% + \colorbox{todocolor}{% + \parbox{0.85\linewidth}{\sffamily \textbf{TODO:}\\ + #1} + }% + \vspace{2pt} +} + + +%glossary \newacronym{IVOA}{IVOA}{International Virtual Observatory Alliance} \newacronym{VO}{VO}{Virtual Observatory} \newacronym{HE}{HE}{High Energy} @@ -408,6 +411,8 @@ \subsubsection{Event Bundle} An {\bf event-bundle} might for example consist of an {\bf event-list} and the associated {\bf response-function}s used to calibrate the dataset, and may also contain provenance information, data quality time-series, and preview images or plots. + + \subsubsection{Advanced Data Products} In addition to data product types that focus on event data, we note that existing ObsCore definitions do not adequately span the breadth of advanced data products (typically with {\em calib\_level\/}${}\ge 3$) that may be generated from astronomical observations. The computational complexity of analyzing \gls{HEA} data robustly in the extreme Poisson regime ({\em e.g.\/}, Bayesian X-ray aperture photometry applied simultaneously to multiple overlapping detections and observations) means that data providers may choose to provide such analysis products directly to the end user. @@ -599,48 +604,86 @@ \subsection{MIME-type Enhancements}\label{sec:mimetypes} \section{Proposed ivoa.obscore\_hea Table Attributes}\label{sec:ibscoreext} This section summarizes the proposal for the \gls{HEA} extension of ObsCore. We use the term {\em ivoa.obscore\_hea\/} to described the extension here and in Appendix~\ref{sec:uc}. +% start mireille ucd update -\begin{landscape} -\begin{center} -%\begin{longtable}{ | m{2.5cm} | m{3em} | m{3em} | m{3em} | m{6cm} | m{2.3em} |} -\begin{longtable}{ | p{0.125\linewidth} | p{0.075\linewidth} | p{0.075\linewidth} | p{0.075\linewidth} | p{0.6\linewidth} | p{0.05\linewidth} |} -\hline -{\centering \bf Column Name} &{\centering \bf UType} &{\centering \bf Unit} &{\centering \bf Type} &{\centering \bf Description} &{\centering \bf MAN}\\ -\hline -{\em ev\_xel\/} & TBD & unitless & integer & Number of events in an event list & NO \\ +\begin{longtable}{ | m{2.5cm} | m{4em} | m{3em} | m{3em} | m{6cm} | m{2.3em} |} \hline -{\em s\_ref\_energy\/} & TBD & eV & double & Energy at which the ObsCore spatial characterization attributes {\em s\_fov\/}, {\em s\_region\/}, {\em s\_resolution\/} are defined & NO \\ + +{\centering \bf Column Name} &{\centering \bf UCD} &{\centering \bf Unit} &{\centering \bf Type} &{\centering \bf Description} &{\centering \bf MAN}\\ \hline -{\em em\_ref\_energy\/} & TBD & eV & double & Energy at which the ObsCore spectral characterization attributes {\em em\_res\_power\/}, {\em em\_resolution} are defined & NO \\ + ev\_xel & \ucd{meta.number;obs.event} & unitless & int & {\footnotesize Number of events in an event\_list }& NO \\ \hline -{\em s\_ref\_oaa\/} & TBD & deg & double & Off-axis angle ({\em i.e.\/}, the angular separation of the target or source from the telescope optical axis) at which the ObsCore spatial characterization attributes {\em s\_fov\/}, {\em s\_region\/}, {\em s\_resolution\/} are defined & NO \\ + s\_ref\_energy & \ucd{meta.ref;em.energy;pos} & eV & float & {\footnotesize Energy at which the ObsCore spatial characterisation attributes s\_fov , s\_region, s\_resolution are defined} & NO \\ \hline -{\em em\_ref\_oaa\/} & TBD & deg & double & Off-axis angle ({\em i.e.\/}, the angular separation of the target or source from the telescope optical axis) at which the ObsCore spectral characterization attributes {\em em\_res\_power\/}, {\em em\_resolution\/} are defined & NO \\ + em\_ref\_energy & \ucd{meta.ref;em.energy;em} & eV & float & {\footnotesize Energy at which the ObsCore spatial characterisation attributes em\_res\_power, em\_resolution are defined} & NO \\ \hline -{\em t\_intervals\/} & TBD & unitless & string & List of observation intervals or stable/good time intervals describing the exact observation time coverage as a TMOC & NO \\ + s\_ref\_oaa & \ucd{pos.posAng;instr.offset;pos} & deg & float & {\footnotesize Off-axis angle (i.e., the angular separation of the target or source from the telescope optical axis) at which the ObsCore spatial characterisation attributes s\_fov , s\_region, s\_resolution are defined} & NO \\ \hline -{\em energy\_min\/} & TBD & eV & double & Energy associated to the ObsCore attribute {\em em\_max\/}, describing the minimum energy of the dataset & NO \\ + em\_ref\_oaa & \ucd{pos.posAng;instr.offset;em} & deg & float & {\footnotesize Off-axis angle (i.e., the angular separation of the target or source from the telescope optical axis) at which the ObsCore spectral characterisation attributes em\_res\_power, em\_resolution are defined} & NO \\ \hline -{\em energy\_max\/} & TBD & eV & double & Energy associated to the ObsCore attribute {\em em\_min\/}, describing the maximum energy of the dataset & NO \\ + t\_intervals & \ucd{?? }& unitless & TMOC & {\footnotesize List of observation intervals or stable/good time intervals describing the exact observation time coverage} & NO \\ \hline -{\em obs\_mode\/} & TBD & unitless & string & Observation mode of an observation & NO \\ + energy\_min & \ucd{em.energy;stat.min} & float & eV & {\footnotesize Energy associated to the Obscore attribute em\_max, describing the minimal energy of the dataset} & NO \\ \hline -{\em tracking\_type\/} & TBD & unitless & string & Tracking type of an observation & NO \\ + energy\_max & \ucd{em.energy;stat.max} & float & eV & {\footnotesize Energy associated to the Obscore attribute em\_min, describing the maximal energy of the dataset} & NO \\ \hline -{\em scan\_mode\/} & TBD & unitless & string & Scan mode of an observation & NO \\ + obs\_mode & \ucd{meta.code;obs.param} & unitless & string &{\footnotesize Observation mode of the observation (e.g. TBU)} & NO \\ \hline -{\em pointing\_mode\/} & TBD & unitless & string & Pointing mode of an observation & NO \\ + tracking\_mode & \ucd{meta.code;obs.param} & unitless & string & {\footnotesize Tracking mode of an observation (e.g., sidereal rate, moving target [solar system] tracking, drift scans)} & NO \\ \hline -{\em analysis\_mode\/} & TBD & unitless & string & Data reduction/analysis mode & NO \\ + analysis\_mode & \ucd{meta.code;obs.param} & unitless & string &{\footnotesize Data reduction/analysis mode}& NO \\ \hline -{\em event\_type\/} & TBD & unitless & string & Event subset indicator ({\em e.g.\/}, data quality flag for the events) & NO \\ + event\_type & \ucd{meta.code.qual;obs.event} & unitless & string &{\footnotesize Data quality flag of the events (e.g. ``good psf'', ``good rejection'', ``Nhit (100,200)''} & NO \\ \hline -\caption{Attributes for the \gls{HEA} Extension of ObsCore} -\label{tab:hea_ext_attr} \end{longtable} -\end{center} -\end{landscape} - +%\end{center} + + +% end mireille ucd update +%\begin{landscape} +%\begin{center} +%%\begin{longtable}{ | m{2.5cm} | m{3em} | m{3em} | m{3em} | m{6cm} | m{2.3em} |} +%\begin{longtable}{ | p{0.125\linewidth} | p{0.075\linewidth} | p{0.075\linewidth} | p{0.075\linewidth} | p{0.6\linewidth} | p{0.05\linewidth} |} +%\hline +%{\centering \bf Column Name} &{\centering \bf UType} &{\centering \bf Unit} &{\centering \bf Type} &{\centering \bf Description} &{\centering \bf MAN}\\ +%\hline +%{\em ev\_xel\/} & TBD & unitless & integer & Number of events in an event list & NO \\ +%\hline +%{\em s\_ref\_energy\/} & TBD & eV & double & Energy at which the ObsCore spatial characterization attributes {\em s\_fov\/}, {\em s\_region\/}, {\em s\_resolution\/} are defined & NO \\ +%\hline +%{\em em\_ref\_energy\/} & TBD & eV & double & Energy at which the ObsCore spectral characterization attributes {\em em\_res\_power\/}, {\em em\_resolution} are defined & NO \\ +%\hline +%{\em s\_ref\_oaa\/} & TBD & deg & double & Off-axis angle ({\em i.e.\/}, the angular separation of the target or source from the telescope optical axis) at which the ObsCore spatial characterization attributes {\em s\_fov\/}, {\em s\_region\/}, {\em s\_resolution\/} are defined & NO \\ +%\hline +%{\em em\_ref\_oaa\/} & TBD & deg & double & Off-axis angle ({\em i.e.\/}, the angular separation of the target or source from the telescope optical axis) at which the ObsCore spectral characterization attributes {\em em\_res\_power\/}, {\em em\_resolution\/} are defined & NO \\ +%\hline +%{\em t\_intervals\/} & TBD & unitless & string & List of observation intervals or stable/good time intervals describing the exact observation time coverage as a TMOC & NO \\ +%\hline +%{\em energy\_min\/} & TBD & eV & double & Energy associated to the ObsCore attribute {\em em\_max\/}, describing the minimum energy of the dataset & NO \\ +%\hline +%{\em energy\_max\/} & TBD & eV & double & Energy associated to the ObsCore attribute {\em em\_min\/}, describing the maximum energy of the dataset & NO \\ +%\hline +%{\em obs\_mode\/} & TBD & unitless & string & Observation mode of an observation & NO \\ +%\hline +%{\em tracking\_type\/} & TBD & unitless & string & Tracking type of an observation & NO \\ +%\hline +%{\em scan\_mode\/} & TBD & unitless & string & Scan mode of an observation & NO \\ +%\hline +%{\em pointing\_mode\/} & TBD & unitless & string & Pointing mode of an observation & NO \\ +%\hline +%{\em analysis\_mode\/} & TBD & unitless & string & Data reduction/analysis mode & NO \\ +%\hline +%{\em event\_type\/} & TBD & unitless & string & Event subset indicator ({\em e.g.\/}, data quality flag for the events) & NO \\ +%\hline +%\caption{Attributes for the \gls{HEA} Extension of ObsCore} +%\label{tab:hea_ext_attr} +%\end{longtable} +%\end{center} +%\end{landscape} + +\input{response_table.tex} + +%\input{analysis_dp_table.tex} \pagebreak %\printglossaries diff --git a/Makefile b/Makefile index 397f0cd..a72c5e9 100644 --- a/Makefile +++ b/Makefile @@ -8,14 +8,14 @@ DOCNAME = HighEnergyObsCoreExt DOCVERSION = 1.0 # Publication date, ISO format; update manually for "releases" -DOCDATE = 2025-11-12 +DOCDATE = 2026-04-27 # What is it you're writing: NOTE, WD, PR, REC, PEN, or EN DOCTYPE = PEN # An e-mail address of the person doing the submission to the document # repository (can be empty until a make upload is being made) -AUTHOR_EMAIL=??? +AUTHOR_EMAIL=ian.evans@ , bruno.khelifi@, mathieu.servillat@ # Source files for the TeX document (but the main file must always # be called $(DOCNAME).tex) diff --git a/VEP/VEP-25_response-function.txt b/VEP/VEP-25_response-function.txt new file mode 100644 index 0000000..95023e7 --- /dev/null +++ b/VEP/VEP-25_response-function.txt @@ -0,0 +1,102 @@ +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 diff --git a/VEPforUCD/VEP-UCD-27-stat_confidencelevel.txt b/VEPforUCD/VEP-UCD-27-stat_confidencelevel.txt new file mode 100644 index 0000000..badc29d --- /dev/null +++ b/VEPforUCD/VEP-UCD-27-stat_confidencelevel.txt @@ -0,0 +1,18 @@ +Vocabulary extension proposal for UCDs / + +Vocabulary: http://www.ivoa.net/rdf/datalink/core +Author: mireille.louys@astro.unistra.fr with EST solar group +Date: 2026-02-11 +Nb of terms discussed together : 1 +----------------------- + +New Term: stat.confidenceLevel +Action: Amendement +Label: Level of confidence for *a statistical measure*, detection or classification process + +Description: statistical confidence level to assess a statistical distribution. +In the analysis of statistical products, the stat confidence levels is used to establish data quality. + +Rationale: Enhance definition of term to include statistical measures + +Used_in: Statistical data sets \ No newline at end of file diff --git a/VEPforUCD/VEP-UCD-28-ParticleFluxes.txt b/VEPforUCD/VEP-UCD-28-ParticleFluxes.txt new file mode 100644 index 0000000..d649ad2 --- /dev/null +++ b/VEPforUCD/VEP-UCD-28-ParticleFluxes.txt @@ -0,0 +1,135 @@ +Vocabulary: http://www.ivoa.net/rdf/UCDlist/ +Author: Bruno Khelifi , mireille.louys@unistra.fr +Date: 2026-04-8, updated 2026-04-22 +Nb of terms discussed together : 5 +----------------------- + +Proposal to add dimension equations to all definition in order to avoid any ambiguity. +The dimensionality is given using the SI symbols of dimensions. +It allows users to express values relative to this UCD in any unit having the same dimensionality. + +New Term: phys.flux +Action: Amendement +Prefix: Q +Description: Flux or flow of particles +( remove energy from current definition) +Additional Property:(dimensionality: [L^-2.T^-1]) +Rationale: Define flux for any physical particle + +Used_in: present in UCDList1.6 +Discussion: +Do we have a normalized representation of dimensional equations ( kind of grammar) in order to have efficient algorithms for comparing these strings ? +For instance, T first , then L , then Mass , etc ... + +Decision: + +----------------------- +New Term: phys.flux.energy +Action: Amendement +Prefix: Q +Description: Energy flux, heat flux or irradiance + +Additional Property:(dimensionality: [M.T^-3]) +Rationale: Distinguish between flux of particles and flux of energy. + +Used_in: %todo provide an example site or file +Discussion: +Decision: +----------------------- +New Term: phys.flux.bol +Action: Addition +Prefix: Q +Description: Bolometric flux +Additional Property:(dimensionality: [M.T^-3]) + +Used_in: %todo provide an example site or file +Rationale: phot.flux.bol is present in UCDList1.6 +Discussion: can we use instead "phys.flux;phys.energy;em.bol" and define ? +Decision: + +----------------------- +New Term: phys.flux.density +Action: Addition +Prefix: Q +Description: Flux density or spectral density or differential flux +Additional Property:(dimensionality: [T.M^-1.L^-4]) + +Used_in: %todo provide an example site or file +Rationale: + +Discussion: Can we use instead "phys.flux;phys.count;em.energy / em.wl / em.freq", leading to the removal of this term of the UCD list? +No phys.count exist in UCDList1.6 +Decision: + +----------------------- +New Term: phys.flux.density.sb +Action: Addition +Prefix: Q +Description: Flux density surface brightness +Additional Property:(dimensionality: [T.M^-1.L^-4]) + +Used_in: %todo provide an example site or file +Rationale: + +Discussion: same as for phys.flux.density +can we use instead "phys.flux;phys.count;em.energy;instr.sr", leading to the removal +of this term of the UCD list? never clear whether we multiply by em.energy or divide... +Isn't phys.flux already per unit of surface area ? Has the same dimensionality as phys.flux.density + +Decision: %todo clarify the definition + +----------------------- +New Term: phys.flux.sb +Action: Addition +Prefix: Q +Description: Flux surface brightness +Additional Property:(dimensionality: [L^-2.T^-1]) + +Used_in: %todo provide an example site or file +Rationale: +???? +Discussion: can we use instead "phys.flux;phys.count;instr.sr"? +--> need to clarify / same unit equations as phys.flux ?? +Decision: + +----------------------- +Term: phys.fluence +Action: Amendement +Prefix: Q +Description: Particles per unit area +Additional Property:(dimensionality: [L^-2]) + +Used_in: exists in UCDList1.6 + +Rationale: + +Discussion: suffix E exists and allows various combinations already. +Harmonize with UCDList1.6 definition + +Decision: +----------------------- +New Term: phys.fluence.density +Action: Addition +Prefix: Q +Description: Spectral fluence or particles per unit area per energy +Additional Property:(dimensionality: [M^-1 L^-4 T^2]) + +Used_in: ?????? +Rationale: + +Discussion: can we use instead "phys.fluence;phys.count;em.energy"? never clear whether we multiply by em.energy or divide... +Must be refined / discussed +Decision: + +----------------------- +New Term: phys.luminosity +Action: Amendement +Prefix: Q +Description: Luminosity or total radiative power +Additional Property:(dimensionality: [M L^2 T^-3]) +Used_in: + +Rationale: +Discussion: defined in UCDList1.6 with suffix E already allowing pre/post combinations +Decision: + diff --git a/VEPforUCD/VEP-UCD-30-stat-error-sup-inf.txt b/VEPforUCD/VEP-UCD-30-stat-error-sup-inf.txt new file mode 100644 index 0000000..aa4c64b --- /dev/null +++ b/VEPforUCD/VEP-UCD-30-stat-error-sup-inf.txt @@ -0,0 +1,41 @@ +Vocabulary: http://www.ivoa.net/rdf/UCDlist/ +Author: mireille.louys@unistra.fr, khelifi@in2p3.fr +Date: 2026-03-12, revised 2026-04-13 +Nb of terms discussed together : 2 +----------------------- + +New Term: stat.error.negative +Prefix: P +Label: Statistical error below the reference value + +Description: For non symmetric error values, we want to distinguish between the upper error value and the lower error value w.r.t the reference value (median or mean). Here we consider the absolute value of the error below the reference value. + +Rationale: + +Used-in: https://www.aanda.org/articles/aa/full_html/2010/12/aa14484-10/aa14484-10.html, +Section 5.4. Excess rms-flux correlation + +Discussion: TBD in semantics & HEIG +Propose stat.error.below instead of stat.error.negative ( Mireille) + +Decision: + +------------------------------------------------------- + +New Term: stat.error.positive +Prefix: P +Label: Statistical error above the reference value + +Description: For non symmetric error values, we want to distinguish between the upper error value and the lower error value w.r.t the reference value (median or mean). Here we consider the absolute value of the error above the reference value. + +Rationale: Useful for tracing the error bars along the data plots ---> a completer + +Used-in: Used-in: https://www.aanda.org/articles/aa/full_html/2010/12/aa14484-10/aa14484-10.html, +Section 5.4. Excess rms-flux correlation +Here r4=0.87exp(+0.10) index(-0.24) is the correlation value with positive error limits of +0.10 and negative error limit of (-0.24). + + +Discussion: +Propose stat.error.above instead of stat.error.positive ( Mireille & Sebastien) +To Be Discussed in semantics & HEIG +Decision: diff --git a/VEPforUCD/VEP-UCD-31-obs-event.txt b/VEPforUCD/VEP-UCD-31-obs-event.txt new file mode 100644 index 0000000..31280ae --- /dev/null +++ b/VEPforUCD/VEP-UCD-31-obs-event.txt @@ -0,0 +1,29 @@ +Vocabulary: http://www.ivoa.net/rdf/UCDlist/ +Author: mireille.louys@unistra.fr, khelifi@in2p3.fr +Date: 2026-04-23 +Nb of terms discussed together : 1 +----------------------- + +New Term: obs.event +Prefix: S +Label: Related to a signal messenger detection (photon or particle) + +Description: + +Rationale: +High energy experiences gather detections of messengers (photon or particle) as lists of events. +An event can be associated with various measurements like time of arrival, detector position, energy, etc. +An event can be categorized using properties like : +- event identifier : as meta.id;obs.event +- event grade : as meta.code.class;obs.event. +(defined from a detector pixel island, for instance) +- event type: as meta.code.class;obs.event +(defined according to some decision in the analysis pipeline) + +Used-in: + +Discussion: TB Discussed in HEIG and Semantics + + +Decision: + diff --git a/response_table.tex b/response_table.tex new file mode 100644 index 0000000..867c31e --- /dev/null +++ b/response_table.tex @@ -0,0 +1,57 @@ + +\newpage + +\section*{Response table proposal} +\todo{ Check fields for this new table } + +This proposal defines a specific table to list the properties of a response function data set. +This strategy focuses on the adequate attributes necessary to identify a response fonction file. +The data product type is defined in the \emph{response-type} vocabulary available at +\url{http://www.ivoa.net/rdf/response-type}. +The features selected to describe a response data product entail: +\begin{itemize} +\item curation attributes : \emph{resp\_publisher\_did}, \emph{resp\_\_date} +\item identification of the observation it belongs to : \emph{obs\_id} +\item identification of the ObsCore data products it relates to : \emph{obs\_publisher\_did} +\item access : \emph{resp\_access\_url} and \emph{resp\_access\_format} +\item response spatial coverage +\item response energy coverage +\end{itemize} + +This clarifies what is restricted to the response file , and what belongs to the observation. + +\todo{ add UCD for each field +} +\begin{table}[htbp] +%\begin{center} +\begin{tabular}{|p{0.25\textwidth}|p{0.12\textwidth}|p{0.1\textwidth}|p{0.39\textwidth}|} +\hline +Column Name & Unit & Type & Description\\\hline +%obs\_collection & unitless & String & Name of the data collection \\\hline +% binding a response with an observation data set +obs\_id & unitless & String & Related Observation ID (foreign key) \\\hline +obs\_publisher\_did & unitless & String & Related Observation ID (foreign key) \\\hline +% copied from related observation if needed +target\_name & unitless & String & Astronomical object observed, if any\\\hline +facility\_name & unitless & String & Facility Name used for data products to process \\\hline +instrument\_name & unitless & String & Instrument Name used for data products to process \\\hline +% response specific fields +resp\_product\_type & unitless & String & Product type as defined in Response vocabulary\\\hline +resp\_publisher\_did & unitless & String & Dataset identifier given by the publisher\\\hline +resp\_access\_url & unitless & String & URL used to access (download) response dataset\\\hline +resp\_access\_format & unitless & String & File content format (see in ObsCore MimeTypes )\\\hline +% response spatial coverage +s\_ra & deg & double & Region of interest 's for response use ; Central right ascension, ICRS\\\hline +s\_dec & deg & double & Region of interest 's for response use ; Central declination, ICRS\\\hline +s\_region & unitless & String & Region of interest for response use (expressed in ICRS frame)\\\hline +t\_intervals & unitless& String (TMOC) & time coverage for response use \\\hline +%response energy coverage +energy\_min & m & double & Energy band minimal value for response use \\\hline +energy\_max & m & double & Energy band maximal value for response use \\\hline +\end{tabular} +\caption{Mandatory fields of the Response table proposed in this HEIG ObsCore extension serialization} +\label{tab:response_table} +%\end{center} +\end{table} + +