Category Archives: presentations

Lightning talk at ADASS XXX: Making organizational software easier to find

The excellent ADASS XXX conference concluded yesterday. I missed meeting ADASS attendees face-to-face, but was delighted to spend time with them safely online, to learn about their projects and research, to talk about software and data, to share what the ASCL has been doing, and to meet old and new friends. The all-virtual conference was just about perfect; the technology set-up was excellent, providing opportunities to see sessions as they happened or at a later time on video, ask questions, comment on and discuss what was presented, and have one-on-one or small group video calls. The schedule was easy to keep track of, as one could subscribe to the schedule and get updates to it (mostly additions) immediately. Support was extremely responsive; an online Help Desk provided answers to queries almost immediately. There was even a conference photo!

Poster presenters were invited to record and upload a lightning talk — no more than three minutes — for their posters; two-minute lightning talks via Zoom were also arranged at the conference. The ASCL presented a poster on Making organizational software easier to find in ASCL and ADS; the hastily-put-together lightning talk presented at the conference for this poster is below.

ADASS attendee Simón Torres offered to download all the pre-recorded lightning talks and stream them during the conference, so a Poster Video Watching Party was scheduled for Wednesday afternoon. The stream was great fun to watch! It was interesting, too, to see all the different ways people presented their lightning talks.

What a great conference this was! I look forward to next year’s!

ASCL poster on NASA software project at ADASS XXX


Software is the most used instrument in astronomy, and organizations such as NASA and the Heidelberg Institute for Theoretical Physics (HITS) fund, develop, and release research software. NASA, for example, has created sites such as code.nasa.gov and software.nasa.gov to share its software with the world, but how easy is it to see what NASA has? Until recently, searching NASA’s Astrophysics Data System (ADS) for NASA’s astronomy software has not been fruitful. Through its ADAP program, NASA has funded the Astrophysics Source Code Library (ASCL ascl.net) to improve the discoverability of these codes. Adding institutional tags to ASCL entries makes it easy to find this software not only in the ASCL but also in ADS and other services that index the ASCL. This poster presentation covers the changes the ASCL has made as a result of this funding and how you can use the results of this work to better find organizational software in ASCL and ADS.

Download poster (PDF)

ASCL API poster at ADASS XXX

Poster about ASCL API
We have developed an API for the Astrophysics Source Code Library (ASCL) that enhances the ability of users to conduct complex and automated queries on ASCL indexed codes. The API is public and allows anyone to programmatically search and filter the ASCL software database via an HTTP request. For example, the search https://ascl.net/api/search/?q=%22supernova%22&fl=credit returns a list of authors with ASCL-indexed codes involving supernovae in JSON format. We will demonstrate the API and show its use in answering a researcher’s questions regarding the growth and usage of both interpreted and compiled languages in the database, gaining a more nuanced understanding of trends in astrophysics software development. Our findings confirmed a piece of conventional wisdom: that Python is growing in market share, while low level programming languages like C and C++ remain very popular. Further documentation for the API is available at https://github.com/teuben/ascl-tools/tree/master/API.

Siddha Mavuram (UMD), Alice Allen (ASCL/UMD), Robert J. Nemiroff (MTU), Judy Schmidt (ASCL), Peter J. Teuben (UMD)

Download poster (PDF)

ADASS 2020 in the time of pandemic

Astronomical Data Analysis Software and Systems (ADASS), which was to have been in Granada, Spain this year, kicked off the fully online ADASS XXX meeting yesterday with four tutorials, as is usually done, though not quite like it was done this year. The Programming Organizing Committee and especially the Local Organizing Committee had to convert a conference that had been two years in the planning to a virtual meeting. This offered numerous challenges and learning opportunities! One challenge is that the conference is international; scheduling sessions for access to all participants couldn’t have been easy, but with the technology stack they chose, which includes the conference website, Zoom, YouTube, and Discord, and hard work, all of ADASS’s resources are available to all participants. One might have to get up early or stay up late to hear all of the talks live — the sleep-deprived author of this post awoke at 12:15 AM today to catch the opening sessions — but there are asynchronous options available, so groggy stumbling as one makes her way to the computer is a choice, not a requirement.

The ASCL has several presentations and activities this year. ASCL Chair Peter Teuben, ASCL Advisory Committee member Bruce Berriman, and I organized a Birds of a Feather (BoF) session on How to better describe software for discovery and citation today. We have organized BoFs focused on some aspect of software in the past, and, as in the past, this BoF offered a number of very short presentations and then open discussion.

The BoF session focused on software metadata, to improve how software is described and can be discovered and cited. After Teuben opened the session, Berriman presented his experience with using CiteAs to see how it suggested his software Montage be cited. CiteAs uses numerous ways to find a code’s citation method, including looking for metadata files — specific files that contain metadata for the software — on the code’s website and/or GitHub repository. Montage does not currently have a metadata file on its sites, so the citation method CiteAs suggested was not as robust as it could have been. The results of the search and its provenance are shown in the BoF’s slides, which can be downloaded at a link below.

This led nicely into my short talk on metadata files and how the ASCL can create a metadata file from an ASCL entry. The files the ASCL creates programmatically, codemeta.json and CITATION.cff, are intended to be starting points and contain placeholders for data the ASCL does not capture, but which we feel should be included in the metadata file; we encourage software authors to edit these files before they are placed on one’s code site.

Yan Grange, who had organized an earlier BoF on Best licensing practices, presented a summary of the session and the results of two of the several polls taken during that BoF.  Providing a license for your software is vitally important, as it lets others know what they can and cannot do with your software. Resources and other information from the earlier BoF are available online, and Grange’s summary slides for our software metadata BoF are included in the slides file below.

Teuben presented on several related topics: expanding or deepening a codemeta file with “API” information, the Unified Astronomy Thesaurus (UAT) and keywords, and the possibility of taking a software census at a niche science meeting. For this latter, he would like to take a well-defined field in astrophysics and have members of that community take an inventory of the software used and categorize it. He thinks a conference would be an ideal event for getting all the stakeholders together, and has identified a possible candidate conference for this activity.

The floor, if there can be a floor in a virtual meeting, was then open for comments, questions, answers and ideas, though discussion had already started in the Discord channel. One outcome of this session was that before the end of it, several participants had added metadata files to code repositories!

All slides for this session are in the PDF file below. If you would like more information about the session, please let us know in the comments section below, pinging us at ADASS if you are participating in the meeting, or by emailing me at editor@ascl.net.

Slides (PDF)

ASCL poster at AAS235


Abstract: Software citation is good for research transparency and reproducibility, and maybe, if you work it right, for your CV, too. You can get credit and recognition through citations for your code! This presentation highlights several powerful methods for increasing the probability that use of your research software will be cited, and cited correctly. The presentation covers how to create codemeta.json and CITATION.cff automagically from Astrophysics Source Code Library (ASCL ascl.net) entries, edit, and use these files, the value of including such files on your code site(s), and efforts underway in astronomy and other fields to improve software citation and credit.

Authors: A. Allen1,2, R. Nemiroff3, P. Ryan1, J. Schmidt1, P. Teuben2
1Astrophysics Source Code Library
2Astronomy Department, University of Maryland, College Park, MD
3Michigan Technological University, Houghton, MI

Download (PDF)

The ASCL at AAS 235

The ASCL is participating in the American Astronomical Society (AAS) meeting that started yesterday in Honolulu, Hawai’i. We have two events, both on Sunday, January 5:

Best ways to let others know how to cite your research software
January 5; Poster 109.12
Software citation is good for research transparency and reproducibility, and maybe, if you work it right, for your CV, too. You can get credit and recognition through citations for your code! This presentation highlights several powerful methods for increasing the probability that use of your research software will be cited, and cited correctly. The presentation covers how to create codemeta.json and CITATION.cff automagically from Astrophysics Source Code Library (ASCL ascl.net) entries, edit, and use these files, the value of including such files on your code site(s), and efforts underway in astronomy and other fields to improve software citation and credit.

The Future and Future Governance of the Astrophysics Source Code Library
January 5, 2:00 PM – 3:30 PM; HCC – Room 301B
Over the past ten years, the Astrophysics Source Code Library (ASCL, ascl.net) has grown from a small repository holding about 40 codes with hand-coded HTML pages maintained by one person to a resource with citable entries on over 2000 codes with a modern database structure that is user- and editor-friendly maintained by a small group of volunteers. With its 20th anniversary now behind it, it’s time to look at the resource and its governance and management. Does its current structure best serve the astro community? What changes would you like to see to its governance? We don’t know the answers to these and other questions! Please join us for an open discussion on the resource and what a new governance model for the ASCL might be.

ASCL research poster at ADASS XXIX

This presentation covers research on software authorship and citation, which we carried out between July and September 2019. We examined codes authored by three or fewer people (“short author list” codes) and codes authored by institutional teams, to determine how many codes in the ASCL can be attributed to one of these categories. Utilizing ADS data, we measured the number of citations per authorship category. We carried out further research to determine whether we could infer software usage and code usage statistics from the number of citations to code description papers. Our research shows that citations to code description papers are not a reliable proxy for software usage.

P. Wesley Ryan, Astrophysics Source Code Library

Download poster (PDF)

Understanding data: Visualisation, machine learning, and reproducibility

The ASCL has once again partnered with others on a Special Session at EWASS. This year’s Special Session (SS34) is titled Understanding data: Visualisation, machine learning, and reproducibility, and will be held on Tuesday, 25 June, in Room 3. Not at EWASS? Follow the session on Twitter at #ewass19ss34.

Full information, including abstracts for the presentations listed below, can be found in the detailed interactive program; look for the sessions in yellow and labeled SS34a, SS34b, and SS34c.

Tuesday, 25 June, 9:00 in Room 3, chaired by Rein Warmels
Reproducibility in computer-aided research by Konrad Hinsen
Publishing associated data: Challenges & opportunities by Pierre Ocvirk
FAIR data in astronomy by Mark Allen
Template for reproducible, shareable & achievable research by Mohammad Akhlaghi
These talks are followed by an open discussion moderated by David Valls-Gabaud.

Tuesday, 25 June, 14:30 in Room 3, chaired by Amruta Jaodand
High-performance machine learning in Astrophysics by Simon Portegies Zwart
Machine learning for the SKA by Anna Scaife
SuperNNova: Open-source, deep learning photometric time-series classifier by Anais Möller
Transfer learning for radio galaxy classification by Hongming Tang
Unsupervised classification of galaxy spectra and interpretability by Didier Fraix-burnet

Tuesday, 25 June, 16:30 in Room 3, chaired by John Wenskovitch
Visual Analytics of Data in Astronomy by Johanna Schmidt
Visual analytics algorithms for multidimensional astronomical data by Dany Vohl
Pulsar to Person (P2P): Data Visualization & Sonification to Experience the Universe by John Wenskovitch
Lightning talks for e-Posters
These talks are followed by an open discussion moderated by the session chair.

This Special Session was organized by:
Rachael Ainsworth (UManchester)
Mohammad Akhlaghi (Instituto De Astrofísica De Canarias)
Amruta Jaodand (ASTRON)
David Valls-Gabaud (Observatoire de Paris)
Rein Warmels (ESO)
John Wenskovitch (Virginia Tech)
Alice Allen (ASCL/UMD)

Open Digital Infrastructure in Astrophysics

I spent two days last week at the Open Digital Infrastructure in Astrophysics meeting at the Kavli Institute for Theoretical Physics (KITP) at UC Santa Barbara. This meeting featured presentations on open-knowledge digital infrastructure projects, the communities around them, their metrics for success, funding, diversity efforts, and plans for sustainability. Yeah, we’re talking code, a lot of code, and code projects, too, from AstroPy to yt, and data, and efforts that support openness and research transparency.

Open data presentations were given on:

STScI data, which includes JWST, Hubble, and PanSTARRS data, and the discovery and analysis software for these archives, by Arfon Smith
SDSS Data Infrastructure, by Joel Brownstein
LSST Transients data, by Federica Bianco
Open gravitational wave data and software tools for these data, by Duncan Brown

These software projects were represented at the meeting:

photograph of the Kavli Institute for Theoretical PhysicsAstropy, by Kelle Cruz
ATHENA++, by Jim Stone
Einstein Toolkit, by Philipp Mösta
emcee, by Daniel Foreman-Mackey
GYRE, by Rich Townsend
JETFIT, by Andrew Macfadyen
MESA Project, by Frank Timmes
TOM Toolkit and the AEON Network, by Rachel Street
yt, by Matt Turk

Other open digital resources presented were:

Journal of Open Source Software, by Arfon Smith
R astrostatistics, by Gwendolyn Eadie
Astrophysics Source Code Library, by yours truly

The meeting hashtag was #OpenAstroInfra, and many of the presentations were live tweeted. They were also video recorded and the podcasts are available on the KITP media page for the meeting, as are most of the slide decks. Participants of the co-located “Better Stars, Better Planets: Exploiting the Stellar-Exoplanetary Synergy” and “The New Era of Gravitational-Wave Physics and Astrophysics” programs were encouraged to attend, and we had a raven or two trying to have lunch with us as well.

Each of the presentations had about 15 minutes devoted to questions and discussion about the project highlighted. In two of these discussion sessions, the presenters were asked whether they were concerned about “improper use” of a code; sometimes people who are not well-schooled in the theory or science underlying a software package will use the code incorrectly, arriving at results that are dodgy, or downright wrong, and in a few cases (I know of only one), have then claimed the software is in error. This fear has been given as the reason some software authors do not release their code. I was cheering in my head with Jim Stone’s response to this question the first time it came up; he stated that there is so much benefit to making the code available that a potential improper use should not stop release. (YES!!!) He further went on to say, as did others in the room, that science will correct the record (YES!!!!!). I could not agree more with these replies, and it was great to hear these sentiments from others.

This was my first visit to KITP, and what a wonderful introduction to the institution it was! So many excellent projects, and so much exciting work being done in the open! My thanks to organizers Frank Timmes, Lars Bildsten, and Rich Townsend for inviting the ASCL to participate, and to the Sloan and Ford Foundations for funding the meeting.

ASCL presentation slides

Research Data Alliance Plenary 13 presentation

The ASCL is participating in the Research Data Alliance (RDA) meeting currently underway in Philadelphia, PA. The Plenary 13 meeting motto is “With Data Comes Responsibility.” Indeed! Among the sessions of special interest for software folks was yesterday’s Interest Group meeting on Software Source Code and today’s first meeting of a new Working Group on Software Source Code Identification. The Working Group is led by Roberto Di Cosmo, who is a founder of Software Heritage, Martin Fenner from DataCite, and Daniel Katz from the University of Illinois. This initial meeting is titled “Identifying, referencing and citing the source code of research software: a state of the art.” The ASCL is doing a short presentation that focuses on a few of our practices, how we do them, and the rationale for them; this includes what we do when we process a submission, what metadata for software we do and don’t have and why, and some of our curation practices. Our slides for this presentation are available below.

Photograph of Alice presenting a slide

Photo courtesy of @StephvandeSandt

Our attendance at this meeting was made possible with support from Software Heritage; our thanks to that organization!

Slides (PDF)