As per the Out-of-cycle funding request: Astropy workshops at Hawaiian observatories funding request (between Cycles 3 and 4), Astropy will hold a series of one-day Astropy workshops/open consultation with major observatories in Hawaii (Subaru, Gemini, Keck, CFHT, SMA, etc.) over the course of one week, culminating in a day of open "office hours" by the Astropy Project team.

The goal of the workshops is threefold:

• Increase the adoption of Astropy (both core astropy and Astropy Affiliated packages) in the workflow of Hawaii Island Observatories.
• Encourage participation of observatory scientists and developers in the development of astropy and Astropy Affiliated packages.
• Identify priority areas for Astropy development to facilitate adoption of astropy and Astropy Affiliated packages.

Contents:

• Logistics
• Remote Participation
• Agenda
• Discussions/links
• Code of Conduct
• SOC
• LOC

Hosts: Subaru Telescope and Keck Observatory
Dates: December 2–6, 2024
Venue:
🔭 Subaru Telescope: 650 North A'ohoku Place, Hilo, HI 96720
🔭 W. M. Keck Observatory Headquarters: 65-1120 Mamalahoa Hwy, Waimea, HI 96743
Timezone: Hawaii-Aleutian Standard Time (GMT-10)

(Back to top)

💻 Zoom link for Subaru
💻 Zoom link for Keck (Day 1)
💻 Zoom link for Keck (Day 2)

Not all events on the schedule will be available remotely. Events available for remote participation will be marked with a 💻 icon in the Agenda below.

(Back to top)

We will deliver two large workshops, one in Hilo at Subaru Telescope Base Facility and one in Waimea at the Keck Observatory Base Facility, with a less formal training session and opportunities for one-on-one help the next day at each observatory.

The rough outline of each workshop day will be:

1. Brief overview of astropy and Astropy Affiliated packages (30 minutes)
2. More detailed presentation on those areas that the observatories have indicated are of greatest interest to them (2 hours)
3. Lunch (1 hour)
4. Deeper dive into additional topics identified in the morning session (1 hour)
5. Office hours/"code along" help with astronomers and developers to facilitate moving towards an Astropy-based workflow (2 hours)

While no preparation is required, we encourage you to set up a Python environment and download workshop materials in advance.

Installation instructions are at https://github.com/astropy/astropy-workshop/tree/ALOHA-2024/00-Install_and_Setup

The workshop will be delivered as a series of Jupyter notebooks. We anticipate making changes to the content through the weekend before the workshops. The materials are on the ALOHA-2024 branch of the astropy-workshop repository. The direct link to that branch is: https://github.com/astropy/astropy-workshop/tree/ALOHA-2024

• 10:00 AM - 10:30 AM: 💻 Intro to astropy package and orientation to the Astropy ecosystem by Matt Craig
• 10:30 AM - 11:00 AM: 💻 More astropy fundamentals and science examples by Matt Craig
• 11:00 AM - 11:30 PM: 💻 Visualization options with astropy and Python by Erik Tollerud
• 11:30 AM - 12:00 PM: 💻 Visualization Q&A / User stories
• 12:00 PM - 01:30 PM: Lunch
• 01:30 PM - 02:30 PM: 💻 Photometry with Astropy by Pey Lian Lim
• 02:30 PM - 04:30 PM: Office hours / "code along"
• $\color{gray}{Organizers' \space BBQ \space (private \space event)}$

• 10:00 AM - 10:30 AM: 💻 Spectroscopy with Astropy by Erik Tollerud
• 10:30 AM - 11:00 AM: 💻 Spectroscopy continued / Q&A
• 11:00 AM - 11:30 PM: 💻 DevOps Q&A by Pey Lian Lim
• 11:30 AM - 12:00 PM: 💻 More astropy science use cases by Matt Craig
• 12:00 PM - 01:30 PM: Lunch
• 01:30 PM - 02:30 PM: Deeper dive (a couple of topics based on participants interest/needs)
• 02:30 PM - 04:30 PM: Office hours / "code along"
• $\color{gray}{Organizers' \space picnic \space and \space observation \space shadowing \space (private \space event)}$

• 10:00 AM - 10:30 AM: 💻 Intro to astropy package and orientation to the Astropy ecosystem by Matt Craig
• 10:30 AM - 11:00 AM: 💻 More astropy fundamentals and science examples by Matt Craig
• 11:00 AM - 11:30 AM: 💻 Visualization options with astropy and Python by Erik Tollerud
• 11:30 AM - 12:00 PM: 💻 Visualization Q&A / User stories
• 12:00 PM - 01:30 PM: Lunch
• 01:30 PM - 02:30 PM: 💻 DevOps Q&A by Pey Lian Lim / discussion
• 02:30 PM - 04:30 PM: Office hours / "code along"
• $\color{gray}{Organizers' \space overnight \space stay \space (tentative, private \space event)}$

• 10:00 AM - 10:30 AM: 💻 Photometry with Astropy by Pey Lian Lim
• 10:30 AM - 11:00 AM: 💻 Photometry continued / Q&A
• 11:00 AM - 11:30 AM: 💻 Spectroscopy with Astropy by Erik Tollerud
• 11:30 AM - 12:00 PM: 💻 More astropy science use cases by Matt Craig
• 12:00 PM - 01:30 PM: Lunch
• 01:30 PM - 02:30 PM: Deeper dive (topic based on participants interest)
• 02:30 PM - 04:30 PM: Office hours / "code along"
• 06:00 PM - 07:00 PM: Group dinner at Hilo Town Tavern in Hilo
• 07:00 PM - 09:00 PM: Astronomy On Tap at Hilo Town Tavern in Hilo, by Matt Craig

$\color{gray}{Organizers' \space Subaru/Keck/IRTF \space observatory \space tours \space (private \space event)}$

(Back to top)

• SkyCoord constructor API seems complicated but is being revisited in APE26: Removing data storage (representations) from coordinate frames.
• Performance Tips might help if you run into performance issues using astropy.coordinates. Also see Fast In-Place Modification of Coordinates, Usage Tips/Suggestions for Methods That Access Remote Resources, and Solar System Ephemerides.

• Why use CCDData over NDData? CCDData propagates uncertainties properly during operations and provides convenience functions assuming CCD properties.

• Why is Astropy Table necessary when there is pandas? Please see DOC: Why use astropy Table/QTable over pandas DataFrame.

• DOC: Performance discussion on Time.

• What is the future of Astropy Quantity? Astropy is currently prototyping Quantity 2.0. Related links:
  • units and constants and NEP 42
  • Quantity 2.0 APE proposal
  • Quantity 2.0 prototype
• How to make Astropy units more performant? Please see tips at Performance Tips for units.
• Can you write your own unit conversion equivalancy? Yes, please see Writing New Equivalencies.

• What does quantity_support actually change? To see the actual implementation, given astropy is open-source, you could see the source code in astropy/visualization/units.py.
• How do you make custom stretch in astropy.visualization? You can subclass from BaseStretch. That said, there is an exhaustive list of the various stretches, therefore the need to write a custom stretch from scratch is probably an edge case.
• Does WCSAxes draw correct lines when WCS have distortion?

• Astropy IERS auto-downloading controls: https://docs.astropy.org/en/stable/utils/iers.html#configuration-parameters

• Does uncertainty mean error? Yes, and there are multiple ways to define it, and users have to tell specutils what kind it is (from given choices) before passing it into Spectrum1D.
• How did Subaru PFS loader get into specutils? It was added in 2019 via specutils Pull Request 431 by @gpernot from Marseille, and approved by @SaOgaz and @eteq. Subaru staff should probably check it to make sure the loader is still correct now.
• Does specutils have built-in line lists? No, but you could grab them from astroquery. Additionally, for visualization, you could also use the Line Lists plugin in Specviz.

• Core ipywidgets package
• Several years of Jupyter widget tutorials are available as a repo and on the SciPy YouTube channel. This set starts with bare-bones widgets builds to more complex examples.
• A newer set of tutorials covers widgets at a higher level.
• If you need to include some basic JavaScript in a widget then check out anywidget.

• The Hertzsprung-Russell diagram notebook that was demonstrated as a science use case at Subaru is here.
• When you have to see, say, where outliers in a color-magnitude diagram fall on the image data, Glue is a good visualization tool to use.

• Is Astropy going to replace IRAF and Source Extractor? Yes and no; Astropy is aiming to replace most general functionality but probably not the instrument specific stuff.
• APE 20: Formatting Code with Black
• To what level should astropy be typed? (open discussion)
• Astropy has 5 years of NASA funding!, so if you have projects in mind to collaborate with Astropy that could benefit from this, please reach out to us!
• How do we keep in touch after the workshop? Please see Astropy communication channels at Astropy Help page. Slack is probably the most active at the time of writing.

(Back to top)

This meeting will be governed by the Astropy Code of Conduct. Our goal is to keep ours a positive, inclusive, successful, and growing community. We hold our community members, especially our core developers and project leaders, to a high bar of inclusive behavior.

Please report violations to any member of the SOC or Ombudsperson.

(Back to top)

• Matt Craig (Minnesota State University Moorhead)
• Pey Lian Lim (STScI)

(Back to top)

• Eric Jeschke (Subaru, NAOJ)
• Jennie Berghuis (Gemini North, NOIRLab)
• Sherry Yeh (Keck Observatory)

(Back to top)