Melissa Graham to talk to Federica Bianco to push stack-club participation
Colin Slater to set up a confluence page and telecon to start a discussion on metadata (The page is LSST Data Model and the minutes of the first telecon on are attached.)
Leanne Guy to update LDM-294 with agreed time allocation for product owners
Discussion: but comments on RFC-520 for the Glossary are being integrated as they come in. John Swinbank found a TON of errors that I just don't have the depth of experience to catch, which makes me think at least one other person should be assigned to read the definitions (or, could split up the alphabet between multiple people)
Only some definitions are contentious or disputed. These will be iterated by the SST. The rest can be published already.
Melissa Graham Separate out terms in the glossary that are disputed for further iteration by the SST. Publish the non-contentious definitions now.
How does Alert stream get its QA info? Where are metadata described? E.g. the # per CCD, CCD-to-CCD variance, xy cross-correlation
Eric Bellm argues that this should be done in the PPDB.
What about False Source injection?
This is large issue. We will be required to characterise the detection efficiency per image and this will requite false source injections. The issue is already covered in DM-12584 covers this issue. We can close out of this issue
How do we know centroids where forced photometry was performed
CTS and EB discussed prior to meeting - this is an open question whether use the history of forced detections or store the information. Partially addressed in RFC-517. It is doable in current schema but is there a better implementation? Not high priority
Do we really need 11 params for PSF model in Source? How about psfFlux and error, at the position of centroid (that is, don't refit for the position)
(Jim Bosch )Issue of adding Sources, like DIAObjects, to Object list -> Tucson DMLT
People requested a more automatic join from objects and sources. Wanted to derive objects by associating them with sources? Jim and Robert are not keen on doing this. Leanne will run past Željko next week.
Discussion of DBs, with Andy Salnikov, after reading LDM-135. - ``The LSST baseline database architecture for its real time Alert Production relies on horizontal time-based partitioning. To guarantee reproducibility, no-overwrite-update techniques combined with maintaining validity time for appropriate rows are employed.'' -> what about deleting DIAObjects during MOPS processing? (for LDM-151, not DPDD)
Follow up ticket:
DM-15784
-
Getting issue details...STATUS
footnote 45: where is positionMotionLnL?
hard to understand what this comment means, but in DIAObject table, pmParallaxLnL is the "Natural Log of the Likelihood of the linear proper motion-parallax fit"
why are covariances separated if simul fit? (Eric Bellm Talk to Mario)
RHL has argued to use a centroid-specific algorithm, then use that as a fixed location for aperture, psFlux [trailed source and dipole fits have their own positions]. Result should be close enough that it’s not worth the trouble.
flags in DIAObject table: is there any info in other docs to add as a footnote? (Eric Bellm Talk to Mario)
outcome: no other information exists; DIAObject flags will all be new.
DM-15929
-
Getting issue details...STATUS
will serve as an initial start)
SSObject table: why two values of MOID? (Eric Bellm Talk to Mario)
outcome: this will be obsolete after
DM-12092
-
Getting issue details...STATUS
footnote 59: What Gbps WAN do we have now? Talk to Mario
Mario has no current information; should be captured by
DM-15512
-
Getting issue details...STATUS
Large edits:
add dipole fit for DIASources
(CTS: Already done)
redesign of nightly Level 1 db; in sec. 4.2.1 bullet 6 need to mention 12 months window; see also bullet 8: the name of db? also, ``full'' light curves? ask Mario...
(CTS: Done in sec 3.2.1 bullet 6)
redesign of nightly Level 1 db: the main section is 4.3.5 (add Colin's plot?)
remove reference to Level 1 db in 3.3.5 (leanne to check)
decide whether to move model description up front, and whether to add anything (remove)
make MOPS diagram and refer to it in Section 4.2.2 (wait for MOPS changes)
can DIASource be DIAForcedSource and ExtendedTable?
Data storage question - RFC from Eric in progress
ditto for Source and Forced Source (look at models plus ``other'' data blocks)
Remove this - these tables are different
TBD - DIASource: add both light centroid and peak PSF centroid (i.e. mode and mean)
2 new features for the DIASource table - is this useful? Discuss with an RFC. Eric to look into it and create an RFC
trailed source needs centroid (CTS: Done)
DIASource: add aperture mags (CTS: Done)
fpSky is on direct template image and rename it to fpBkgd (CTS: Done)
TBD - we need to bring back DIAForcedSource (CTS:
RFC-517
-
Getting issue details...STATUS
)
adaptive moments in DIASource table (switch to xy), add moments for PSF (CTS: Done)
look for spuriousness in LSE-30 (OSS?), add to DIASource table? (CTS: Done)
Defer remainder to next meeting
do we want curved trail? -> footnote
do we want to fit a gaussian convolved with PSF to each DIASource?
Leftovers from Colin's Minutes for 2016-03-23: (Colin Slater )
From the SAC: Alerts only include footprints for the detection band; is that enough?
SAC: do we need more than 30 days of precovery fluxes for new DIASources? ZI: yes, 30 days is only about two data points in a given band and we don't know colors for transients
ZI: science case for moving variable stars: how do we get LCs and pm/parallax? Sophisticated matching of DIAObjects to 3 nearest Objects: might want to do the nearest star and the nearest galaxy, and the most probable object
moving variable star: a bias in motion due to flux=const.?
Eric Bellm to follow up on the alert stream/QA and metadata issue
Colin Slater Create a create a ticket to track centroids where forced photometry question. Low priority - due date in a year:
DM-15763
-
Getting issue details...STATUS
Leanne Guy to create ticket for Colin Slater to follow-up with Mario and Željko on the question of the number of parameters for the PSF model in the Source.
Leanne Guy Crate ticket for Željko to look at the Source/Object issue. Update: Željko requested a few weeks to look at his notes.
Colin Slater to follow up on the database architecture for alert production
Eric Bellm to follow-up with Mario on 4 issues concerning SSObject schema
Eric Bellm to discuss with Robert Lupton about adding both light centroid and peak PSF centroid (i.e. mode and mean) to DIASource
Leanne Guyto remove free text from DPDD of all issues already dealt with or moved to tickets
Robert Lupton Clarify the meaning of time in the object table. 1 sentence description in sdm_schemas, can link to a short DMTN. Update 2022-02-09: Meeting to resolve this on 2022-02-21
Leanne Guy Prepare to consult the PST on the question of providing compressed PVIs for AP outputs, to cover the period before the data become available in a DR.
Parker FagreliusPatrick Ingraham how long will it take to do a scan as described? No need to scan the whole WL range but will require additional points outside nominal lambda range.
Eli Rykoff , Leanne Guy Develop a proposal for what calibration processing, hardware, data we actually need and what will be needed for DR1. This has implications for the ORR and for prioritisation of work in commissioning
but picky good – mostly you flagged things that i thought sounded adequate. so i think a couple more eyes on these definitions now will prevent future corrections.
2 Comments
John Swinbank
Melissa Graham
but picky good – mostly you flagged things that i thought sounded adequate. so i think a couple more eyes on these definitions now will prevent future corrections.