...
- Refer to LDM-643.
- “Prepare for ComCam on the sky”.
- How will observing proceed?
- How will changes be folded in?
- How will processing be incorporated into the daily operations of the system?
- Inform e.g. our approach to change control: how do you change how the DAC is read out? How do you fall back to a previous system?
- Exercise whatever systems we have available, or use shims to make the rehearsal possible.
- However, the real aim is the interaction between the various teams (summit, Tucson, LDF); reality of hardware etc is not fundamental.
- However, using hardware to make the rehearsal “hands-on” makes it more compelling.
- Previous rehearsal was based on simulated data.
- This is a commissioning rehearsal, rather than preparation for a steady state operations scenario.
Outstanding questions:
- Which instrument should we use to drive the rehearsal? Simulations, or AuxTel/LATISS, or ComCam?
- In the near term, AuxTel will be in stasis; ~months before it is back online.
- Probability ComCam will be running in La Serena at some level, but it's not clear what level of connectivity it will have.
- Wil reckons “quite a bit”; it's in the data center.
- A moving target in terms of availability.
- Could be used to generate biases, darks, flats.
- Could play fake images through the NCSA test stand. This obviously doesn't exercise ComCam hardware.
- Can inject “interesting” images, but it takes some effort.
- Decision: target ComCam in the Recinto.
- Backup plan: use test stand at NCSA if ComCam is not available. Specifically, the date takes priority over the hardware availability.
- What compute hardware do we use?
- The commissioning cluster should be available.
- Also want to exercise batch compute as part of this exercise at NCSA.
- When do we feel we need to run this rehearsal?
- Do we need to rethink ops rehearsals given our current situation? E.g. introducing more rehearsals in future, as things start coming back online.
- Note there is a pre-ops milestone which may fold in to this rehearsal.
- That milestone implies we want this done by the end of June.
- Aiming for May gives enough time to get ComCam up and running, but likely the summit will still be closed so people will be available.
- There is still some managerial work to be worked out to get ComCam going.
- As above, date takes precedence, and we use the test stand if ComCam isn't available.
- Some uncertainty about the availability of code to perform ingestion by May.
- Decision: Doodle poll key individuals for three days in May.
- But can reconsider if ingestion is unavailable on that timescale.
- Do we need to rethink ops rehearsals given our current situation? E.g. introducing more rehearsals in future, as things start coming back online.
- How long should the rehearsal last?
- Three days last time; allows time for handovers, debriefs, etc.
- Decision: the duration will be at least three nights (four calendar days).
- If the exercise is run during the day using ComCam in Recinto, then the equivalent of three nights is fine.
- Who are the key personnel?
- Chile: Kevin Reil, Brian Stalder (likely as observing scientist; alternatives are Sandrine Thomas, Chuck Claver, Kevin Reil, Tiago Ribeiro), Cristian Silva
- Tucson: Michael Reuter, Patrick Ingraham (& Chuck as observer).
- Execution staff / NCSA: Monika Adamow, JD Maloney, Robert Gruendl, Matt Kollross
- SDQA: Lauren MacArthur, Jeff Carlin
- Depends on exactly what pipelines get run, what high-level requirements can we test?
- Pipelines (as troubleshooting): Merlin Fisher-Levine
- Note there is a pre-ops milestone which may fold in to this rehearsal.
- That milestone implies we want this done by the end of June.