Repository navigation
Conversation
Captures the DR1 update as a repeatable workflow: release-dependent spots in each notebook, settled decisions and gotchas, a release-availability check script, and a parameterized Source Discovery Tool test harness. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
run_sdt_release_test.py gains --sia-host to run the notebook's own SIA cells against irsadev; decisions.md notes how to test SIA notebooks there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
TAP's ivoa.obscore leaves cloud_access blank even where SIA fills it (production QR3 included), so the script reported a false blank. Ask SIA, as the notebooks do, at the position of one of the release's own images. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The old test ran selected cells and stood in a 2MASS star for secs. 9-11, which hid sec. 6 picking a D5 image instead of D4 on DR1. The script now executes every cell on a copy against the pre-release host (SIA, IBE in place of S3, that host's Firefly viewer) and prints a summary of what to check. Also record the DR1 gotchas: detector selection by name, the hard-coded selected_ids source, Firefly and MOST on pre-release hosts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jkrick
added
infrastructure
Contributor
Author
|
@DeekshaMohanty as you are doing the final release, it would be super helpful if you (or your AI) could update this skill with any last minute items that are good to document about this workflow, that would help make this smoother for the next go around. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
.claude/skills/spherex-data-release/, a Claude Code project skill that captures how the SPHEREx tutorials were updated for DR1 (#392, PR #401), so the next release (DR2, a new Quick Release, a reprocessing) can follow the same steps instead of rediscovering them.What's in it
SKILL.md: the workflow. Keep a plan file, check what's live on the pre-release hosts, ask IRSA/SSDC early for what only they can provide (SIA collection names, DOI, Explanatory Supplement), make and test the changes, then the release-day steps.references/touchpoints.md: every release-dependent spot in each SPHEREx notebook, with its DR1 value.references/decisions.md: rules settled during DR1 (show only the newest release, which DOI to cite, which flags count as bad, who owns which notebook), gotchas that cost time, and DR1's release-day checklist.scripts/check_release.sh <release>: reports what's live for a release on irsadev, irsatest and production (SIA, TAP, IBE,cloud_access), on S3, and the Explanatory Supplement.scripts/run_sdt_release_test.py: executes the whole Source Discovery Tool notebook against a pre-release host (SIA, IBE in place of S3, that host's Firefly viewer) and prints a summary of what to check. Running every cell is what found the D4/D5 detector bug fixed in the DR1 PR.Notes for reviewers
.claude/directory in the repo. Claude Code picks up skills in.claude/skills/automatically; nothing else uses them. The docs build (MyST, driven bytoc.yml) and the notebook tests (which look only undertutorials/) ignore it.🤖 Generated with Claude Code