You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

OpSim "All-Hands" Meeting in Tucson June 22-25, 2015

The objective of the meeting is to plan in details the work to be done on both side of OpSim (ObSim, aka Simulator, and Scheduler):

  1. The technical scope of the work shall be captured in requirements documents. There are useful information that currently not part of the official plan, like Steve's "input" write up. Next week we should make sure we have short term plans for submitting the two updated requirements documents (Scheduler and simulator) to the CCB. 
  2. The schedule and budget for the Scheduler and Simulator in the PMCS shall reflect the technical scope. Next week we should make sure we have short term plans to update the PMCS accordingly, so the change requests can include schedule and budget information.

We should submit the change requests before the Bremerton meeting in August, so we can have wider discussions there in support of a speedy decision on the requests. Both requirements and schedule should be further negotiated with the rest of the project (Telescope and Project Science, in particular).

The agenda includes a few meetings and unstructured, "workshop style" collaboration in between. The meetings are scheduled as follows:

Monday 10 am - 12 am Kick-off and objectives (LSST Workroom)

Tuesday 10 am - 12 am Review draft Scheduler Requirements Document, and identify

  • missing information,
  • interface requirements and
  • necessary deliverables by other project component

Wednesday 10:30 am - 12 am Review draft OpSim Requirements Document, identify

  • missing information
  • interface requirements and
  • necessary deliverables by other project component 

Thursday 10 am - 12 am Review corresponding schedule and resources to be incorporated in PMCS

For all these meetings, we will use the LSST Workroom, and Blue Jeans.

 


Please note, both requirements and schedule should be further negotiated with the rest of the project (Telescope and Project Science, in particular). However, optimally by the en

  • No labels