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
DM-37196: Modernize APDB schema #107
Conversation
5f1253b
to
b1cef34
Compare
c8e89ee
to
a169df9
Compare
a169df9
to
a3c38c2
Compare
df57191
to
ef4fe81
Compare
6314ad2
to
a5d008a
Compare
* decl->dec in names * RA-Right Ascension and Decl->Declination in descriptions
This matches the middleware convention.
5339722
to
bdd79a7
Compare
bdd79a7
to
f52ef0c
Compare
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.
Some fiddly little suggestions. I tried to suggest the same suggestions for the same column in different tables, but might not have been completely successful at that.
@@ -8812,7 +8885,7 @@ tables: | |||
- name: llcra | |||
'@id': '#CcdVisit.llcra' | |||
datatype: double | |||
description: RA of lower left corner. | |||
description: Right Ascension of lower left corner. |
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.
No need to change this now, but I just realized how ambiguous "lower left corner" is (on the sky? which way is up on the camera?). Someday this should probably be "minimum y, minimum x" or some other way to express pixel coordinates.
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.
It may or may not help if we linked to the cameraGeom docs in these kinds of places, since we do have a self-consistent camera geometry definition.
https://pipelines.lsst.io/modules/lsst.afw.cameraGeom/cameraGeom.html#camera-coordinate-systems
validityStart/validityEnd are now processing time, not visit time.
Update description of DiaSource/DiaForcedSource versions to be explicit about where they are measured.
This is to have a record of what we've changed from the imsim.yaml definitions.
These fields are Visit level, not CcdVisit level: zenithDistance, skyRotation, expMidpt[MJD], expTime, obsStart, obsStart[MJD], darkTime, physical_filter, band. Move detector id to near the top of the list Cleanup CcdVisit descriptions and add punctuation.
This is a single-value table; we only ever include data from one instrument in a given APDB instance.
f3a2e43
to
a5e9797
Compare
We've added `time_processed` as a much more explicit and easy to determine way to order DiaSources by when they were processed. This field was unused.
Also cleanup midPoint capitalization and expMidpt name. raDecTai->raDecMjdTai midPointMjd->midpointMjdTai obsStartMJD->objStartMjdTai expMidptMJD->midpointMjdTai expMidpt->midpoint
a5e9797
to
2ece4c3
Compare
No description provided.