Key reproducibility enhancements — revision checklist

[temospena]

Archive raw data snapshots

• Deposit the exact GTFS ZIPs (Carris & Carris Metropolitana) and your OSM query output on Zenodo (or similar) and cite their DOIs.

Capture the software environment

• Include a renv.lock (or Packrat) file listing exact versions of R (v4.5) and all packages (GTFShift v0.7, tidytransit, stplanr, etc.).
• Optionally add a minimal Dockerfile or GitHub Actions workflow that installs these versions.

Provide session info and test outputs

• In a reproducibility appendix, show sessionInfo() and a small summary (e.g., head or summary) of your frequencies_segment_8 object so readers can verify correct replication.

Link to a reproducibility badge

• Integrate a CI badge (e.g., from GitHub Actions) showing your main pipeline passes on each commit.

Permanent code version

• Reference a Zenodo-archived snapshot of your GTFShift release, ensuring the exact code used in the paper never changes.

Minor

• In Findings, add:
  “All code, data snapshots, and environment descriptors required to reproduce these results are archived at DOI:10.xxxx/zenodo.xxxxxxx.”

• Include a brief Reproducibility Statement after Acknowledgements summarizing availability of code, data, and environment capture.

[gmatosferreira]

I just looked up and CI badge can be added using the following sintax:

[![Main Workflow Status](https://github.com/<username>/<repo>/actions/workflows/<workflow>.yml/badge.svg)](https://github.com/<username>/<repo>/actions/workflows/<workflow>.yml)

[temospena]

Reference a Zenodo-archived snapshot of your GTFShift release, ensuring the exact code used in the paper never changes.

Maybe we should do this anyway to refer to the release version used in the paper:
https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content#issuing-a-persistent-identifier-for-your-repository-with-zenodo

[temospena]

Reference a Zenodo-archived snapshot of your GTFShift release, ensuring the exact code used in the paper never changes.

Maybe we should do this anyway to refer to the release version used in the paper: https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content#issuing-a-persistent-identifier-for-your-repository-with-zenodo

I can do this after uploading the gtfs used and the results to the 0.8 version and setting it as the latest

[temospena]

To-Do to finish:

• DOI Zenodo
• ZIPs GTFS in releases
• Chek renv.lock again without unnecessary packages
• Convert 0.8 to latest
• CSV or results (maybe not necessary)
• Make a paper-code.R with full reproducibility even if takes 20min to run
• Re-run track changes with latexdiff
• Resubmit