IVOA RadioAstronomy Virtual Meeting Number 1 -- July 2nd 2020 first slot ML:MarkLacy (group chair, NRAO) JD: James Dempsey (ASKAP, CASDA) BC: baptiste Cecconni (Nançay) MatM: Matthia Mancini (Astron) MiL:Mireille Louys (CDS) FB : François Bonnarel (group vice-chair, CDS) AL : Alan Loh (Nançay) MK: Mark Kettenis (JIVE) YG: Yan Grange (Astron,LOFAR) HV: Harro Verkouter (JIVE) FS: Felix Stoehr (ALMA) AZ:Allessandra Zanichei (INAF) MarM: Marco Molinaro (INAF) LM: Laurent Michel (ObAS Strasbourg) HH: Hendrik Heinl (CDS) Others ? second slot PT:Peter Teuben SG: Severin Gaudet (CADC) RT: Russ Taylor (South Africa, SKA ?) CF: Chiara Ferrar (SKA France)i TC:Tracy Clarke (US naval Obs , Washington DC) MA: Mark Allen (CDS) ML FB MiL KL: Katharina Lutz (CDS) JG: Juan Garrido (IAA, spain) Others ? ML: presents what is the aim of the group : - getting radio archive work with the VO. - and encourage Making science with that ? - Changes needed in the virtual observatory standards. As an introduction : presentation of James Dempsey (ASKAP/CASDA). (see slides) ASKAP has a Very wide bunch of data Motivation : provide acess to science ready data products. - One API for system and astronomer use - Interoperability is a driver Catalogs : TAP and Conesearch. Programmatic search + Cross Match --> Using TOPCAT as client Image and Cube Use cases : SIA2, programmatic access to data products General Data Discovery : Use ObscOre for data products Most data products have s_region and ra/dec. No Measurement Sets yet ... BC : you have solar system observations. What about EPN-core services ? JD : for some observations for example multiwavelength Jupiter observations BC: wil keep in touch with ASKAP HV: how can you use existing tooling? interactions foreseen between tools? JD: using API, SAMP FS: how do you treat private data ? JD: we have a proxy with authentication system ML: what is needed to put data in the VO ? FS: : we have ObsCore service (for ALMA)+ additional columns. Data hierachy is complicated. We have to use DataLink for that. we want to move to VO inside philosophy. Other Radio VO services: - YG: LOFAR (ASTRON, with DaCHS): Apertif, MSSS. there are interesting challenges. DataLink planned - JD: ASKAP (local developments) - BC: in Nancay : routine Decametric for Solar sytem and Jupiter available with EpnCore (NDA), and set-up on going for solar decimetric observation (NRH), proto service for Nenufar with Obscore BC: Orleans : Pulsar data to be mapped to Obscore check how to map PSRfits to Obscore : done also done at ASKAP : they have done this mapping BC: proposes to prepare a collective IVOA note with this interest group partners - MK: JIVE : most of obscore metadata present in future services. ObsCore for Visibility data based on Dachs. Currently Developping the code to collect metadata. AZ : in Italia also, we are still working on radioastronomy services, with Obscore but we work also with CAOM. Also exploring DataLink. FB : shows visibility data obscore prototype (see slides) MK: has a specialized Fits format ; an observation is split by time. has code for this on Fits format . wish to collaborate about this strategy for splitting f_min,f_max = do they duplicate the em_min em_max? FB: yes. everuthing done in frequency. Eventually computed in wl. Freq are more familiar to set a search criterium data sets splitting : MM & BC : lofar and nenufar will have diff MS files for diff spectral windows ??? split by freq intervals BC + AL +YG : clarify the interpretation of antenna diameter for Nenufar : Lofar : will use the nbeam of the current observation MK: long base line : time and freq smearing limit the field of view. has code for this. MatM: station beam MarM: describing one observation and searching for criteria seems to be dependent on usecases we should discuss discovering strategy and clarify the parameters that help to select data in various use-cases fov, antennae params,...larger angular scale? FS: in Alma , MS is split along time axis , contains several fields ASDM to store data instead of MS ( smaller files) BC : target name "field names in MS are not standard" discuss what content to put wrt use cases. see how it could be tracked during observation phase . i JD : given by the observer , so diificult to standardize while observing ? -------------------------------------------------------------------------------------------------------- Second teleconf: ML : improve the usage of the VO. in radioastronomy data / metadata unique to radioastronomy what to be added for discovery/ acces / and visualisation this morning we had several groups in Australia and Europe with VO projects TC : what is a vo tool a tool aware of VO standards / ---> ds9 can be TC : I have not used the vO myself;. we have a lot of images .. / Washington DC / VLA images / calibrated visibilities, catalogs / xmatch ML : VO not developping service, but standards CF: we don't have our radio telescope yet / developping SKA regional center (?)building storage infrastructure including VO layer TC : has NRAO considerd becoming such a center ? ML : we don't have specific VO human resources MA : idea = by using vO tools reuse tools built by others. libraries provided by CADC / CDS for tap servers use of HiPS. If you do that you get a cutout server for free... We are assuming regional centers have the resource to put the data on line / they have benefit to use the standards CF: workshop to show what exists in other domains ? tutorial ? workshops could be very useful. use the experience of the groups givibg talks this morning. / TC : how to tackle radio visualisation specifitcities. you cannot normalize your images by using rms for example. CF : FaceBook page useful . How to learn to young people. Tracy : NRAO summer schools? Chiara : schools in SKA center could be useful MA : collect event infomation on the RadioIG wiki page Visibility data service : RT : don't miss polarization information for query (correlation ?) ML : how to characterize highest size structure ? TC: how can we show these coverage maps for combination of datasets we would like to do ? MA : could be a prefiguration of what can be produced. What do you want to do ?New mailCopy