International Virtual Observatory Alliance

Difference: RadioastronomyInterestGroupEighthVirtualMeeting (2 vs. 3)

Revision 32024-07-06 - MarkKettenis

  META TOPICPARENT 
  name="IvoaRadio"  

 Radio Astronomy Interest Group ( Jointly organised with Data Model Working Group) 
 Eight Virtual Running Meeting 2024, July 2nd via zoom 

15:30 to 16:30 UTC



Zoom coordinates:

https://astron.zoom.us/j/81533464364?pwd=bQh0hVs3x3kAmjaLbwoDNJsjIFyIWS.1

Meeting ID: 815 3346 4364

Passcode: 354277
 Telecon Agenda:
- META TOPICPARENT
+  name="IvoaRadio"
-<
<
+) Representation of the ObsCore extension:
->
>
+) Representation of the ObsCore extension:
-<
<
+ The PR standardizes a new ivoa.obscore_radio table and mandates the presence of a obs_publisher_did column in order to be able to do a NATURAL JOIN. Note that Markus suggested to not specify an explicit column to join on...
->
>
+The PR standardizes a new ivoa.obscore_radio table and mandates the presence of a obs_publisher_did column in order to be able to do a NATURAL JOIN. Note that Markus suggested to not specify an explicit column to join on...
-<
<
+ The PR suggests the possibility to provide a view that does that performs this join but doesn't mandate it and doesn't provide a standardized name for it. Is this desirable? Should this be standardized? How would this work for combining multiple extensions (i.e. Radio + Time Domain).
->
>
+The PR suggests the possibility to provide a view that does that performs this join but doesn't mandate it and doesn't provide a standardized name for it. Is this desirable? Should this be standardized? How would this work for combining multiple extensions (i.e. Radio + Time Domain).
-<
<
+) Discovery of ObsCore extensions
->
>
+) Discovery of ObsCore extensions
-<
<
+ Converged on using a utype, but there are still multiple suggestions for the name (ivo://ivoa.net/std/obsradio#table-1.0 vs. ivo://ivoa.net/std/ObsCore#obscore-radioExt-1.0) ?
->
>
+Converged on using a utype, but there are still multiple suggestions for the name (ivo://ivoa.net/std/obsradio#table-1.0 vs. ivo://ivoa.net/std/ObsCore#obscore-radioExt-1.0) ?
-<
<
+ Should we introduce both table_utype and schema_utype for extensions?
->
>
+Should we introduce both table_utype and schema_utype for extensions?
-<
<
+) t_exp_{min|max|mean}
->
>
+) t_exp_{min|max|mean}
   These still need a science case in the Appendix. Can someone (Baptiste?) provide one? Naming is somewhat confusing (name is similar to t_exptime in ObsCore, but describing a different concept)? Is the description correct now?
-<
<
+) s_maximum_angular_scale_{min|max}
->
>
+) s_maximum_angular_scale_{min|max}
-<
<
+ Like the FOV and resolution, the maximum spatial scale is actually frequency-dependent. Should we include min/max values in addition to a typical value?
->
>
+Like the FOV and resolution, the maximum spatial scale is actually frequency-dependent. Should we include min/max values in addition to a typical value?
-<
<
+) f_{min|max}
->
>
+) f_{min|max}
-<
<
+ These have been dropped in the PR. How to convert em_{max|min} into frequencies has been specified in the standard with a prescribed value for the speed of light. f_resolution has been retained to cater for observations with large fractional bandwidth and fixed spectral resolution across the band. Settled?
->
>
+These have been dropped in the PR. How to convert em_{max|min} into frequencies has been specified in the standard with a prescribed value for the speed of light. f_resolution has been retained to cater for observations with large fractional bandwidth and fixed spectral resolution across the band. Settled?
-<
<
+) Next steps
->
>
+) Next steps
-<
<
+ Are we ready for RFC phase?
->
>
+Are we ready for RFC phase?
-<
<
+) AOB
->
>
+) AOB
->
>
+ Recording: 

https://drive.google.com/file/d/1OvfKgpM2go8oXY4NVNajTkPnbiXyIYd5/view?usp=share_link
 <-- 
 
 
 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

View topic | History: r3 < r2 < r1 | More topic actions...