Skip to content

Yalemeeting2013

Jump to bottom Edit New page
Erik Tollerud edited this page Oct 9, 2013 · 76 revisions

Astropy Coordination Meeting 2013

This coordination meeting was held October 7-8, 2013 at the Leitner Family Observatory and Planetarium, Yale University, New Haven, CT, USA

Important Links

Planned Attendees

These people intend to be physically present for the meeting.

  • Erik Tollerud (Yale University)
  • Adam Ginsburg (ESO)
  • John Parejko (Yale University)
  • Adrian Price-Whelan (Columbia University) (Tuesday only)
  • Michael Droettboom (STScI)
  • Jonathan Foster (Yale University)
  • Kelle Cruz (Hunter College, CUNY & AMNH)
  • Miguel de Val-Borro (Princeton University)
  • Dan Foreman-Mackey (NYU)
  • Perry Greenfield (STScI)
  • Nadia Dencheva(STScI)
  • Pey Lian Lim (STScI)
  • Demitri Muna (OSU)
  • Tom Aldcroft (SAO/CfA)
  • Benjamin Weaver (NYU)
  • Joanna Corby (UVa)
  • Russell Hewett (MIT)
  • Marten van Kerkwijk (Toronto)

Planned Remote Attendees

These people would like to attend via videoconference.

  • Thomas Robitaille (MPIA)
  • Tim Jenness (Cornell)
  • James Turner (Gemini)
  • Alex Hagen (Penn State)
  • David Shupe (IPAC/Caltech)
  • Steve Crawford (SAAO)
  • Moritz Günther (SAO/CfA) [for part of the time]
  • Stuart Mumford (Sheffield University)
  • Kyle Barbary (Argonne) [part of the time]
  • Wolfgang Kerzendorf (UofT) [part of the time]

Lodging

A block of rooms will be reserved at the New Haven Hotel, with booking details to follow soon. There are also a wide range of other lodging options available in New Haven, so you are welcome to book as you prefer. Note that there is a free Yale Shuttle that you are welcome to use to get to campus from much of New Haven.

Schedule

Oct 7: Discussion Day

  • 8-9a: Arrival and coffee/breakfast (provided)
  • URLs for remote attendance and shared google docs will be posted during this time.
  • Provide your lunch order (menu)
  • 9a-10:15p: Overviews and general news
  • Erik T: Welcome and overview
  • Perry G: Astropy/STScI development news
  • Tom R: Astropy paper and affiliated packages
  • Kelle C.: Astropy community-building
    • Plenary Discussion: How do we make sure the community-building happens?
  • 10:15-10:45p: Coffee break
  • 10:45a-12: Brief progress reports and plenary discussions
  • Plenary Discussion (Erik T.): Do we want to change our rate and the meaning of releases? (And change version numbering to match?)
  • Russell H. / Stuart M.: SunPy and Astropy
  • Nadia D.: modeling package progress
  • Plenary Discussion (Perry G.): Shall we start doing "Astropy Enhancement Proposals" for major changes?
  • Tom A.: tables, time, and io.ascii packages
  • Adam G.: astroquery progress and demo (http://slideviewer.herokuapp.com/urls/github.com/keflavich/astroquery/raw/master/docs/demos/Astroquery_DotAstro_Demo.ipynb)
  • 12-1p: Lunch
  • 1-1:30p: Discuss breakout session topics and goals
  • Planned sessions will be posted on a google doc to facilitate remote participation
  • 1:30p-2:20p: Breakout sessions I
  • 2:30p-3:20p: Breakout sessions II
  • 3:30p-4:20p: Breakout sessions III
  • 4:30-5p: Summary of breakout session discussions
  • 5-6p: Plenary Discussion: What are the development priorities for the next year? And who will do it?
  • 6p on: Group dinner

Oct 8: Coding Sprint Day

  • 8-9a: Arrival and coffee/breakfast
  • Please post your plans for the day on the google doc to facilitate remote participation
  • Provide your lunch order (menu)
  • 9a-12p: Code/hack/discuss
  • 12-1p: Lunch (menu)
  • 1p-5p: Code/hack/discuss
  • 5p: Summary of sprints and closing remarks
  • 7p: Public science talk and open viewing on Leitner Observatory telescopes (if weather cooperates)

Topic suggestions

Below are some suggestions for specific topics to be addressed at the meeting. This is not a definitive list, but will be seriously considered by those who attend the meeting (as they will determine what is actually discussed):

  • What should we aim to have in 1.0 release?

  • When should we have a 1.0 release/should we have a clear version numbering scheme?

  • How should we move forward with nddata (and dependent affiliated package) development?

  • Is the configuration system being used at all? How might it be made more useful? (+1 @mdboom, @pllim)

  • What is the next main functionality that should go in the core? (i.e. what is 0.4 or 1.0, whichever comes next?)

  • How do we move forward with the generalized WCS? (@nden)

  • How do we faciliate getting people involved? We need a place where people can go and see what projects within Astropy are going on (similar to the GSoC list of projects), which ones are active, on hold, in need of a leader, in need of certain expertise, etc. The issue list is a little intimidating, and we need something higher level. (addendum - note that this is beyond just the core package, so maybe not appropriate as issues in the core package anyway?) (+1 @pllim, +1 @mhvk - a "big issue" tag?)

  • @mdboom offers to give a "six" tutorial for writing portable code without 2to3 if there is interest. (+1 @keflavich)

  • Coordinating common data containers (NDData) with Sunpy (and other projects? Table with Pandas?)

  • Coordinating Units with other implementations (e.g., amuse); ability to cross-talk, use in matplotlib? (@mhvk)

  • Further integration of quantities: e.g., should table columns with units start to return quantities?

  • Special dtype for quantities? Start implementing uncertainties? (@mhvk)

  • Plans to move STScI pysynphot to astropy (+1 @pllim, @mhvk, @kbarbary). Related: coordination of pysynphot with specutils? (@kbarbary)

  • Coordinates and Time for observatories/observations: proper geocentric XYZ coordinates, barycentering (ideally at VLBI/pulsar timing precision level, includes finalizing IERS, implementing JPL ephemerides; @mhvk)(+1 @keflavich)

  • Testing standards against reference/other implementations (@mhvk)

  • For which packages can we guarantee the API?

  • How much do we want to worry about test coverage? Some sub-packages have e.g. 70% test coverage - is that ok, or should we aim for more? Don't want to require 100% for contributions as this probably sets the bar too high, but how about a sprint to increate testing coverage?

  • Is it time to think about having Astropy Enhancements Proposals (AEP - ok, not a great acronym) - i.e. a formalized way to propose large-ish changes and vote on them, but for things that aren't quite as detailed as API proposals? (+1 @keflavich)

  • How to continue with modeling (alternate API/design, future features and priorities)?(@nden)

  • Spectral coordinate classes (this may be discussed with the generalized WCS)?(@nden) (+1 @keflavich)

  • What documentation (for users) is most needed? What format should this take?

  • Brainstorm on main website re-design?

  • Breakout Sessions Sign-up/Suggestion sheet

Add a custom footer
Add a custom sidebar
Clone this wiki locally