| |
| META TOPICPARENT |
name="IVOA.TomDonaldson" |
|
|
<
< | Applications Sessions Schedule - IVOA May 2021 Interoperability Meeting |
>
> | Discussion: IVOA/Astropy/Astroquery/PyVO Collaboration |
| |
[back to main programme page]
| Schedule Summary |
| Session |
DateTime UTC |
UTC-08:00 |
UTC-05:00 |
UTC+02:00 |
UTC+08:00 |
UTC+11:00 |
| Victoria BC/Pasadena |
Washington DC |
Strasbourg |
Perth/Beijing |
Canberra |
|
|
<
< |
| Applications |
May 25 20:30 |
May 25 13:30 |
May 25 16:30 |
May 25 22:30 |
May 26 04:30 |
May 26 06:30 |
|
>
> |
| Discussion Session |
May 25 15:00 |
May 25 08:00 |
May 25 11:00 |
May 25 17:00 |
May 25 23:00 |
May 26 01:00 |
|
|
<
< |
| Apps/DAL |
May 27 05:00 |
May 26 22:00 |
May 27 01:00 |
May 27 07:00 |
May 27 13:00 |
May 27 15:00 |
|
| | |
|
<
< | Applications |
>
> | Discussion Session |
| | |
|
<
< | Time: Tuesday May 25 20:30 UTC |
>
> | Time: Tuesday May 25 15:00 UTC |
| | |
|
<
< |
|
>
> | With the success of the Astropy hack sessions at the 2019 Paris Interoperability Meeting (summary slides) and significant VO-related development in PyVO, Astroquery and Astropy since, this is an opportunity to discuss some details of the collaboration to help ensure its continued success. |
|
<
< |
| Pierre Fernique, Ada Nebot, Sébastien Derriere |
Status on MOCs in the IVOA We will present the current status of the "MOC: Multi-Order Coverage map version 2.0" document, and in particular the differences and progresses from the current standard, and the exension to the time domain with TMOC and STMOC expanding the SMOC capabilities. We will discuss the implementation of the new capabilities in libraries, applications, and the description of existing datasets. The presentation will be followed by a short demonstration of STMOC usage on simple science cases. |
15'+3' |
|
| Dave Morris |
Registering IVOA software in ESCAPE The European ESCAPE project is creating a registry of software linked to the project. Our work package in ESCAPE is tasked with promoting IVOA standards andsoftware within ESCAPE. We have started a discussion in ESCAPE about how to promote IVOA software in the context of ESCAPE. This session is to raise the same discussion at the IVOA, collecting thoughts ideas and suggestions about how to promote IVOA software to other communities. |
12'+2' |
|
| Baptiste Cecconi |
VESPA-Cloud EOSC experiment for automated deployment of TAP service |
12'+2' |
|
| Jiri Nadvornik |
HDF5 and the VO An emerging practice in machine learning is to combine data from different domains, such as spectra and images, to gain additional knowledge. Combining such data brings its own challenges which we solved by using HDF5 for creating a specialized data model. It is used to store and process combined spectra and images efficiently. In this talk, I will discuss the possibility to connect HDF5 via VO protocols to existing tools, such as Topcat or Aladin to explore the combined data |
12'+2' |
|
|
| | |
|
<
< | Moderator: Raffaele, Notetaker: Tom, notes: Etherpad link |
>
> | Discussion topics are suggested below with an accompanying outline in the Etherpad link. Please add notes there to help inform and guide the discussions as well as suggesting other potential topics to cover in this or future meetings. |
|
<
< | DAL/Apps |
| | |
|
<
< | Time: Thursday May 27 05:00 UTC Please see the DAL schedule for details on this joint session between the Applications and Data Access Layer working groups. |
>
> | The time schedule is ambitious, so topics may need to be abbreviated (or skipped), but let's try to at least establish the next step for the discussion (splinter meeting, github discussion, etc.). |
|
>
> |
| Speaker(s) |
Title and Abstract |
Time |
Material |
| Bruno Merin |
Introduction A brief high-level review of the goals and recent history of IVOA/Astropy to help set the context for the discussions. |
10' |
|
| All |
Unifying PyVO's TAP with Astroquery's TAPPlus One of the goals coming out of the Paris meeting was to refactor Astroquery modules to use TAP features implemented in PyVO instead of those implemented in the Astroquery TAPPlus module. PyVO TAP evolved substantially since then, but is not identical to TAPPlus either in feature set or usability details. How do we move forward towards identifying and implementing the changes needed in PyVO to be able to deprecate TAPPlus and refactor the Astroquery modules that use it? |
15' |
|
| All |
Where to Handle VOTable Metadata Astropy has a very solid VOTable parser and writer which is able to recognize and validate some, but not all, of the metadata elements. What has been particularly elusive is doing something meaningful based on the metadata such as creating SkyCoord objects for rows in a source catalog VOTable. With efforts underway in the Data Model working group to make the metadata more rigorous and unambiguous, automatic mapping to Astropy objects may become both more possible and more desired (see the presentations and discussions in the Data Model Workshop sessions this week). A natural question then is where do such implementations belong (PyVO, Astropy, other)? |
15' |
|
| All |
Governance and Process Improvements - PyVO is currently an Astropy affiliated package, though there were initial plans to work towards a status of coordinated package. Let's clarify the differences and practical impacts and set expectations/goals for future.
- IVOA participation in Astropy projects seems generally good. What are some ways to improve?
|
10' |
|
| All |
Next Steps Should we schedule splinter meetings or hack sessions to continue work on any topic? What homework should be completed prior to such a meeting? |
5' |
|
Moderator: TBD, Notetaker: Tom Donaldson, notes: Etherpad link |
| |
<--
--> |
