<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Pat , Hi DMers , <br>
<br>
Thanks for the summary . <br>
I volunteer to join the effort for the update of ObsCore to 1.2 . <br>
<br>
I see no problem in including <i>t_exp_min</i> and <i>t_exp_max</i>
in the Core table and remove them from<br>
the time extension table. <br>
<br>
<i>f_resolution</i> proposed in the radio extension was a request
from radio astronomers . <br>
Unlike <i>em_resolution</i> , which varies along the spectral axis,
it is constant along the frequency axis, and <br>
it can be provided directly in the convenient frequency units . <br>
<br>
Concerning the high energy extension , discussion is going on in the
HEIG group to clarify the set of <br>
metadata re-usable from the main Obscore table , and to feed the
heig extension table with precise definitions. <br>
<br>
best wishes, Mireille<br>
<br>
<div class="moz-cite-prefix">Le 06/01/2025 à 21:02, Patrick Dowler
via dm a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAFK8nro62aL=DhL_KGCLbAZEo0AZKYmcVs837o7ZXvCUCcjKNQ@mail.gmail.com">
<pre wrap="" class="moz-quote-pre">At the last interOp and while comparing the radio extension to
CAOM-2.4 and some new features in WD-CAOM-2.5, it became increasingly
clear that some of the proposed fields for the radio extension are
more generally applicable and in my opinion should be promoted to
"core". I kind of volunteered to write down the details of that, so
here it is that proposal:
** core **
s_resolution_min
s_resolution_max
s_fov_min
s_fov_max: I still feel the existing s_fov is already the same as
s_fov_max and not a representative value; it is nominally the size of
the s_region
t_exp_min
t_exp_max
t_exp_mean: In CAOM exposure is already the mean exposure time per
pixel and I feel strongly that the existing ObsCore.t_exptime is
already the same thing (well, it suggests "median exposure time per
pixel" which I think I may have contributed, but median breaks down in
some common nearly degenerate cases and is less useful than mean; we
may need to clarify the definition in ObsCore
f_resolution: absolute spectral resolution is useful, but this should
be named em_resolution
** radio extension **
s_maxiumum_angular_scale - I have been convinced by radio people that
maximum_recoverable_scale is more explicit and a better term for this
uv_distance_min
uv_distance_max
uv_distribution_ecc
uv_distribution_fill
Questions:
1. How does this impact the time extension?
2. How does this impact the high energy extension?
Work:
1. ObsCore needs to be ported to ivoatex (from docx?) and included in ivoa-std
2. I can set aside time necessary to write the the changes for WD-ObsCore-1.2
--
Patrick Dowler
Canadian Astronomy Data Centre
Victoria, BC, Canada
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
--
Mireille Louys, MCF (Associate Professor)
Centre de données CDS Images, Laboratoire ICube &
Observatoire de Strasbourg Telecom Physique Strasbourg
11 rue de l'Université 300, Bd Sebastien Brandt CS 10413
F- 67000-STRASBOURG F-67412 ILLKIRCH Cedex
Tel: +33 3 68 85 24 34</pre>
</body>
</html>