Skip to content

Use YYYY-MM-DD for downloaded orbit file dates - #34

Merged
wilsonbb merged 1 commit into
mainfrom
fix-date-format-18
Sep 28, 2026
Merged

wilsonbb merged 1 commit into
mainfrom
fix-date-format-18

Conversation

@wilsonbb

Copy link
Copy Markdown
Contributor

Closes #18.

--download_orbits wrote files named with %d-%m-%Y (e.g. asteroid_orbits_23-09-2026.json.gz), which don't sort chronologically. This switches them to %Y-%m-%d.

Results files (results/<date>_job_<job>.* and results/chunk_runs/<date>_job_...) already use YYYY-MM-DD because they come from datetime.isoformat(), so this was the last date in DD-MM-YYYY form. chunk_cleanup.RUN_DIR_RE already expects the ISO form.

Nothing looks up orbit files by date, so there's no compatibility shim. Existing downloaded files keep their old names.

Testing

  • test_download_orbits_without_db_skips_analysis now checks that the date string is YYYY-MM-DD
  • pytest tests: 39 passed

🤖 Generated with Claude Code

The --download_orbits path named files like asteroid_orbits_23-09-2026.json.gz,
which does not sort chronologically. Switch to ISO dates to match the
results/<YYYY-MM-DD>_job_<job> naming.

Closes #18

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@codecov

codecov Bot commented Sep 23, 2026

Copy link
Copy Markdown

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

@wilsonbb
wilsonbb merged commit e43e541 into main Sep 28, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix output date formats to YYYYMMDD or YYYY-MM-DD

2 participants