<div dir="ltr"><div dir="ltr"><div>Dear All,</div><div><br></div><div>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></div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Cheers,</div><div> Brigitta</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 22 Apr 2021 at 10:40, Bruno Merin <<a href="mailto:bruno.merin@sciops.esa.int">bruno.merin@sciops.esa.int</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;">Dear all,<div><br></div><div>I hope my email finds you all and your families well and with good health.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Many thanks in advance for your time and I look forward seeing you soon,</div><div><br></div><div>Bruno</div><div><br></div><div><br></div><div><div><div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="background-color:rgb(255,255,255);color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br><font style="color:rgb(0,0,0)" size="1" face="Verdana" color="#808080"><b>ESA - European Space Agency</b></font><p style="color:rgb(0,0,0)"><font size="1" face="Verdana" color="#00a1e0">Dr. Bruno Merín</font><font size="1" face="Verdana" color="#808080"><br>Head of the ESAC Science Data Centre (SCI-SAA)</font><font size="3"></font></p><p style="color:rgb(0,0,0)"><font size="1" face="Verdana" color="#808080"><b>European Space Astronomy Centre (ESAC)</b><br>Camino Bajo del Castillo s/n<br>Villanueva de la Cañada, 28692 Madrid, Spain</font></p><p><a href="mailto:bruno.merin@esa.int" style="color:rgb(0,0,0)" target="_blank"><font size="1" face="Verdana" color="#808080"><u>Bruno.Merin@esa.int </u></font></a><font style="color:rgb(0,0,0)" size="1" face="Verdana" color="#808080">| </font><a href="http://cosmos.esa.int/esdc" target="_blank"><font size="1" color="#808080">cosmos.esa.int/esdc</font></a><font style="color:rgb(0,0,0)" size="1" face="Verdana" color="#808080"><br>Phone: +34 91 813 1456 | Fax: +34 91 813 1218</font></p></div></div></div></div></div></div></div></div></div>
</div>
<div><br><blockquote type="cite"><div>On 20 Mar 2019, at 18:32, Bruno Merin <<a href="mailto:bmerin@sciops.esa.int" target="_blank">bmerin@sciops.esa.int</a>> wrote:</div><br><div><div style="overflow-wrap: break-word;">Dear Tom, Erik, Thomas, Brigitta and Adam,<div><br></div><div>We are planning to organize a hackathon on May 15th 2019 in the afternoon at our Paris IVOA <a href="https://indico.obspm.fr/event/64/overview" target="_blank">interop meeting</a> 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. </div><div><br></div><div>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:</div><div><br></div><div><div>1 - VOTable <—> astropy: Conversions between VOTables with the TIMESYS element and the astropy.time class.</div><div>VOTable: <a href="http://www.ivoa.net/documents/VOTable/20190318/" target="_blank">http://www.ivoa.net/documents/VOTable/20190318/</a></div><div>astropy.time <a href="http://docs.astropy.org/en/stable/time/index.html" target="_blank">http://docs.astropy.org/en/stable/time/index.html</a></div><div><br></div><div>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).</div><div><a href="https://wiki.ivoa.net/internal/IVOA/InterOpMay2018TDIG/TDIG-TBoch-TMOC-MOCPy.pdf" target="_blank">https://wiki.ivoa.net/internal/IVOA/InterOpMay2018TDIG/TDIG-TBoch-TMOC-MOCPy.pdf</a></div><div><a href="https://github.com/cds-astro/mocpy/blob/master/notebooks/tmoc.ipynb" target="_blank">https://github.com/cds-astro/mocpy/blob/master/notebooks/tmoc.ipynb</a></div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Thanks in advance for your time,</div><div><br></div><div>Bruno</div><div><br></div><div><br></div></div></div></div></blockquote></div><br></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 (<a href="mailto:dpo@esa.int" target="_blank">dpo@esa.int</a>).
</pre></div></blockquote></div></div>