Difference between revisions of "UCSD-2019: Technical Working Group: Data Management"

From CMB-S4 wiki
Jump to navigationJump to search
Line 29: Line 29:
 
Big questions to answer here:
 
Big questions to answer here:
 
* What are we missing?
 
* What are we missing?
 +
 +
Note that the L2-level stuff, including the bi-weekly telecon, is all coordination and management; real work is done at L3 and below.
 +
 +
DM scope redefined as raw data coming off the telescopes to well-characterized "reduced data (maps, etc.)." (Used to be "well-characterized maps" but transients...)

Revision as of 14:46, 17 October 2019

Link back to agenda

Charge

  1. Identify key decisions that must be made (and justified) prior to CD-1/PDR,
  2. Make progress on (or actually make) those decisions,
  3. Lay out a timeline and process for making each decision, consistent with the post-decision work and internal reviews that will be needed to complete preparations for CD-1/PDR,
  4. Ensure that those timelines and processes are understood and supported by the collaboration, and that we (together) believe we can follow them.

Agenda

  1. L2 Overview (Julian Borrill/Tom Crawford) slides
    1. Subsystem Management (Julian Borrill) slides
    2. Data Movement (Sasha Rahlin) slides
    3. Software Infrastructure (Ted Kisner) slides
    4. Data Synthesis (Sara Simon/Andrea Zonca) slides
    5. Data Reduction (Colin Bischoff/Reijo Keskitalo) slides
    6. Transients (Don Petravik/Nathan Whitehorn) slides (note conflict with Transients parallel)
    7. Site Hardware (Tom Crawford) slides
  2. Simulations for Flowdown (Sara Simon) slides

Remote attendance

Zoom link


Notes

Big questions to answer here:

  • What are we missing?

Note that the L2-level stuff, including the bi-weekly telecon, is all coordination and management; real work is done at L3 and below.

DM scope redefined as raw data coming off the telescopes to well-characterized "reduced data (maps, etc.)." (Used to be "well-characterized maps" but transients...)