Pith. sign in

REVIEW 3 major objections 5 minor 1 cited by

Provenance Tracking in Large-Scale Machine Learning Systems

T0 review · 3 major / 5 minor · reviewed 2026-08-06 · deepseek-v4-flash

Challenge this review Re-run · record.json Download PDF Read on arXiv ↗

Pith's one-line read The paper introduces yProv4ML, a provenance collection library for machine learning that records experiment lineage at a finer granularity than existing trackers, in W3C PROV-compliant JSON, and reports more than 90 percent smaller…

desk verdict A genuinely useful provenance library, but the headline compression claim rests on a single example and needs a real measurement protocol before it can be trusted. read the letter →

arxiv 2507.01075 v1 pith:Z6ZOFF6L submitted 2025-07-01 cs.LG cs.DC

Gabriele Padovani , Valentine Anantharaj , Sandro Fiore This is my paper
classification cs.LGcs.DC
keywords provenancemachinelearningPROV-JSONW3CPROVexperimenttrackingenergyefficiencyZarrNetCDF
verification ladder T0 review T1 audit T2 compute T3 formal

The pith

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

The reading

yProv4ML is a provenance library for machine learning that tries to make detailed lineage tracking cheap enough to use in large-scale training. The paper argues that existing tools such as MLflow and Weights and Biases log too coarse a record, and that yProv4ML captures per-epoch, per-context information — artifacts, parameters, metrics, and input/output relationships — in a W3C PROV-compliant form without becoming a performance bottleneck. The central efficiency claim is that moving bulky time-series metrics out of the main PROV-JSON file into Zarr or NetCDF companion files cuts the total provenance footprint by more than 90 percent, based on a measured comparison reported in Table 1. A scaling study of the MODIS-FM foundation model on a leadership-class HPC system is offered as evidence that this provenance can then be used to weigh energy consumption against model loss when choosing model size and GPU count. If the library works as described, reproducible and energy-aware ML development would not require a separate heavyweight provenance infrastructure.

What carries the argument

The central object is the yProv4ML data model, built around an Experiment that contains multiple Run Executions and subdivides each run into contexts and epochs. Its defining mechanism is the separation of concerns between a small, process-describing PROV-JSON file and companion Zarr or NetCDF files for bulky metrics. The library's logging API mirrors MLflow's, so the additional lineage comes from tracking each logged value as an artifact, parameter, or metric and marking it as an input or output, then recording the W3C PROV relationships 'used' and 'wasGeneratedBy'.

What would settle it

Run one standard training workload (for example, a vision model on ImageNet) for a fixed number of steps and log identical metrics three ways — JSON-only, Zarr, and NetCDF — across at least fifty runs with varying numbers of logged epochs and metric frequencies. If the median total file-size reduction is far below 90 percent, or if the main PROV-JSON file remains large because textual parameters and artifact links dominate, the paper's headline efficiency claim fails.

Watch

Extended reading notes

Core claim

The paper presents yProv4ML as a provenance-producing library for machine learning. Its central claim is that the library captures lineage at a finer grain than MLflow and Weights and Biases by structuring each experiment into run executions, contexts (training, validation, testing, or user-defined), and epochs, and by logging artifacts, parameters, and metrics with explicit input/output relationships. The output is a W3C PROV-compliant PROV-JSON file, optionally paired with RO-Crate packaging, and the latest version adds the ability to store time-series and bulky metrics in separate Zarr or NetCDF files so the top-level provenance file stays small. On that point the paper reports a measured total provenance size of 39.82 MB in JSON versus 2.74 MB in Zarr and 2.35 MB in NetCDF for one comparison, a reduction above 90 percent. The paper then uses a MODIS-FM foundation-model scaling study run on a leadership-class supercomputer to argue that this granular provenance makes it possible to compare model configurations by GPU-energy consumption times loss, finding the SwinT-V2 architecture preferable at scale.

Load-bearing premise

The assumption that a typical training run's provenance record is dominated by bulky numeric time series is the load-bearing premise; if textual metadata dominates, the 90 percent reduction will not materialize.

Editorial extensions

If this is right

  • If the 90 percent size reduction holds across typical runs, provenance capture ceases to be a storage bottleneck and can be left on by default in large-scale training.
  • With per-epoch, per-context lineage in a standard format, experiments can be compared run-to-run and across teams without converting between proprietary tracking formats.
  • The MODIS-FM scaling study indicates that fine-grained provenance can reveal energy-versus-loss trade-offs per model size and GPU count, which is exactly the information needed to budget node-hours.
  • Because the main PROV-JSON file stays small and self-describing, sharing a single file plus its artifact wrapper (RO-Crate) becomes a plausible path to out-of-the-box reproducibility of a training run.
  • If provenance histories accumulate, forecasting the effect of a hyperparameter or model-size change could be done from past runs rather than from fresh training.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

  • The reported file-size comparison is one example; a broader benchmark across model families and metric cadences would tell whether the 90 percent figure is typical or an outlier.
  • The same companion-file mechanism could be extended to store weight snapshots or optimizer states in chunked formats, not just metrics, making the provenance record itself a distributed checkpoint catalog.
  • The empty cells in the scaling grid suggest that experiments exceeding a walltime limit are silently lost; an online provenance system that records partial runs could make such studies more complete without additional compute.
  • If provenance standards were unified across ML frameworks, the historical runs needed for scaling-law forecasting would be much easier to assemble, but that depends on ecosystem adoption, which the paper does not itself address.
Share X Bluesky LinkedIn Reddit HN

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Referee Report

3 major / 5 minor

Summary. The paper presents yProv4ML, an open-source provenance collection library for machine learning workflows, integrated with the yProv framework and compliant with W3C PROV and ProvML standards. The library logs parameters, metrics, and artifacts, supports user-defined contexts, and can store bulky time-series metrics in Zarr or NetCDF to keep the main PROV-JSON file small. The authors report a file-size reduction of more than 90% for a single representative file (Table 1) and illustrate the tool on a MODIS-FM scaling study on Frontier, where GPU energy consumption and loss are used to identify trade-offs between model size and compute configuration (Figure 3). The paper also describes planned reproducibility features, including git tracking and RO-Crate packaging.

Significance. If the reported benefits are substantiated, yProv4ML would be a useful contribution to ML provenance practice: it provides a standards-based, extensible logging interface with finer-grained lineage than typical experiment trackers, and the Frontier use case demonstrates real-world deployment on a leadership-class supercomputer. The paper's strengths include the public availability of the library, its integration with the yProv ecosystem and workflow tools, and its concrete energy-versus-performance illustration. However, the current evaluation is preliminary: the headline size-reduction figure rests on one measurement, and the scaling-study conclusions are drawn from an incomplete run grid without statistical support.

major comments (3)
  1. [Section 4, Table 1] The claim that storing bulky metrics in Zarr or NetCDF yields 'gains of more than 90% on average' is supported by a single file comparison (39.82 MB JSON vs 2.74 MB Zarr and 2.35 MB NetCDF). The paper does not report the metric types, numeric precision, logging frequency, or the fraction of the original JSON that is textual overhead, so the reader cannot judge whether the reduction is representative or partly an artifact of switching from high-precision decimal strings to binary float32. The compressed-size column shows a much smaller benefit (8.65 MB vs 2.14-2.30 MB, about 75%), so the >90% figure applies only to uncompressed storage. Because file-size reduction is one of the two central advertised benefits, this claim needs to be supported by multiple runs, with protocol details and an analysis of variability.
  2. [Section 5, Figure 3] The conclusion that 'the best trade-off between energy consumption and performance is obtained' and that MAE 'presents a steeper trade-off curve' is drawn from Figure 3, in which several configurations are empty because they exceeded the 2-hour walltime. With no statistical analysis, no error bars, and no statement of how the missing cells were treated, the qualitative ranking of architectures and configurations is not yet established. The authors should either restrict the claims to the completed cells, provide a sensitivity analysis, or add error estimates from repeated runs.
  3. [Section 4] The paper states that the core idea of the library is to log more lineage information compared to MLFlow or Weights and Biases, but it does not provide a concrete comparison of the lineage captured by these tools. A feature-by-feature table or a small benchmark showing the additional lineage elements (e.g., contexts, epochs, input/output relationships) would substantiate this central design goal and make the contribution easier to evaluate.
minor comments (5)
  1. [Abstract and Introduction] There are several typographical errors, including 'shear amount' (should be 'sheer amount'), 'conjuction' (should be 'conjunction'), and 'are have already been shown' (grammar).
  2. [Section 2] In the Related Work section, 'moltitude' should be 'multitude'.
  3. [Figure 3] The color scale units ('1e6') and the empty cells should be explained in the caption; also consider labeling axes more clearly and using a perceptually uniform colormap.
  4. [Table 1] The caption says the measurements include both the PROV-JSON and the additional metric files, but the row names 'Original_file.json', 'Converted_to.zarr', and 'Converted_to.nc' could be clearer about what is being compared, namely a single JSON file versus a split PROV-JSON plus binary metric store.
  5. [Section 6] In the conclusions, 'tracking all experiment runs in a single provenance files' has a plural/singular mismatch; 'files' should be 'file'.

Circularity Check

0 steps flagged · score 0.0 of 10

No significant circularity: the paper's claims are architectural descriptions and external measurements, not predictions forced by fitted inputs or self-referential definitions.

full rationale

The paper introduces yProv4ML as a software library and supports its claims with direct descriptions of the data model, code-level logging utilities, and measured file-size comparisons. The central quantitative claim—that storing bulky metrics in Zarr/NetCDF avoids JSON text overhead and yields more than 90% size reduction on average (Section 4, Table 1)—is an external measurement of the tool's output, not a derived quantity whose value is encoded in an assumption or fitted parameter. The use-case energy/performance trade-off (Section 5, Figure 3) is likewise an empirical scaling-study observation with incomplete grid cells, which is an evidentiary weakness, not a circularity. The paper cites the authors' own prior work on the yProv framework and ecosystem ([11], [12], [32]) and states that earlier use cases were shown there, but those citations are contextual; the present functionality claims (PROV-JSON generation, plugin integration, RO-Crate wrapping, input/output relationship rework) are presented as implemented features, and no load-bearing conclusion depends on a theorem or uniqueness claim imported from those citations. Because there is no predictive chain that reduces to its inputs, no circular step can be exhibited under the required standard.

Assumptions & free parameters 0 free parameters · 0 assumptions · 0 invented entities

The paper is a software tool description; it introduces no free parameters, no new mathematical axioms, and no invented entities. The only input is the design choice of using W3C PROV as the provenance model and the library's own configuration, which are not formal assumptions in the sense of a derivation.

how reviews work

0 comments
Cite this review

Pith. "Pith review of Provenance Tracking in Large-Scale Machine Learning Systems." pith.science (2026). https://pith.science/paper/Z6ZOFF6L

@misc{pith2026250701075,
  author       = {Pith},
  title        = {Pith review of: Provenance Tracking in Large-Scale Machine Learning Systems},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/Z6ZOFF6L}},
  note         = {Machine review of arXiv:2507.01075}
}
read the original abstract

As the demand for large scale AI models continues to grow, the optimization of their training to balance computational efficiency, execution time, accuracy and energy consumption represents a critical multidimensional challenge. Achieving this balance requires not only innovative algorithmic techniques and hardware architectures but also comprehensive tools for monitoring, analyzing, and understanding the underlying processes involved in model training and deployment. Provenance data information about the origins, context, and transformations of data and processes has become a key component in this pursuit. By leveraging provenance, researchers and engineers can gain insights into resource usage patterns, identify inefficiencies, and ensure reproducibility and accountability in AI development workflows. For this reason, the question of how distributed resources can be optimally utilized to scale large AI models in an energy efficient manner is a fundamental one. To support this effort, we introduce the yProv4ML library, a tool designed to collect provenance data in JSON format, compliant with the W3C PROV and ProvML standards. yProv4ML focuses on flexibility and extensibility, and enables users to integrate additional data collection tools via plugins. The library is fully integrated with the yProv framework, allowing for higher level pairing in tasks run also through workflow management systems.

Figures

Figures reproduced from arXiv: 2507.01075 by the authors.

Figure 1
Figure 1. Example of provenance file created using the latest version of yProv4ML, it showcases the use of multiple contexts, [PITH_FULL_IMAGE:figures/full_fig_p002_1.png] view at source ↗
Figure 2
Figure 2. Data Model used as foundation for yProv4ML, blue [PITH_FULL_IMAGE:figures/full_fig_p005_2.png] view at source ↗
Figure 3
Figure 3. Energy and performance trade-off, calculated as the loss times the total energy consumption, for MAE (top) and SwinT [PITH_FULL_IMAGE:figures/full_fig_p007_3.png] view at source ↗

Discussion (0). Sign in to comment.

Forward citations

Cited by 1 Pith paper

Reviewed papers in the Pith corpus that reference this work. Sorted by Pith novelty score. Full citation record

  1. AuditWeave: A Tamper-Evident, Auditor-Navigable Evidence Layer for AI-Assisted and Data-Transformation Workflows

    cs.LG 2026-06 conditional novelty 4.0 of 10

    A no-dependency Python library records RAG and tabular workflow steps in one hash-chained ledger, enabling end-to-end evidence navigation and detectable tampering at tens of microseconds per event.

Reference graph

Works this paper leans on

44 extracted references · 34 canonical work pages · cited by 1 Pith paper

  1. [1]

    Pushing the frontiers in climate modelling and analysis with machine learning

    Veronika Eyring, William D Collins, Pierre Gentine, Elizabeth A Barnes, Marcelo Barreiro, Tom Beucler, Marc Bocquet, Christopher S Bretherton, Hannah M Christensen, Katherine Dagon, et al. Pushing the frontiers in climate modelling and analysis with machine learning. Nature Climate Change, pages 1–13, 2024

    work page 2024

  2. [2]

    Machine Learning for the Physics of Climate

    Annalisa Bracco, Julien Brajard, Henk A Dijkstra, Pedram Hassanzadeh, Christian Lessig, and Claire Monteleoni. Machine learning for the physics of climate.arXiv preprint arXiv:2408.09627, 2024

    work page Pith review arXiv 2024

  3. [3]

    Tackling climate change with machine learning

    David Rolnick, Priya L Donti, Lynn H Kaack, Kelly Kochanski, Alexandre Lacoste, Kris Sankaran, Andrew Slavin Ross, Nikola Milojevic-Dupont, Natasha Jaques, Anna Waldman-Brown, et al. Tackling climate change with machine learning. ACM Computing Surveys (CSUR), 55(2):1–96, 2022

    work page 2022

  4. [4]

    Provenance: a future history

    James Cheney, Stephen Chong, Nate Foster, Margo Seltzer, and Stijn Vansum- meren. Provenance: a future history. In Proceedings of the 24th ACM SIGPLAN conference companion on Object oriented programming systems languages and applications, pages 957–964, 2009

    work page 2009

  5. [5]

    Advances, challenges and opportunities in creating data for trustworthy ai

    Weixin Liang, Girmaw Abebe Tadesse, Daniel Ho, Li Fei-Fei, Matei Zaharia, Ce Zhang, and James Zou. Advances, challenges and opportunities in creating data for trustworthy ai. Nature Machine Intelligence, 4(8):669–677, 2022

    work page 2022

  6. [6]

    What information is required for explainable ai?: A provenance-based research agenda and future challenges

    Fariha Tasmin Jaigirdar, Carsten Rudolph, Gillian Oliver, David Watts, and Chris Bain. What information is required for explainable ai?: A provenance-based research agenda and future challenges. In 2020 IEEE 6th International Conference on Collaboration and Internet Computing (CIC) , pages 177–183. IEEE, 2020

    work page 2020

  7. [7]

    Leakage and the reproducibility crisis in ml-based science

    Sayash Kapoor and Arvind Narayanan. Leakage and the reproducibility crisis in ml-based science. arXiv preprint arXiv:2207.07048, 2022

    arXiv 2022

  8. [8]

    Komadu: A capture and visual- ization system for scientific data provenance

    Isuru Suriarachchi, Quan Zhou, and Beth Plale. Komadu: A capture and visual- ization system for scientific data provenance. Journal of Open Research Software , 3(1):e4–e4, 2015

    work page 2015

Show all 44 references
  1. [9]

    Accelerating the machine learning lifecycle with mlflow

    Matei Zaharia, Andrew Chen, Aaron Davidson, Ali Ghodsi, Sue Ann Hong, Andy Konwinski, Siddharth Murching, Tomas Nykodym, Paul Ogilvie, Mani Parkhe, et al. Accelerating the machine learning lifecycle with mlflow. IEEE Data Eng. Bull., 41(4):39–45, 2018

    2018

  2. [10]

    The prov-json serialization

    Trung Dong Huynh, Michael O Jewell, Amir Sezavar Keshavarz, Danius T Michaelides, Huanjia Yang, and Luc Moreau. The prov-json serialization. 2013

    2013

  3. [11]

    Enabling provenance tracking in workflow management systems

    Ludovica Sacco, Carolina Sopranzetti, and Sandro Fiore. Enabling provenance tracking in workflow management systems. In2024 IEEE International Conference on Big Data (BigData) , pages 4402–4409. IEEE, 2024

    2024

  4. [12]

    A software ecosystem for multi-level provenance management in large-scale scientific workflows for ai applications

    Gabriele Padovani, Valentine Anantharaj, Ludovica Sacco, Takuya Kurihana, Matteo Bunino, Kalliopi Tsolaki, Maria Girone, Fabrizio Antonio, Carolina So- pranzetti, Massimiliano Fronza, et al. A software ecosystem for multi-level provenance management in large-scale scientific w...

    2024

  5. [13]

    The w3c prov family of specifications for modelling provenance metadata

    Paolo Missier, Khalid Belhajjame, and James Cheney. The w3c prov family of specifications for modelling provenance metadata. In Proceedings of the 16th International Conference on Extending Database Technology , pages 773–776, 2013

    2013

  6. [14]

    Prov-dm: The prov data model

    Khalid Belhajjame, Reza B’Far, James Cheney, Sam Coppens, Stephen Cresswell, Yolanda Gil, Paul Groth, Graham Klyne, Timothy Lebo, Jim McCusker, et al. Prov-dm: The prov data model. W3C Recommendation, 14:15–16, 2013

    2013

  7. [15]

    Prov-n: The provenance notation

    Luc Moreau, Paolo Missier, James Cheney, and Stian Soiland-Reyes. Prov-n: The provenance notation. 2013

    2013

  8. [16]

    Provenance data in the machine learning lifecycle in computational science and engineering

    Renan Souza, Leonardo Azevedo, Vítor Lourenço, Elton Soares, Raphael Thiago, Rafael Brandão, Daniel Civitarese, Emilio Brazil, Marcio Moreno, Patrick Val- duriez, et al. Provenance data in the machine learning lifecycle in computational science and engineering. In 2019 IEEE/AC...

    2019

  9. [17]

    Efficient runtime capture of multiworkflow data using provenance

    Renan Souza, Leonardo Azevedo, Raphael Thiago, Elton Soares, Marcelo Nery, Marco AS Netto, Emilio Vital, Renato Cerqueira, Patrick Valduriez, and Marta Mattoso. Efficient runtime capture of multiworkflow data using provenance. In 2019 15th International Conference on eScience ...

    2019

  10. [18]

    Ml- schema: exposing the semantics of machine learning with schemas and ontolo- gies

    Gustavo Correa Publio, Diego Esteves, Agnieszka Ławrynowicz, Panče Panov, Larisa Soldatova, Tommaso Soru, Joaquin Vanschoren, and Hamid Zafar. Ml- schema: exposing the semantics of machine learning with schemas and ontolo- gies. arXiv preprint arXiv:1807.05351, 2018

    2018 arXiv

  11. [19]

    Workflow provenance in the lifecycle of scientific machine learning

    Renan Souza, Leonardo G Azevedo, Vítor Lourenço, Elton Soares, Raphael Thiago, Rafael Brandão, Daniel Civitarese, Emilio Vital Brazil, Marcio Moreno, Patrick Valduriez, et al. Workflow provenance in the lifecycle of scientific machine learning. Concurrency and Computation: Pra...

    2022

  12. [20]

    Mlflow2prov: extracting provenance from machine learning experiments

    Marius Schlegel and Kai-Uwe Sattler. Mlflow2prov: extracting provenance from machine learning experiments. In Proceedings of the Seventh Workshop on Data Management for End-to-End Machine Learning , pages 1–4, 2023

    2023

  13. [21]

    Harris, Frederick C., Chenhao Li, Jiyin Zhang, and Xiaogang Ma

    Amruta Kale, Tin Nguyen, Jr. Harris, Frederick C., Chenhao Li, Jiyin Zhang, and Xiaogang Ma. Provenance documentation to enable explainable and trustworthy AI: A literature review. Data Intelligence, 5(1):139–162, 03 2023

    2023

  14. [22]

    Interoperability for provenance-aware databases using {PROV} and {JSON}

    Xing Niu, Boris Glavic, Dieter Gawlick, Zhen Hua Liu, Vasudha Krishnaswamy, and Venkatesh Radhakrishnan. Interoperability for provenance-aware databases using {PROV} and {JSON}. In 7th USENIX Workshop on the Theory and Practice of Provenance (TaPP 15), 2015

    2015

  15. [23]

    Provenance supporting hyperparameter analysis in deep neural networks

    Débora Pina, Liliane Kunstmann, Daniel de Oliveira, Patrick Valduriez, and Marta Mattoso. Provenance supporting hyperparameter analysis in deep neural networks. In International Provenance and Annotation Workshop, pages 20–38. Springer, 2020

    2020

  16. [24]

    Data provenance based system for classification and linear regression in distributed machine learning

    Muhammad Jahanzeb Khan, Ruoyu Wang, Daniel Sun, and Guoqiang Li. Data provenance based system for classification and linear regression in distributed machine learning. In International Workshop on Structured Object-Oriented Formal Language and Method, pages 279–295. Springer, 2019

    2019

  17. [25]

    Lima: Fine-grained lin- eage tracing and reuse in machine learning systems

    Arnab Phani, Benjamin Rath, and Matthias Boehm. Lima: Fine-grained lin- eage tracing and reuse in machine learning systems. In Proceedings of the 2021 International Conference on Management of Data , pages 1426–1439, 2021

    2021

  18. [26]

    Au- ditmai: Towards an infrastructure for continuous ai auditing

    Laura Waltersdorfer, Fajar J Ekaputra, Tomasz Miksa, and Marta Sabou. Au- ditmai: Towards an infrastructure for continuous ai auditing. arXiv preprint arXiv:2406.14243, 2024

    2024 arXiv

  19. [27]

    Recording provenance of workflow runs with ro-crate

    Simone Leo, Michael R Crusoe, Laura Rodríguez-Navas, Raül Sirvent, Alexander Kanitz, Paul De Geest, Rudolf Wittner, Luca Pireddu, Daniel Garijo, José M Fernández, et al. Recording provenance of workflow runs with ro-crate. PLoS one, 19(9):e0309210, 2024

    2024

  20. [28]

    Packaging research artefacts with ro-crate

    Stian Soiland-Reyes, Peter Sefton, Mercè Crosas, Leyla Jael Castro, Frederik Cop- pens, José M Fernández, Daniel Garijo, Björn Grüning, Marco La Rosa, Simone Leo, et al. Packaging research artefacts with ro-crate. Data Science, 5(2):97–138, 2022

    2022

  21. [29]

    Towards lightweight data integration using multi- workflow provenance and data observability

    Renan Souza, Tyler J Skluzacek, Sean R Wilkinson, Maxim Ziatdinov, and Rafael Ferreira Da Silva. Towards lightweight data integration using multi- workflow provenance and data observability. In 2023 IEEE 19th International Conference on e-Science (e-Science) , pages 1–10. IEEE, 2023

    2023

  22. [30]

    Work- flow provenance in the computing continuum for responsible, trustworthy, and energy-efficient ai

    Renan Souza, Silvina Caino-Lores, Mark Coletti, Tyler J Skluzacek, Alexandru Costan, Frédéric Suter, Marta Mattoso, and Rafael Ferreira Da Silva. Work- flow provenance in the computing continuum for responsible, trustworthy, and energy-efficient ai. In 2024 IEEE 20th Internati...

    2024

  23. [31]

    Experiment tracking with weights and biases, 2020

    Lukas Biewald. Experiment tracking with weights and biases, 2020. Software available from wandb.com

    2020

  24. [32]

    A graph data model-based micro-provenance approach for multi-level provenance exploration in end-to-end climate workflows

    Sandro Fiore, Mattia Rampazzo, Donatello Elia, Ludovica Sacco, Fabrizio Antonio, and Paola Nassisi. A graph data model-based micro-provenance approach for multi-level provenance exploration in end-to-end climate workflows. In 2023 IEEE International Conference on Big Data (Big...

    2023

  25. [33]

    Evalua- tion of pre-training large language models on leadership-class supercomputers

    Junqi Yin, Sajal Dash, John Gounley, Feiyi Wang, and Georgia Tourassi. Evalua- tion of pre-training large language models on leadership-class supercomputers. The Journal of Supercomputing , 79(18):20747–20768, 2023

    2023

  26. [34]

    Brown, Benjamin Chess, Rewon Child, Scott Gray, Alec Radford, Jeffrey Wu, and Dario Amodei

    Jared Kaplan, Sam McCandlish, Tom Henighan, Tom B. Brown, Benjamin Chess, Rewon Child, Scott Gray, Alec Radford, Jeffrey Wu, and Dario Amodei. Scaling laws for neural language models, 2020

    2020

  27. [35]

    Rae, Oriol Vinyals, and Laurent Sifre

    Jordan Hoffmann, Sebastian Borgeaud, Arthur Mensch, Elena Buchatskaya, Trevor Cai, Eliza Rutherford, Diego de Las Casas, Lisa Anne Hendricks, Johannes Welbl, Aidan Clark, Tom Hennigan, Eric Noland, Katie Millican, George van den Driessche, Bogdan Damoc, Aurelia Guy, Simon Osin...

    2022

  28. [36]

    Rush, Boaz Barak, Teven Le Scao, Aleksandra Piktus, Nouamane Tazi, Sampo Pyysalo, Thomas Wolf, and Colin Raffel

    Niklas Muennighoff, Alexander M. Rush, Boaz Barak, Teven Le Scao, Aleksandra Piktus, Nouamane Tazi, Sampo Pyysalo, Thomas Wolf, and Colin Raffel. Scaling data-constrained language models, 2023

    2023

  29. [37]

    Netcdf user’s guide, 1993

    Russ Rew, Glenn Davis, Steve Emmerson, Harvey Davies, and Ed Hartnett. Netcdf user’s guide, 1993

    1993

  30. [38]

    https://zarr.dev/

    Zarr developers. https://zarr.dev/

  31. [39]

    Trustworthy provenance for big data science: a modular architecture leveraging blockchain in federated settings

    Nicola Giuseppe Marchioro, Yannis Velegrakis, Valentine Anantharaj, Ian Fos- ter, and Sandro Luigi Fiore. Trustworthy provenance for big data science: a modular architecture leveraging blockchain in federated settings. arXiv preprint arXiv:2505.24675, 2025

    2025 arXiv

  32. [40]

    An image is worth 16x16 words: Transformers for image recognition at scale

    Dosovitskiy Alexey. An image is worth 16x16 words: Transformers for image recognition at scale. arXiv preprint arXiv: 2010.11929 , 2020

    2010 arXiv

  33. [41]

    The modis cloud optical and microphysical products: Collec- tion 6 updates and examples from terra and aqua.IEEE Transactions on Geoscience and Remote Sensing, 55(1):502–525, 2016

    Steven Platnick, Kerry G Meyer, Michael D King, Galina Wind, Nandana Ama- rasinghe, Benjamin Marchant, G Thomas Arnold, Zhibo Zhang, Paul A Hubanks, Robert E Holz, et al. The modis cloud optical and microphysical products: Collec- tion 6 updates and examples from terra and aqu...

    2016

  34. [42]

    Swin transformer v2: Scaling up capacity and resolution

    Ze Liu, Han Hu, Yutong Lin, Zhuliang Yao, Zhenda Xie, Yixuan Wei, Jia Ning, Yue Cao, Zheng Zhang, Li Dong, et al. Swin transformer v2: Scaling up capacity and resolution. In Proceedings of the IEEE/CVF conference on computer vision and pattern recognition, pages 12009–12019, 2022

    2022

  35. [43]

    Masked autoencoders are scalable vision learners

    Kaiming He, Xinlei Chen, Saining Xie, Yanghao Li, Piotr Dollár, and Ross Girshick. Masked autoencoders are scalable vision learners. In Proceedings of the IEEE/CVF conference on computer vision and pattern recognition , pages 16000–16009, 2022

    2022

  36. [44]

    Pytorch distributed: Experiences on accelerating data parallel training

    Shen Li, Yanli Zhao, Rohan Varma, Omkar Salpekar, Pieter Noordhuis, Teng Li, Adam Paszke, Jeff Smith, Brian Vaughan, Pritam Damania, et al. Pytorch distributed: Experiences on accelerating data parallel training. arXiv preprint arXiv:2006.15704, 2020

    2006 arXiv

Pith tools

Reviewed August 6, 2026 · model on record in the stance chip above.