Skip to content

Conversation

@braingram
Copy link
Collaborator

@braingram braingram commented Oct 21, 2025

This includes:

  • docs updates describing CCSP schemas. Further documentation will be added as interaction with the PITs proceeds and more is learned about their data products and needs. MAST will link to these new rad docs in a document they are preparing to provide to the PITs.
  • add a latest/CCSP directory which will house all CCSP/PIT schemas. These will be organized by team name (CCSP/SN for the SN team, etc). Tests were updated to check this new structure.
  • 2 component schemas are added ccsp_minimal and ccsp_custom_product that will be referenced in CCSP schemas. The docs describes when each is supposed to be used and tests were added to check for the structure mentioned in the docs.
  • 2 example CCSP example schemas are added example_custom_product and example_derived_mosaic. We may want to delete these prior to the next release if we have real PIT products (or even if we don't). They are useful for testing and illustration purposes but those benefits weight against the need to maintain functionally useless schemas.

Link to built docs: https://rad--747.org.readthedocs.build/en/747/

Tasks

  • Update or add relevant rad tests.
  • Update relevant docstrings and / or docs/ page.
  • Does this PR change any schema files?
    • Schema changes were discussed at RAD Review Board meeting.
  • Does this PR change any API used downstream? (If not, label with no-changelog-entry-needed.)
News fragment change types:
  • changes/<PR#>.feature.rst: new feature
  • changes/<PR#>.bugfix.rst: fixes an issue
  • changes/<PR#>.doc.rst: documentation change
  • changes/<PR#>.removal.rst: deprecation or removal of public API
  • changes/<PR#>.misc.rst: infrastructure or miscellaneous change

@braingram braingram changed the title WIP CCSP docs and schemas CCSP docs and example schemas Oct 22, 2025
Based on MAST feedback we want to allow
the posibility for a schema that doesn't reference
a SOC schema to reference ccsp_minimal instead.

The unit test that checks this was updated to
allow for this case.
Copy link

@adrianlucy adrianlucy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks excellent! I just have a bunch of minor proposed changes. (For proposed changes to example_custom_product and example_derived_mosaic, I can adjust the docs later in accordance with any changes that get approved.)

braingram and others added 9 commits October 24, 2025 13:55
Co-authored-by: Adrian Lucy <[email protected]>
@braingram braingram marked this pull request as ready for review October 24, 2025 19:41
@braingram braingram requested review from a team and WilliamJamieson as code owners October 24, 2025 19:41
@braingram braingram requested a review from PaulHuwe October 24, 2025 21:01
center of the spatial image, or the target coordinates
of a spectrum or light curve. May be null for large
survey images, simulated data, etc.
type: number
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Description says it can be null, so does that need to be allowed in the type?

center of the spatial image, or the target coordinates
of a spectrum or light curve. May be null for large
survey images, simulated data, etc.
type: number
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Description says it can be null, so does that need to be allowed in the type?

description: |
Waveband of this data product, used to enable archival
searches. Select from: RADIO, MILLIMETER, INFRARED,
OPTICAL, UV, EUV, XRAY, GAMMARAY.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should these be an enum for the strings below?

@@ -1 +0,0 @@
../../../../latest/manifests/datamodels.yaml No newline at end of file
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we be preserving datamodels-1.5.0.yaml‎? We have with previous versions.

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.

3 participants