-
Notifications
You must be signed in to change notification settings - Fork 32
CCSP docs and example schemas #747
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Brett Graham <[email protected]>
Co-authored-by: Brett Graham <[email protected]>
We will instead enforce many requirements upon reference in the science product schemas
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.
There was a problem hiding this 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.)
Co-authored-by: Adrian Lucy <[email protected]>
Co-authored-by: Adrian Lucy <[email protected]>
Co-authored-by: Adrian Lucy <[email protected]>
Co-authored-by: Adrian Lucy <[email protected]>
Co-authored-by: Adrian Lucy <[email protected]>
Co-authored-by: Adrian Lucy <[email protected]>
Co-authored-by: Adrian Lucy <[email protected]>
Co-authored-by: Adrian Lucy <[email protected]>
for more information, see https://pre-commit.ci
Co-authored-by: Adrian Lucy <[email protected]>
Co-authored-by: Adrian Lucy <[email protected]>
| 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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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 | |||
There was a problem hiding this comment.
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.
This includes:
latest/CCSPdirectory which will house all CCSP/PIT schemas. These will be organized by team name (CCSP/SNfor theSNteam, etc). Tests were updated to check this new structure.ccsp_minimalandccsp_custom_productthat 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.example_custom_productandexample_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
radtests.docs/page.no-changelog-entry-needed.)changes/:echo "changed something" > changes/<PR#>.<changetype>.rst(see below for change types).romancalregression test (https://github.com/spacetelescope/RegressionTests/actions/workflows/romancal.yml) with this branch installed ("git+https://github.com/<fork>/rad@<branch>").roman_datamodelsutilities and tests.News fragment change types:
changes/<PR#>.feature.rst: new featurechanges/<PR#>.bugfix.rst: fixes an issuechanges/<PR#>.doc.rst: documentation changechanges/<PR#>.removal.rst: deprecation or removal of public APIchanges/<PR#>.misc.rst: infrastructure or miscellaneous change