|
LSSTApplications
1.1.2+25,10.0+13,10.0+132,10.0+133,10.0+224,10.0+41,10.0+8,10.0-1-g0f53050+14,10.0-1-g4b7b172+19,10.0-1-g61a5bae+98,10.0-1-g7408a83+3,10.0-1-gc1e0f5a+19,10.0-1-gdb4482e+14,10.0-11-g3947115+2,10.0-12-g8719d8b+2,10.0-15-ga3f480f+1,10.0-2-g4f67435,10.0-2-gcb4bc6c+26,10.0-28-gf7f57a9+1,10.0-3-g1bbe32c+14,10.0-3-g5b46d21,10.0-4-g027f45f+5,10.0-4-g86f66b5+2,10.0-4-gc4fccf3+24,10.0-40-g4349866+2,10.0-5-g766159b,10.0-5-gca2295e+25,10.0-6-g462a451+1
LSSTDataManagementBasePackage
|
Should really have FITS be a separate Storage.
Need to implement overwriting of FITS metadata PropertySet
Should support an additional color-based position correction in the remapping (differential chromatic refraction). This can be done either object-by-object or pixel-by-pixel.
Need to deal with oversampling and/or weight maps. If done we can use faster kernels than sinc.
Need to deal with oversampling and/or weight maps. If done we can use faster kernels than sinc.
How is the time of observation for a visit specified? And how is the association pipeline deadline derived from this? Possibly post-DC2.
[Post DC3a] How are variability probabilities set for new objects? Currently, the probability is set to 100% for any new Object.
[Post DC3a] StoreStage can issue multiple database requests in parallel
The end of the pipeline needs to send out a 'triggerAlertGeneration' event. Post-DC3a, since there is no alert generation pipeline.
[Post DC3a] Add a version number to chunk delta file names. Use a database table to track the version numbers of valid delta files in transactional fashion. Note that the transaction which updates these version numbers should include the insert to the object table as well as the append to the historical DIASource table. Use MySQL API directly for this?
1.8.5