Papers › Jupyter-Enabled Astrophysical Analysis for Researchers and Students

Jupyter-Enabled Astrophysical Analysis for Researchers and Students

13 Apr 2021arXiv:2104.06527links table onlyarchive 2025-07-28

Stéphanie Juneau, Knut A. G. Olsen, Robert Nikutta, Alice Jacques, Stephen Bailey

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

The advent of increasingly large and complex datasets has fundamentally altered the way that scientists conduct astronomy research. The need to work closely to the data has motivated the creation of online science platforms, which include a suite of software tools and services, therefore going beyond data storage and data access. We present two example applications of Jupyter as a part of astrophysical science platforms for professional researchers and students. First, the Astro Data Lab is developed and operated by NOIRLab with a mission to serve the astronomy community with now over 1500 registered users. Second, the Dark Energy Spectroscopic Instrument science platform serves its geographically distributed team comprising about 900 collaborators from over 90 institutions. We describe the main uses of Jupyter and the interfaces that needed to be created to embed it within science platform ecosystems. We use these examples to illustrate the broader concept of empowering researchers and providing them with access to not only large datasets but also cutting-edge software, tools, and data services without requiring any local installation, which can be relevant for a wide range of disciplines. Future advances may involve science platform networks, and tools for simultaneously developing Jupyter notebooks to facilitate collaborations.

Code

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

14 samples harvested; 0 ran; 0 honoured the contract we drafted; 14 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

Licence: 0 of the 14 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from noaodatalab/notebooks-latest. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections