[csp] Astropy - IVOA - pyVO follow-up online discussion in May

[Adam Ginsburg]

Hi Bruno,
    I'll come to the meeting next week on Tuesday - am I allowed to come
without registering?  If so, can you share the zoom link when it is
available?

On Wed, May 19, 2021 at 11:05 AM Bruno Merin <bruno.merin at sciops.esa.int>
wrote:

> Thanks very much for your positive response Adrian,
>
> I really like the idea of coordinating a single pyvo presentation via
> slack. I have for now added a placeholder presentation for Tom Donaldson on
> the experience at MAST contributing to astropy/astroquery and another one
> by you on the CADC experience of contributing to pyVO.
>
> I just realise now that I had not copied Christine in my first emails on
> this topic (my apologies Christine! I hope you are fine! ;) but I think it
> would be great to hear from the three main current pyvo maintainers,
> namely, Adrien Damian for CADC, Christine Banek for VRO and Javier Durán
> for ESA, on their experiences contributing code to pyvo and/or astroquery
> from our different organisations. This could be as Adrian suggests in a
> single presentation of in separate ones, as you prefer. We have a full hour
> for the session.
>
> And, as I said, it would be really great to have some inputs from the
> astropy core or astroquery teams as well as on how would you guys would
> like to see these contributions coming and how much coordination might be
> useful to get things flowing most efficiently. Would that be possible?
>
> Many thanks in advance everybody and I look forward discussing with you
> all next week.
>
> Bruno
>
>
> On 18 May 2021, at 20:22, Damian, Adrian <Adrian.Damian at nrc-cnrc.gc.ca>
> wrote:
>
> Thanks for organizing this, Bruno.
>
> It’s an excellent idea.
>
> I’m available to contribute to this effort. For efficiency, we could use
> slack to coordinate on the details of the `pyvo` presentation, if that’s OK
> with you.
>
> Cheers,
> Adrian
>
> On May 13, 2021, at 9:47 AM, Bruno Merin <bruno.merin at sciops.esa.int>
> wrote:
>
> ****ATTENTION*** This email originated from outside of the NRC.
> ***ATTENTION*** Ce courriel provient de l'extérieur du CNRC*
> Thanks Tom,
>
> We have just had programmed a session of 60 minutes on Tuesday May the
> 25th at 15:00 UTC to discuss about these topics. See the full draft agenda
> of the meeting here
> <https://wiki.ivoa.net/twiki/bin/view/IVOA/InterOpMay2021>.
>
> I would like to propose to have a presentation by Tom, possibly followed
> by a few slides from any of the pyvo maintainers at LSST, CADC or ESA if
> possible, and then followed possibly by someone from the astropy core team
> and then to leave some minutes for an open discussion on how to make the
> contribution of IVOA members to the astropy project more successful in the
> future. What do you think?
>
> Would any of you volunteer to make such small (rather informal)
> presentation? Hopefully a short discussion later in the month could help
> our two communities continue to improve further our currently working
> collaboration. Please feel free to bring up any issues that you would
> prefer to discuss beforehand and we can certainly have a short zoom meeting
> if you guys think that would help making the meeting more efficient.
>
> Many thanks in advance for your time,
>
> Bruno
>
>
> On 12 May 2021, at 16:44, Tom Donaldson <tdonaldson at stsci.edu> wrote:
>
> Hi Bruno,
>
> I’m interested in this discussion and am certainly available for the IVOA
> meeting.  As you say, at a high level it will be interesting to discuss
> what is going well and what could work better, and what the current
> thinking is on pyvo becoming an astropy coordinated package.  IVOA
> contributions to pyvo (and astropy) have been increasing, but more
> participation would obviously be better.  These lower level specific
> questions regarding where VO functionality should be built and maintained
> may also help inform the discussion:
>
>
>    - What is the timeline for deprecating TAPPlus in astroquery in favor
>    of a unified pyvo TAP implementation?  See
>    https://github.com/astropy/astroquery/pull/2034
>    - Where should handling of VOTable metadata live?  A specific instance
>    of this is here:https://github.com/astropy/astroquery/issues/2036
>
>
> Cheers,
> Tom
>
>
> *From: *Bruno Merin <bruno.merin at sciops.esa.int>
> *Date: *Thursday, April 22, 2021 at 1:40 PM
> *To: *Tom Donaldson <tdonaldson at stsci.edu>, Erik Tollerud <
> etollerud at stsci.edu>, Thomas Robitaille <thomas.p.robitaille at gmail.com>,
> Brigitta Sipocz <bsipocz at gmail.com>, Adam Ginsburg <
> adam.g.ginsburg at gmail.com>, TCG IVOA <tcg at ivoa.net>, Baptiste Cecconi <
> baptiste.cecconi at obspm.fr>, AdaNebot <ada.nebot at astro.unistra.fr>,
> "Damian, Adrian" <Adrian.Damian at nrc-cnrc.gc.ca>, Kelle Cruz <
> kellecruz at gmail.com>, Christine Banek <CBanek at lsst.org>, Javier Duran <
> jduran at sciops.esa.int>
> *Cc: *AstroPy Coordinators <coordinators at astropy.org>, csp <csp at ivoa.net>
> *Subject: *Astropy - IVOA - pyVO follow-up online discussion in May
>
> Dear all,
>
> I hope my email finds you all and your families well and with good health.
>
> 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.
>
> 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.
>
> 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.
>
> Many thanks in advance for your time and I look forward seeing you soon,
>
> Bruno
>
>
>
> *ESA - European Space Agency*
> Dr. Bruno Merín
> Head of the ESAC Science Data Centre (SCI-SAA)
> *European Space Astronomy Centre (ESAC)*
> Camino Bajo del Castillo s/n
> Villanueva de la Cañada, 28692 Madrid, Spain
> Bruno.Merin at esa.int  <bruno.merin at esa.int>| cosmos.esa.int/esdc
> Phone: +34 91 813 1456 | Fax: +34 91 813 1218
>
>
> On 20 Mar 2019, at 18:32, Bruno Merin <bmerin at sciops.esa.int> wrote:
>
> Dear Tom, Erik, Thomas, Brigitta and Adam,
>
> We are planning to organize a hackathon on May 15th 2019 in the afternoon
> at our Paris IVOA interop meeting
> <https://indico.obspm.fr/event/64/overview> 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.
>
> 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:
>
> 1 - VOTable <—> astropy: Conversions between VOTables with the TIMESYS
> element and the astropy.time class.
> VOTable: http://www.ivoa.net/documents/VOTable/20190318/
> astropy.time http://docs.astropy.org/en/stable/time/index.html
>
> 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).
>
> https://wiki.ivoa.net/internal/IVOA/InterOpMay2018TDIG/TDIG-TBoch-TMOC-MOCPy.pdf
> https://github.com/cds-astro/mocpy/blob/master/notebooks/tmoc.ipynb
>
> 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.
>
> 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.
>
> Thanks in advance for your time,
>
> Bruno
>
>
>
>
>
> 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 at esa.int).
>
>
> 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 at esa.int).
>
>
>
>
>
> 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 at esa.int).
>
>
>

-- 
Adam Ginsburg
Assistant Professor, Department of Astronomy
University of Florida, Gainesville
http://www.adamgginsburg.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/csp/attachments/20210519/c3f6e24c/attachment-0001.html>