pith. sign in

arxiv: 2605.20714 · v1 · pith:PJLXQM6Cnew · submitted 2026-05-20 · 🌌 astro-ph.IM

Data Formats and Visualisation BoF

Pith reviewed 2026-05-21 02:21 UTC · model grok-4.3

classification 🌌 astro-ph.IM
keywords data formatsFITSvisualizationastronomy softwareinteroperabilityADASSBoF
0
0 comments X

The pith

Multiple data formats make general-purpose astronomy visualization programs harder to write, yet why agreement is elusive became clearer at this BoF.

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The paper recounts a Birds of a Feather session at ADASS on astronomical data formats and visualization. It notes the shift from FITS-focused talks to acceptance that several formats will coexist for the near term. Participants asked whether this variety creates real obstacles for shared tools such as SAOImage/DS9. The conversation produced no final verdict, but it exposed the practical reasons why settling the question proves difficult.

Core claim

The BoF discussion clarified why reaching a conclusion on the difficulties posed by multiple data formats for general-purpose utilities such as visualization programs is hard.

What carries the argument

The open discussion among attendees on whether format diversity hinders development of versatile utilities like visualization software.

If this is right

  • Visualization programs must continue to handle several data formats at once.
  • General utilities face repeated interoperability challenges across the community.
  • Attempts to impose a single replacement format have been set aside in favor of managing diversity.
  • The variety of use cases and legacy data makes uniform solutions unlikely in the short term.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • Conversion libraries that work across common formats could reduce the load on individual tool authors.
  • Ongoing format discussions may gradually produce de-facto standards for specific data types.
  • Developers of new instruments might weigh visualization needs earlier when choosing output formats.

Load-bearing premise

Astronomy will have to work with multiple data formats in the foreseeable future.

What would settle it

A survey of visualization tool maintainers measuring the extra effort required to support each additional format would show whether multiplicity creates measurable problems.

read the original abstract

ADASS used to hold a regular FITS BoF (Birds of a Feather meeting). As other data formats started to be used along with FITS, this became a Data Formats BoF, and there was some element of competition between formats, together with an occasional attempt to create a unified Format that could replace FITS as the only astronomical format needed. The impetus for this year's BoF came from an acceptance that astronomy would have to work with multiple formats in the foreseeable future, and a question: Did the use of multiple formats make it difficult to write general-purpose utilities, for example visualisation programs such as SAOImage/DS9, and if so was this a problem? The resulting discussion was interesting, and although it came to no ultimate conclusion, it at least made it clearer why such a conclusion was hard to reach.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

0 major / 2 minor

Summary. The manuscript summarizes a Birds of a Feather (BoF) session at ADASS on astronomical data formats. It describes the historical shift from a FITS-focused BoF to a broader Data Formats BoF amid the adoption of multiple formats, notes the premise that astronomy will continue using several formats, and reports that the discussion on whether multiple formats complicate general-purpose tools (e.g., visualization programs such as SAOImage/DS9) yielded no final conclusion but clarified the reasons such a conclusion is difficult to reach.

Significance. If the account accurately reflects the session, the report contributes a concise record of community dialogue on data-format interoperability, a recurring practical issue for software tools in astronomy. Such summaries can help track evolving attitudes toward standardization versus pluralism and may inform developers of visualization and analysis utilities.

minor comments (2)
  1. The manuscript is extremely concise; expanding the summary with one or two concrete examples of points raised during the discussion would strengthen the claim that the session clarified why conclusions are hard to reach, without altering its character as a BoF report.
  2. The title 'Data Formats and Visualisation BoF' is terse; a subtitle such as 'Summary of the ADASS 202X Birds of a Feather Session' would improve discoverability.

Simulated Author's Rebuttal

0 responses · 0 unresolved

We thank the referee for their positive summary of the manuscript and their recommendation to accept. The report accurately captures the content and intent of our account of the ADASS Data Formats BoF session.

Circularity Check

0 steps flagged

No significant circularity; qualitative meeting summary

full rationale

This paper is a short report summarizing a Birds of a Feather discussion at ADASS on astronomical data formats and visualization challenges. It contains no equations, derivations, fitted parameters, predictions, or self-citations that could form a load-bearing chain. The central observation—that the session made clearer why reaching a conclusion on multiple-format difficulties is hard—is a qualitative note on meeting dynamics with no technical content that reduces to its own inputs by construction. The paper is self-contained as a discussion summary and requires no verification against internal reductions.

Axiom & Free-Parameter Ledger

0 free parameters · 0 axioms · 0 invented entities

No free parameters, axioms, or invented entities are introduced; the document is a descriptive meeting report with no technical derivations.

pith-pipeline@v0.9.0 · 5657 in / 909 out tokens · 27089 ms · 2026-05-21T02:21:06.483157+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Reference graph

Works this paper leans on

3 extracted references · 3 canonical work pages

  1. [1]

    2026, in ADASS XXXV , edited by TBD (San Francisco: ASP), vol

    Barloy, N., & Landais, G. 2026, in ADASS XXXV , edited by TBD (San Francisco: ASP), vol. TBD of ASP Conf. Ser., TBD

  2. [2]

    2020, in ADASS XXIX, edited by R

    Mink, J., Diaz, R., Fernique, P., Landais, G., Mireille, L., & Michel, L. 2020, in ADASS XXIX, edited by R. Pizzo, E. R. Deul, J. D. Mol, J. de Plaa, & H. Verkouter, vol. 527 of ASP Conf. Ser., 761

  3. [3]

    2019, in ADASS XXVII, edited by P

    Mink, J., Diaz, R., Shortridge, K., & Jenness, T. 2019, in ADASS XXVII, edited by P. J. Teuben, M. W. Pound, B. A. Thomas, & E. M. Warner, vol. 523 of ASP Conf. Ser., 701