Request for Modification (RFM) for the UCD vocabulary towards UCDList v1.6

UCDList v1.6 Request For Modifications, from Jan 2024 to now

Proposals from StephaneErard (VEP-UCD-003)

• Proposed term: pos.moc
• Proposed description: Multi-order coverage

• Prefix: S
• Rationale: This term is used to tag a parameter containing a MOC (of any type, e.g, temporal, spatial, both, or any future MOC types)
• Used-in: EPNcore-2.0
• Discussion:The closest term available is pos.contour, but it doesn't seem adequate for multi-order coverage.

• a VOTable field is tagged with "pos.moc", in this case, the xtype attribute must be present to tell what is the encoding of the MOC
• "pos.moc" is in the EpnCore "measurement_type", to advertise the content of the product. Could be used with "dataproduct_type", to tell which axes are in the MOC (e.g., 'im' for classical MOC, 'mo' for STMOC, 'ts' for TMOC...)
• A VOTable field with URLs pointing to MOC products. The UCD would be "meta.ref.url;pos.moc"

Decision: implement "meta.coverage" as proposed in VEP-UCD-003.

• Proposed term: pos.projection
• Proposed description: Geometric projection
• Prefix: S
• Rationale: This term is used to tag a parameter containing the projection in use, or to identified parameters that have been projected onto a map (map projected products).
• Used-in: EPNcore-2.0
• Discussion: The current UCD List contains `pos.lambert` which is a specific projection type, which can't cover all the needs for geometric projection tagging.

BC [2023-06-22]: accepted in VEP, to be used with meta.id as primary.

If `pos.lambert` is not used currently in registry => possibly deprecate and move to `pos.projection.lambert` ?

Sci-UCD Discussion: during EPN-TAP RFC review, MarkTaylor proposed to have Q prefixes for both pos.moc and pos.projection.

Proposal from AdaNebot (VEP-UCD-004)

• Proposed term: time.period.oscillation
• Proposed description: Period of pulsation of a body (similar to solar pulsations or oscillations)
• Prefix: Q
• Rationale: This term is used to measure periods in oscillating phenomena.
• Used-in: https://academic.oup.com/mnras/article/487/3/3523/5512602
• Discussion: This term was proposed actually by Ada Nebot to consider oscillating phenomena on sky objects and cover possible time measurements used in these studies. This is a first term proposal for addition concerning oscillating stars, etc ...

BC [2023-06-22]: no objection, but ML to discuss again with Ada.

BC [2024-03-21]: proposed term: "time.period.pulsation" with Label "Period of pulsation or oscillation of a body or a phenomenon"

Proposal from MarkusDemleitner & BaptisteCecconi (VEP-UCD-005, initially in UCDList 1.4 RFM)

• Discussion: See VEP-UCD-005, and UCDList 1.4 RFM for the detailed discussion.

Proposed RFMs - suggestions for datasets issued in the science domain of gravitational waves

Proposal from M.Louys , S.Derriere for P. Chanial (VEP-UCD-011)

• Proposed term: stat.confidenceLevel
• Proposed label: Level of confidence for a detection or classification process
• Proposed description: a value to state the level of confidence for a detection, usually in percent (?).
• Prefix: P
• Rationale: GW studies produce maps of the sky with regions showing detection likelihood at particular confidence level . Such a confidence level can be a selection criteria for a map, or a dataset in general.
• Used-in: Gravitational waves catalogs
• Discussion:

BC [2023-06-22]: Would be useful for a column providing the confidence level used to derive min/max values of a distribution. Could be associated with `stat.stdev` or `stat.percentile` (would require change `stat.stdev` to Q). Examples:

• 3 sigma confidence level => value = 3 and ucd = `stat.confidenceLevel;stat.stdev`
• 95 % confidence level => value = 95 and ucd = `stat.confidenceLevel;stat.percentile`

BC [2024-03-21]:Proposed solution:

• New Term: stat.confidenceLevel
• Action: Addition
• Label: Level of confidence for a detection or classification process
• Prefix: P

• Update Term: stat.stdev
• Action: Modification
• Prefix: Q

Proposal from M.Louys , S.Derriere for P. Chanial (VEP-UCD-012)

• Proposed term: phys.inspiralSpin
• Proposed description: Effective inspiral spin in binary mergers  (used in GW detections )
• Prefix: Q
• Label: Effective inspiral spin in binary mergers  (used in GW detections )
• Rationale: In the study of binary mergers, the notion of spin for each component of the system

• Used-in: LIGO Virgo Gravitational waves detection
• Discussion:
  • https://en.wikipedia.org/wiki/List_of_gravitational_wave_observations#List_of_gravitational_wave_events
  • https://www.quora.com/What-is-the-inspiral-spin-parameter-and-why-are-we-surprised-that-it-is-so-low-in-the-LIGO-events

BC [2024-03-21]:Proposed solution: Accept

Proposals from M.Louys , S.Derriere for P. Chanial (VEP-UCD-013)

• Proposed term: stat.falsePositive
• Proposed description: Related to false alarm or false positive detection
• Prefix: Q
• Description: Used to evaluate the rate of false alarm in detection problems.
• Rationale:Needed for support of catalogs of events detection in various multi- messenger data collections.
• Used-in: Gravitational waves detection (LIGO, Virgo) and in event detections more generally.
• Discussion:
  • Dataset examples:
    • https://en.wikipedia.org/wiki/List_of_gravitational_wave_observations#List_of_gravitational_wave_events
    • Vizier catalogs on GW

BC [2024-03-21]:Proposed solution: Accept

• Proposed term: stat.falseNegative
• Proposed description: Related to missed or false negative detection
• Prefix: Q
• Description: Used to evaluate the rate of missed or false negative detection.
• Rationale:Needed for support of catalogs of events detection in various multi- messenger data collections.
• Used-in: Gravitational waves detection (LIGO, Virgo) and in event detections more generally.
• Discussion:
  • Dataset examples:
    • https://en.wikipedia.org/wiki/List_of_gravitational_wave_observations#List_of_gravitational_wave_events

BC [2024-03-21]:Proposed solution: Accept

Proposal from B.Cecconi (VEP-UCD-014)

• Proposed term: phys.adu
• Proposed description: Analog to digital units, raw samples of an instrument, not converted into physical unit.
• Prefix: P
• Description: The raw data samples, often referred to as analog-to-digital-units (ADU). They are not converted yet into physical units. In other words, the transfer function of the instrument has not been applied.
• Rationale: This term would be useful to refer to raw data. This term was mentionned during the preparation of the ObsCore for Radioastronomy extension. The first atom word ('phys.') could be something else (like 'meta.').
• Used-in:
  • Dataset examples:
    • cassini_rpws.epn_core table (on voparis-tap-maser TAP server), containing raw, calibrated and derived products.
• Discussion [2024-03-21]
  • in the ObsCore Radio extension (as of this date): "In the current UCD vocabulary (UCD1+ controlled vocabulary - Updated List of Terms Version 1.5) there appear to be no primary words suitable to describe raw SD data. o_ucd=phot.flux.density, which fits well for appropriate data, does not seem appropriate, since the single dish measured quantity is expressed in raw counts coming from the digitisation of a voltage signal generated in the receiver chain by the incoming electromagnetic field. Further discussion on o_ucd is ongoing within the Semantics WG."
  • A proposal could be to use the secondary word "stat.uncalib" to indicate the "raw" status of the quantity, but a primary UCD word must be used, such as "phot.count", or "phys.current" (or "phys.voltage" which doesn't exist yet)
  • Conceptually the "stat.adu" is referring to the output of an analogue-to-digital sampler.
  • If we add "phys.voltage", a solution would be phys.voltage;stat.uncalib

• BC [2024-03-21]: Proposed change:
  • New term: phys.voltage
  • Prefix: Q
  • Description: Electric potential difference over a distance or measured by an instrument.

Proposal from M.Louys (VEP-UCD-015)

• Proposed description: Amplitude measured by a pulse analyser after a particle or radiation detector (photon, gamma ray, ...).

• Rationale: This term would be useful to refer to raw data coming out of a detector and not calibrated yet. The need for such a term was mentionned during the preparation of the IVOA Note "VO Data discovery for High Energy data sets".
• Used-in: Chandra event-list, CTA event-list before calibration.
• Discussion:

• • There may be an overlap with the proposal for "phys.adu" in VEP-UCD-14.txt. To be discussed.

• BC [2024-03-21]: Proposed change: "src.var.amplitude" prefix set to "Q".

Proposed RFMs for Ambiant Conditions at telescopes sites

Proposals from A. Micol , ESO Archive

List of terms and concepts to cover (open for discussion) : ESO VLT Ambient parameters with new terms proposed.

Example Proposal for new term humidity under the subtree obs.atmos.

• Proposed term: obs.atmos.humidity
• Proposed description:
• Prefix: S
• Rationale: Ambient conditions measure various physical parameters at telescope site to monitor turbulence, seeing, etc.
• Used-in: ESO FITS keywords for observations at Paranal , etc .
• Discussion: Some of these parameters are general, some have a very specific definition for the assessment of physical conditions at the telescope's site. Their meaning may be restricted to a the local definition of the measure at the site. In this case , such terms can be branched under the cud node 'obs.atmos'.

On the contrary general terms can be branched below phys.*.

The proposal for adding a obs.atmos subtree to the UCD tree is explained in Proposal for obs.atmos subtree

Proposed RFMs - modification suggestions for planetary science

Summary for iteration UCDList1.5 to UCDList1.6

UCD proposal applied as changes for UCDList1.6

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->