Skip to content

Conversation

@hernandezc1
Copy link
Contributor

@hernandezc1 hernandezc1 commented Sep 9, 2025

Summary of Changes

Changed

  • docs/source/listings.rst
    • updated resource names and descriptions for LSST data listings

@codacy-production
Copy link

codacy-production bot commented Sep 9, 2025

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
+0.00%
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (4f67242) 985 689 69.95%
Head commit (17809a0) 985 (+0) 689 (+0) 69.95% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#109) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

@hernandezc1 hernandezc1 requested a review from troyraen September 9, 2025 20:11
excluding image cutouts and metadata.
It has the same schema as the original alert bytes (except cutouts), including nested and repeated fields.
Equivalent tables exist for previous schema versions: alerts_v7_3, alerts_v7_1.
Equivalent tables exist for previous schema versions: alerts_v7_9, alerts_v7_4, alerts_v7_3, and alerts_v7_1.
Copy link
Contributor

Choose a reason for hiding this comment

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

Is everything less than v7.9 simulated data? If so, it won't be available alongside the real data.

Comment on lines 261 to 263
The filename syntax is: `<schema_version>/<alert_date>/<objectid_key>=<objectid>/<sourceid_key>=<sourceid>.avro`.
For example, `v7_9/2026-10-01/diaObjectId=3516505565058564097/diaSourceId=3527242976319242284.avro` or
`v7_9/2026-10-01/ssObjectId=3516505565058564097/diaSourceId=3527242976319242284.avro`.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
The filename syntax is: `<schema_version>/<alert_date>/<objectid_key>=<objectid>/<sourceid_key>=<sourceid>.avro`.
For example, `v7_9/2026-10-01/diaObjectId=3516505565058564097/diaSourceId=3527242976319242284.avro` or
`v7_9/2026-10-01/ssObjectId=3516505565058564097/diaSourceId=3527242976319242284.avro`.
The filename syntax is: `<schema_version>/<alert_date>/<objectid_key>=<objectid>/<sourceid_key>=<sourceid>.avro`.
DIA Object example: `v7_9/2026-10-01/diaObjectId=3516505565058564097/diaSourceId=3527242976319242284.avro`.
Solar System Object example: `v7_9/2026-10-01/ssObjectId=3516505565058564097/diaSourceId=3527242976319242284.avro`.

It's hard to look through the filenames and figure out why there are two examples, so something like this would make it more clear.

Copy link
Contributor

Choose a reason for hiding this comment

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

BTW, have you tested in any way to make sure the = in the filenames are ok? I don't think it will cause any problems be we should probably check a bit to make sure. Maybe try downloading a file from the command line and/or python.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Maybe try downloading a file from the command line and/or python.

No issues encountered when trying to download a file using Python and the command line

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