<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>Dear Bruno, Tom,</div><div><br data-mce-bogus="1"></div><div>Would you be open to swap two of the topics in this agenda? </div><div><br data-mce-bogus="1"></div><div><span style="caret-color: #000000; color: #000000; font-family: arial, helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration: none; display: inline !important; float: none;" data-mce-style="caret-color: #000000; color: #000000; font-family: arial, helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration: none; display: inline !important; float: none;">"Unifying PyVO's TAP with Astroquery's TAPPlus" </span></div><div><span style="caret-color: #000000; color: #000000; font-family: arial, helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration: none; display: inline !important; float: none;" data-mce-style="caret-color: #000000; color: #000000; font-family: arial, helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration: none; display: inline !important; float: none;">with</span></div><div><span style="caret-color: #000000; color: #000000; font-family: arial, helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration: none; display: inline !important; float: none;" data-mce-style="caret-color: #000000; color: #000000; font-family: arial, helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration: none; display: inline !important; float: none;">"Where to Handle VOTable Metadata"</span></div><div><span style="caret-color: #000000; color: #000000; font-family: arial, helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration: none; display: inline !important; float: none;" data-mce-style="caret-color: #000000; color: #000000; font-family: arial, helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration: none; display: inline !important; float: none;"><br></span>Due to a last minute personal problem I will join the conversation at 15:30 UTC and I would like to be present by the time the PyVO topic is discussed.</div><div><br data-mce-bogus="1"></div><div>Should that change affects others, please, keep it as it is.</div><div><br data-mce-bogus="1"></div><div>Best regards</div><div>Javier</div><div><br></div><div data-marker="__SIG_PRE__">-- <br>RHEA Group for ESA - European Space Agency<br><br>Javier Durán<br><br>ESAC Science Data Centre<br>Data and Engineering Division<br>Operations Department, Directorate of Science<br>European Space Astronomy Centre (ESAC)<br>European Space Agency (ESA)<br><br>European Space Astronomy Centre (ESAC)<br>Camino Bajo del Castillo s/n<br>Urb. Villafranca del Castillo<br>28692 Villanueva de la Cañada, Madrid, Spain.</div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Bruno Merin" <bmerin@sciops.esa.int><br><b>To: </b>"Tom Donaldson" <tdonaldson@stsci.edu><br><b>Cc: </b>"Adam Ginsburg" <adam.g.ginsburg@gmail.com>, "Erik Tollerud" <etollerud@stsci.edu>, "Clara Brasseur" <cbrasseur@stsci.edu>, "Brigitta Sipocz" <bsipocz@gmail.com>, "Thomas Robitaille" <thomas.p.robitaille@gmail.com>, "TCG IVOA" <tcg@ivoa.net>, "Baptiste Cecconi" <baptiste.cecconi@obspm.fr>, "AdaNebot" <ada.nebot@astro.unistra.fr>, "Damian, Adrian" <Adrian.Damian@nrc-cnrc.gc.ca>, "Christine Banek" <CBanek@lsst.org>, "Javier Duran" <jduran@sciops.esa.int>, "AstroPy Coordinators" <coordinators@astropy.org>, "csp" <csp@ivoa.net>, "Juan Carlos Segovia" <jsegovia@sciops.esa.int><br><b>Sent: </b>Monday, May 24, 2021 9:52:38 AM<br><b>Subject: </b>Re: Astropy IVOA session - Tuesday, May 25, 15:00 UTC<br></div><div><br></div><div data-marker="__QUOTED_TEXT__">Thanks so much Tom,<br><br>The page you did is fantastic! <br><br>I volunteer to act as a moderator for the session if you want.<br><br>Would any of you like to add or modify anything to he points in the page? Please let Tom and myself know.<br><br>Thanks again and talk to you tomorrow,<br><br>Bruno<br><br><br>----- Original Message -----<br>From: Tom Donaldson <tdonaldson@stsci.edu><br>To: Bruno Merin <bruno.merin@sciops.esa.int><br>Cc: Adam Ginsburg <adam.g.ginsburg@gmail.com>, Erik Tollerud <etollerud@stsci.edu>, Clara Brasseur <cbrasseur@stsci.edu>, Brigitta Sipocz <bsipocz@gmail.com>, Thomas Robitaille <thomas.p.robitaille@gmail.com>, TCG IVOA <tcg@ivoa.net>, Baptiste Cecconi <baptiste.cecconi@obspm.fr>, AdaNebot <ada.nebot@astro.unistra.fr>, Damian, Adrian <Adrian.Damian@nrc-cnrc.gc.ca>, Christine Banek <CBanek@lsst.org>, Javier Duran <jduran@sciops.esa.int>, AstroPy Coordinators <coordinators@astropy.org>, csp <csp@ivoa.net>, Juan Carlos Segovia <jsegovia@sciops.esa.int><br>Sent: Mon, 24 May 2021 08:09:30 +0200 (CEST)<br>Subject: Astropy IVOA session - Tuesday, May 25, 15:00 UTC<br><br>Hi All,<br><br>Based on this e-mail thread, I’ve updated the IVOA Meeting wiki with a draft agenda<https://wiki.ivoa.net/twiki/bin/view/IVOA/InterOpMay2021Astropy> for the session. On the main program page<https://wiki.ivoa.net/twiki/bin/view/IVOA/InterOpMay2021>, this is session 3, which runs for 60 minutes starting at Tuesday May 25 15:00 UTC<https://www.timeanddate.com/worldclock/fixedtime.html?msg=DAL&iso=20210525T1500&p1=1440&ah=1>.<br><br>Meeting notes will be kept on this etherpad page<https://yopad.eu/p/IVOA_May21_Astropy>. Please add information, thoughts etc. to help the discussion or to inform possible future sessions. With only 60 minutes, this agenda seems (wildly?) optimistic to me. Maybe some things will be quicker than I expect, but I hope we can at least set up if/how to move forward on these items. I’m also open to other approaches to optimize this time together.<br><br>Thanks,<br>Tom<br><br><br><br>From: Bruno Merin <bruno.merin@sciops.esa.int><br>Date: Thursday, May 20, 2021 at 5:45 AM<br>To: Tom Donaldson <tdonaldson@stsci.edu><br>Cc: Adam Ginsburg <adam.g.ginsburg@gmail.com>, Erik Tollerud <etollerud@stsci.edu>, Clara Brasseur <cbrasseur@stsci.edu>, Brigitta Sipocz <bsipocz@gmail.com>, Thomas Robitaille <thomas.p.robitaille@gmail.com>, TCG IVOA <tcg@ivoa.net>, Baptiste Cecconi <baptiste.cecconi@obspm.fr>, AdaNebot <ada.nebot@astro.unistra.fr>, "Damian, Adrian" <Adrian.Damian@nrc-cnrc.gc.ca>, Christine Banek <CBanek@lsst.org>, Javier Duran <jduran@sciops.esa.int>, AstroPy Coordinators <coordinators@astropy.org>, csp <csp@ivoa.net>, Juan Carlos Segovia <jsegovia@sciops.esa.int><br>Subject: Re: Astropy - IVOA - pyVO follow-up online discussion in May<br><br>Hi all,<br><br>Thanks for the contributions. I do agree that the Paris meeting was a very successful gathering worth following up by both groups. I also like the idea of having a first discussion next week at the IVOA interop meeting plenary session and then to organise a splinter discussion with anyone interested to discuss the details that have been raised.<br><br>I will put together a few summary slides of what we have discussed for the intro presentation and I will share them you you all beforehand to make sure I am not misunderstanding anything. If you could Tom setup that Wiki page to organise a bit the different more detailed points to be discussed afterwards and let people fill in their views in advance of the discussion that would be great. I can help organising the splinter meeting afterwards.<br><br>So, more soon on this topic.<br><br>Thanks again everyone for your time,<br><br>Bruno<br><br><br><br><br><br>On 20 May 2021, at 02:08, Tom Donaldson <tdonaldson@stsci.edu<mailto:tdonaldson@stsci.edu>> wrote:<br><br>Hi Bruno, all,<br><br>I also like Erik’s suggested agenda. Given the time available, I think it would be most productive to minimize presentations, and dive quickly into specific discussions.<br><br>I do like the idea of a brief introduction (<= 10 min?) so that participants old and new have context for the ensuing discussions. Each discussion will need a little setup as well of course, but maybe we can do that informally by seeding the notes page to frame the conversation. Anyone could add info, links, ideas, etc. ahead of time.<br><br>Cheers,<br>Tom<br><br>From: Adam Ginsburg <adam.g.ginsburg@gmail.com<mailto:adam.g.ginsburg@gmail.com>><br>Date: Wednesday, May 19, 2021 at 4:25 PM<br>To: Erik Tollerud <etollerud@stsci.edu<mailto:etollerud@stsci.edu>>, Clara Brasseur <cbrasseur@stsci.edu<mailto:cbrasseur@stsci.edu>><br>Cc: Brigitta Sipocz <bsipocz@gmail.com<mailto:bsipocz@gmail.com>>, Bruno Merin <bruno.merin@sciops.esa.int<mailto:bruno.merin@sciops.esa.int>>, Tom Donaldson <tdonaldson@stsci.edu<mailto:tdonaldson@stsci.edu>>, Thomas Robitaille <thomas.p.robitaille@gmail.com<mailto:thomas.p.robitaille@gmail.com>>, TCG IVOA <tcg@ivoa.net<mailto:tcg@ivoa.net>>, Baptiste Cecconi <baptiste.cecconi@obspm.fr<mailto:baptiste.cecconi@obspm.fr>>, AdaNebot <ada.nebot@astro.unistra.fr<mailto:ada.nebot@astro.unistra.fr>>, "Damian, Adrian" <Adrian.Damian@nrc-cnrc.gc.ca<mailto:Adrian.Damian@nrc-cnrc.gc.ca>>, Christine Banek <CBanek@lsst.org<mailto:CBanek@lsst.org>>, Javier Duran <jduran@sciops.esa.int<mailto:jduran@sciops.esa.int>>, AstroPy Coordinators <coordinators@astropy.org<mailto:coordinators@astropy.org>>, csp <csp@ivoa.net<mailto:csp@ivoa.net>><br>Subject: Re: Astropy - IVOA - pyVO follow-up online discussion in May<br><br>External Email - Use Caution<br>Hi all,<br><br>I'm replying all to add Clara Brasseur, who is also an astroquery maintainer, onto the thread.<br><br>Erik's agenda seems reasonable to me. As Brigitta said, we're looking for ways to remove redundant, parallel implementations from astroquery and make sure the VO tools all live in pyvo.<br><br>On Wed, May 19, 2021 at 3:48 PM Erik Tollerud <etollerud@stsci.edu<mailto:etollerud@stsci.edu>> wrote:<br>To echo Brigitta, I agree the Paris workshop went great, and I think trying to replicate that to whatever extent is possible in the virtual format is a great idea!<br><br>Maybe we should go into it with a list of questions we want to try to answer? Ideally that provides a bit more concreteness to a space where in a virtual format it's rather easy to drift off into doing separate things on our computers, defeating the point of a meeting. The obvious ones I see so far are:<br>• Where TAP/TAP+ belongs between astroquery and pyvo (might need more refining to be a productive discussion!)<br>• VOTable metadata<br>• (maybe) Coordinated status or not<br><br>Perhaps some of those "other smaller things" Brigitta mentioned can be done more in hack-day format? I realize that's not on your schedule Bruno, but to replicate what we saw as success of the Paris event, perhaps we should do that? Perhaps then the discussion segment of the 60 min on the schedule can be discussion of the above items + planning for "hack day" activities to be done async?<br><br><br>On the question of coordinated, I think the question is kind of the other way around: there is *no* extra bureaucracy that I can think of to having it be coordinated given the repo is already in the astropy org. It's really more whether it solves any problems the current package has. From the Astropy Project perspective, having something be coordinated means the Project is a "backstop" against the current maintainer team disappearing - TBH I'm not sure we could commit to that now anyway since most of the Astropy expertise on the VO lives in pyvo already. In return the *users* of that package get some trust that something bigger than an individual is supporting it. In PyVO's case, the IVOA might be just as big/trustworthy of an organization as Astropy would be. There are other smaller things like you get your names on the Astropy team page and get invites to some of the core team events, although in most cases those are in principle open anyway if you're interested enough.<br><br>So it might make sense to consider the coordinated pathway if we think having it be listed on a web site as coordinated will help, say, some of the people on this email chain convince their development team to have a more open process, or have some funding source be more likely to fund developers doing work in an open way. Or if we think the user community is more likely to trust it if it's "coordinated" (which I doubt because I think most non-insiders don't know the distinction). But if not, I agree it's not clear anyone is served by making it coordinated. But if the pyvo maintainers want it, that opinion can change!<br><br><br>---<br>Erik Tollerud<br>Assistant Astronomer<br>Space Telescope Science Institute<br>________________________________<br>From: Brigitta Sipocz <bsipocz@gmail.com<mailto:bsipocz@gmail.com>><br>Sent: Wednesday, May 19, 2021 2:28:48 PM<br>To: Bruno Merin<br>Cc: Tom Donaldson; Erik Tollerud; Thomas Robitaille; Adam Ginsburg; TCG IVOA; Baptiste Cecconi; AdaNebot; Damian, Adrian; Christine Banek; Javier Duran; AstroPy Coordinators; csp<br>Subject: Re: Astropy - IVOA - pyVO follow-up online discussion in May<br><br>External Email - Use Caution<br>Dear All,<br><br>This is an excellent idea to follow-up on our previous meeting, and I'm planning to join, too. I personally feel the Paris workshop was a success, we saw really good momentum and more collaboration than we had before, but of course there are still a number of items that we can work on going forward.<br><br>As to address one of the points below, pyvo currently is an astropy affiliated package. And I feel the maintainer group is very well set up balancing between multiple stakeholders, at least from the sidelines it seems to me that it is working rather well. At the moment I don't see advantages just more bureaucracy of bringing in as a "coordinated" package, there isn't any extra offered for the coordinated ones compared to what pyvo has. We can discuss the nuances, bottom line is that currently bureaucracy what keeps the gates closed.<br><br>I agree with Tom that one of the bigger outstanding questions is TAP. What features should get to be included in the pyvo version (or in the standard) to be able to deprecate the parallel implementation from astroquery. I'm also aware of smaller things that could go into pyvo from either astroquery or astropy, but I think those are more straightforward cases that don't need much coordination from this larger group.<br><br>Cheers,<br> Brigitta<br><br><br>On Thu, 22 Apr 2021 at 10:40, Bruno Merin <bruno.merin@sciops.esa.int<mailto:bruno.merin@sciops.esa.int>> wrote:<br>Dear all,<br><br>I hope my email finds you all and your families well and with good health.<br><br>It is now roughly two years since some of us got together at a nice hackathon in Paris between astropy, astroquery and IVOA software engineers to identify possible synergies and to try to put a collaboration on motion.<br><br>In preparation for the upcoming IVOA online interop meeting from the 25th to the 28th of May, we would like to ask whether you could be available for a follow-up discussion of approx. 1.5 hours, on what worked well, what is ongoing, and what could still do to better for the benefit of the astronomical community as a whole. Among other things, we would like to understand what is pending for pyvo to become an astropy affiliated package and to get your advice on what could be the best use of people’s times in this collaboration or by contributing to astropy.<br><br>Please share your thoughts about this conversation and this collaboration via email and let me know whether you could participate in a session, whose exact date and time is still TBD.<br><br>Many thanks in advance for your time and I look forward seeing you soon,<br><br>Bruno<br><br><br><br>ESA - European Space Agency<br>Dr. Bruno Merín<br>Head of the ESAC Science Data Centre (SCI-SAA)<br>European Space Astronomy Centre (ESAC)<br>Camino Bajo del Castillo s/n<br>Villanueva de la Cañada, 28692 Madrid, Spain<br>Bruno.Merin@esa.int <mailto:bruno.merin@esa.int> | cosmos.esa.int/esdc<https://urldefense.com/v3/__http:/cosmos.esa.int/esdc__;!!CrWY41Z8OgsX0i-WU-0LuAcUu2o!jUyxIG7M2mwZ4C4j1U5-eDCgxNfrOFOLuiBbINDnWPEIVfgPlU0r_8zymN-8Lp8ClQ$><br>Phone: +34 91 813 1456 | Fax: +34 91 813 1218<br><br><br><br>On 20 Mar 2019, at 18:32, Bruno Merin <bmerin@sciops.esa.int<mailto:bmerin@sciops.esa.int>> wrote:<br><br>Dear Tom, Erik, Thomas, Brigitta and Adam,<br><br>We are planning to organize a hackathon on May 15th 2019 in the afternoon at our Paris IVOA interop meeting<https://urldefense.com/v3/__https:/indico.obspm.fr/event/64/overview__;!!CrWY41Z8OgsX0i-WU-0LuAcUu2o!jUyxIG7M2mwZ4C4j1U5-eDCgxNfrOFOLuiBbINDnWPEIVfgPlU0r_8zymN_R4-8UXA$> where we would like to invite people to do hacks that explore the links between astropy/astroquery and the VO infrastructure, in particular focussing possibly on time-domain use-cases.<br><br>Ada Nebot, who is coordinating the IVOA time domain interest group (TDIG), she proposed the following two areas of possible interest / overlap although there might be others:<br><br>1 - VOTable <—> astropy: Conversions between VOTables with the TIMESYS element and the astropy.time class.<br>VOTable: http://www.ivoa.net/documents/VOTable/20190318/<https://urldefense.com/v3/__http:/www.ivoa.net/documents/VOTable/20190318/__;!!CrWY41Z8OgsX0i-WU-0LuAcUu2o!jUyxIG7M2mwZ4C4j1U5-eDCgxNfrOFOLuiBbINDnWPEIVfgPlU0r_8zymN_eeZoJUg$><br>astropy.time http://docs.astropy.org/en/stable/time/index.html<https://urldefense.com/v3/__http:/docs.astropy.org/en/stable/time/index.html__;!!CrWY41Z8OgsX0i-WU-0LuAcUu2o!jUyxIG7M2mwZ4C4j1U5-eDCgxNfrOFOLuiBbINDnWPEIVfgPlU0r_8zymN_4ujnxvA$><br><br>2 - T-MOC & astropy : The T-MOC format is a time-dependent Multi-Order Coverage structure, e.g. a healpix structure that indexes spatially the existing data in the sky (that is the MOC), but chopped off in time intervals to allow easy visualization and access to data in both space and time (that is the T-MOC).<br>https://wiki.ivoa.net/internal/IVOA/InterOpMay2018TDIG/TDIG-TBoch-TMOC-MOCPy.pdf<https://urldefense.com/v3/__https:/wiki.ivoa.net/internal/IVOA/InterOpMay2018TDIG/TDIG-TBoch-TMOC-MOCPy.pdf__;!!CrWY41Z8OgsX0i-WU-0LuAcUu2o!jUyxIG7M2mwZ4C4j1U5-eDCgxNfrOFOLuiBbINDnWPEIVfgPlU0r_8zymN_YuF9fmw$><br>https://github.com/cds-astro/mocpy/blob/master/notebooks/tmoc.ipynb<https://urldefense.com/v3/__https:/github.com/cds-astro/mocpy/blob/master/notebooks/tmoc.ipynb__;!!CrWY41Z8OgsX0i-WU-0LuAcUu2o!jUyxIG7M2mwZ4C4j1U5-eDCgxNfrOFOLuiBbINDnWPEIVfgPlU0r_8zymN_RitrISg$><br><br>The reason of my message is to inform you about this hackathon, ask for your feedback on whether this would be of interest or not for some of the astropy developers and to ask for advice on how do you think this event could be more useful to both the astropy users and IVOA users. It would also be great if you would know some astropy contributor who might be based in Paris and might want to come in person to the session.<br><br>Finally, should you be interested, you are all of course invited to join any of the two telecons described below where we will discuss what to prepare and how to organize the hackathon.<br><br>Thanks in advance for your time,<br><br>Bruno<br><br><br><br><br>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<br><br>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<br><br>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<br><br>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int<mailto:dpo@esa.int>).<br><br><br><br><br>--<br>Adam Ginsburg<br>Assistant Professor, Department of Astronomy<br>University of Florida, Gainesville<br>http://www.adamgginsburg.com/<https://urldefense.com/v3/__http:/www.adamgginsburg.com/__;!!CrWY41Z8OgsX0i-WU-0LuAcUu2o!n8O5EP640h9zWnAAbmYhyNooHAWmgHDuKpLFKgwlkRIAXhpi8GXNcLcz5mVDYTPF5Q$><br><br><br>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<br><br>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<br><br>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<br><br>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<br></div></div><PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE></body></html>