This page captures remaining topics, issues, activities, etc for the DM Science team to address in  FY24 and through the end of construction. Items that are not complete but could be transferred to Operations should also be listed. Items that must be addressed to support construction completeness should be indicated as such

Topics 


TopicDetails, notes, commentsKey people involvedCan be transferred to Operations
DMSR requirements verification

Verification of DMSR construction requirements. Construction completeness and success is contingent on the completion and verification of all P1 DMSR requirements and as many P2/3 as possible.  Includes the VCD reporting.

Jeffrey Carlin (lead)

Leanne Guy 

All DM Science POs supporting verification activities

No (except those requirements that receive a 'waiver' to complete during operations
DPDD revisions Many pending changes to the DPDD No - although DP/DR specific data product descriptions are under Ops. 
Improvements for user-facing schemas

Question for Gregory



Criteria for deciding on 2x15 v 1x30 sec 'snaps'What are the criteria to decide whether we go with 2x15 or 1x30 snaps? What tests will we execute? This will need LSSTCam images. if ComCam goes back on sky - what early tests could  we do with single-raft data?
No - key part of construction completeness
Strategy for template generation in year 1
Yes 
Selection of DIAObject timeseries features
Eric Bellm +refinement of an initial set can be deferred to ops
incremental template generation strategy in commissioning
No
Construction Papers?
AllNo
Topics from the Science Platform?

Question for Gregory

Leanne: I would like to review the schedule for development and rollout of the remaining RSP functionality based on feedback from the DPs so far. 


Interactions with system-level science verification and validation

Anticipate situations where support from DM Science Team would be invaluable:

  • Science performance metric specifications and mathematical details of how metrics are defined (extension of work done for DMSR verification)
  • Prioritizing and addressing emergent needs for configuration changes, algorithmic adjustments, etc.
  • Quantifying the impacts of emergent issues, recognizing which can be dealt with "in software", and how much effort will be needed to address


Cross matchingThis is a real use case that comes up more and more.  Alert Brokers and Joint Processing are two topics that will need it. In Gaia we provided neighbour tables to facilitate crossmatch. Can we consider something similar to support the community and reduce demand on our services. Note - we have no requirement to provide crossmatch with any catalog

Special programs

Non standard alert packetsWhat is the ETA for this, where are we?
Software and services for (re-)creating coadds
Jim Bosch 






  • No labels