...

1. Run ci_hsc with large set of Gen3 changes.  (Waiting for 

   Jira
   server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-17023

    to merge to master)
2. Jim Boschneeds to pick what changes/features goes in that set)
3. Run RC2 patch through as much of DRP as applicable
   1. needs RC2 bootstrap
4. Run RC2
   1. DB folks will now have larger set of data flow information for analysis (along with updated schemas)

   Planning

   • When OODS includes Gen3 (Tucson and Mountain)
     • Raw Ingest (AuxTel and ComCam)
     • Purge (to keep size of registry small)
     • Multi-registry
       • Staff schemas (db admin procedures, etc)
       • Unique Site IDs?
     • Get calibs from any production runs (subset and merge??)
   • When NCSA DBB endpoint includes Gen3
     • Raw Ingest (AuxTel and ComCam)
     • Ingestion of certain LFA files? (wavefront???)
     • Multi-registry
       • Staff schemas (db admin procedures, etc)
       • Unique Site IDs
   • EFD ETL (Quick Look & DBB copy)
     • No additonal Gen3 work because joins would happen on visit?
     • Will EFD ETL values be used in QuantumGraph generation?
   • Gen3 "production" pipeline runs
     • RC2 DRP running at some cadence like we currently do with Gen2
     • AuxTel pipelines (calibration?  drp?)
     • BPS
       • HTCondor version of BPS
       • BPS job activator
   • Next OPS rehearsal (Feb-ish)
     • Not clear that it will use Gen3, but can assume that is the hope.
     • Could include everything from image generation 

   Technical Discussions

   • Discussion of Tim's review of ticket

     Jira
     server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-17023

       (Repo import/export)
   • DM-20845 Support re-run of pipetask on the same output collection (

     Jira
     server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-20845

   • obs_lsst gen3 support now merged (

     Jira
     server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-16297

     )
   • Need to sort out OBSID vs EXPID in data model.