<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Thanks for these notes Mark,</div>
<div class="moz-cite-prefix">I only made a small fix on the
ObsCoreExtension authorship. (in bold below)</div>
<div class="moz-cite-prefix">Cheers</div>
<div class="moz-cite-prefix">François<br>
</div>
<div class="moz-cite-prefix">Le 11/05/2021 à 16:51, Mark Lacy a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:9077640d-0f63-bf41-a554-221586586fd3@nrao.edu">Hi All,
<br>
<br>
Notes from last week's radio interest group video/telecon are
below. Let me know if I've missed anything or got something wrong.
I hope to hear/see some of you at the interop session in a couple
of weeks.
<br>
<br>
Cheers,
<br>
<br>
Mark
<br>
<br>
Radio interest group 3rd Zooms 6th May 2021
<br>
<br>
ObsCore extension:
<br>
<br>
Francois presented the proposal for the ObsCore extension that had
been developed <b>by him and the CDS team within the scope of the
ESCAPE project.</b> It allows for ranges in resolution and
field-of-view for wide-band observations, includes the concept of
largest angular scale, and also other uv-plane and instrumental
characterizations (longest/shortest baselines, number of antennas,
uv-plane filling factor). It also includes time resolution ranges,
and spectral ranges expressed as frequencies instead of
wavelengths. The proposal will be placed on GitHub for comments,
and discussed in the DM session in the Interop.
<br>
<br>
In meeting 1, most of the discussion revolved around how a row in
the ObsCore table should be defined, especially in terms of what
common key could be used to link the ObsCore extension to the
primary ObsCore Table (although the desirability of adding some of
these new fields to ObsCore was also discussed), and how DataLink
services could be implemented to fetch the relevant data.
<br>
<br>
For ALMA, Felix Stoehr broke out target+spw combinations into
separate rows. Mark Kettenis said that JIVE takes the path of
assigning a single obs_publisher_did to an observation (which can
contain many sources and calibrators, and multiple bands). James
Dempsey said that ASKAP is relatively straightforward (one band),
but ATCA data has similar issues (multiple sources and bands in a
single observation).
<br>
<br>
It may be that datalink services could be used to download what
the user will need, e.g. a whole raw observation including
calibrators in some cases, or a calibrated dataset or image of a
single source in others.
<br>
<br>
Frequency for specifying spectral range was widely supported.
<br>
<br>
In meeting 2, the discussion was more focussed on what should be
in the ObsCore extension - Severin Gaudet pointed out that obscore
was designed to focus on the core properties of an observation for
data discovery, and perhaps some of the uv-plane and instrumental
characteristics might not be searched on much. Baptiste Cecconi
wondered whether frequencies need be added as they are redundant
given the wavelength ranges already in obscore, and a tool on the
search front end could be used to do the conversion. He also
suggested that we should work on mapping keywords from common data
formats ((A)SDM/SDFITS/PSRFITS etc) to ObsCore and the proposed
extension.
<br>
<br>
Implementation note:
<br>
<br>
Stories from CASDA (JD), ASTRON (Yan?), MERLIN (PH) missing, JIVE
story needs an update (MK)
<br>
ML will try to tidy it up in time for the Interop.
<br>
<br>
Interop schedule:
<br>
<br>
A 1hr session is tentatively scheduled for May 25th 22:00-23:00
UT.
<br>
<br>
Speakers who’ve volunteered already:
<br>
Mark Kettenis (VO implementation at JIVE and uv-plane
characterization)
<br>
Yan Grange (FRBs)
<br>
Hendrik Heinl (LoFAR DR1)
<br>
Peter Teuben (Single dish radio data in the VO and SDFITS)
<br>
Ricardo Rizzo
<br>
<br>
Other possible contributions:
<br>
Susana Sanchez - provenance for radio data (may be scheduled in
the DM session, also dependent on approval from company working on
the problem)
<br>
Arecibo/CI CoE (may be scheduled in CSP)
<br>
<br>
<br>
</blockquote>
<p><br>
</p>
</body>
</html>