This LCR applies LCR-733 to LSE-140 and corrects some other minor issues. It does not attempt to fully define the telemetry items expected from the auxiliary instrumentation; that will be left for a later LCR.
The Base Network plan has been delayed relative to the baseline due to the updated schedule for construction and occupancy of the Base Facility. This LCR reflects the updated dates.
The US Network plan has been delayed while we coordinated with ESnet for dedicated 2 x 100 Gbps links between Atlanta and Chicago. The ESnet links provide additional path diversity and guaranteed latency for prompt processing over leased service from internet2. This coordination is documented in a request document and technical requirements document, which when finalized will be posted in docushare. The activities and dates in this LCR reflect the implementation plan and schedule for the ESnet links.
LSE-239 was developed to provide the definition of the Base Data Center (BDC) requirements for the Base construction contracts and the BDC Information Technology and Communications (ITC) infrastructure design. Since that version, much has been learned and the requirements have been migrated into the project SySML requirements model. A new version of LSE-239 has been prepared as a document generated from Magic Draw, and has also been substantially re-organized, to more cleanly separate those sections directly applicable to the Base Facility construction contract (Sections 1 - 3), versus those more targeted at the ITC infrastructure design (Appendices I and II). Finally, as the formerly baseline Tape Library has been recommended to be replaced in the BDC ITC design baseline (LCR-781 and follow-on), requirements related to the Tape Library have been deprecated into Appendix III.
Resolves a long-running formal gap in our requirements flowdown. Makes the contents of the DPDD (LSE-163) authoritative in deriving DM-level requirements (i.e., in the DMSR, LSE-61) by stating in the OSS that the data products generated by DM shall conform to the DPDD.
Notes ~60 day delay in the installation of the Summit-Base and Base-Santiago DWDM equipment, triggered by late delivery from the equipment vendor. New schedule shows installations complete by roughly November 2017.
Adds the new image types introduced by LCR-773 (New Camera Image Types) to the Camera requirements and OCS-Camera ICD. Superficially this doesn't require a response in DM-level documents; however, the exploitation of the new image types is driven by calibration requirements and so most likely they should eventually appear in DM documents.
Note that as of LCR-773 itself is Approved but not Fully Implemented.
This is mostly a cleanup pass on a key OCS middleware definition document. The DM-to-OCS interface depends on its contents, so it's likely that some consequential changes to LSE-72 will be needed.
In 2015, the project shifted from the then-existing DM-to-T&S ICD LSE-77 to a new "Base Data Center Requirements" document, LSE-239, to capture the needs of DM for data center space at the Base. LSE-77 became effectively a dead letter in the process. This change request is intended to just clean that up. Final result: LSE-77 has been withdrawn.
Perform additional early integration activities, notably around the use of the CCOB camera test facility to generate data to be ingested into DM on a regular basis.
LSE-63 has not been updated since 2011. This update includes some minor modernizations based on current best practice and removes mention that we are currently in R&D phase.
Adopt the following requirement: "The LSST project shall maintain user access to the contents of all Data Releases. This facility may be provided with reduced performance and capacity for Data Releases older than the most recent one, but be qualitatively identical otherwise." in place of the current policy of maintaining access only to the two most recent data releases.
Proposes that a common Summit-Base service be created that extracts all observation metadata (from published telemetry or the EFD) intended to be packaged with the image files, storing an artifact containing all this metadata as "headers" for later retrieval.
Q: Does this have anything to do with the reformatted EFD database? -XW
LCR-849 is to make LSE-78 consistent with and refer to the Network Sizing document LDM-142. Requested CCB if this can be voted on via the electronic voting process. I think it is non-controversial and was discussed at some length in the DM TCT when we last updated LDM-142.It would be good to get this done, as there are a number of more significant changes to the same documents coming very soon as a consequence of Tiger Team activities.
Implicitly sharpens requirements on ability to determine the correct pixel geometry upon data ingest from Camera to DM. May have an implication for the generation of difference imaging templates, at the (~annual) template-creation level and/or at the nightly template-warp-instantiation level.
Eliminate Base Network Outage Buffer; Expand Summit Camera Image Buffer
Status
colour
Green
title
FULLY IMPLEMENTED
Unclear
Kevin Long is awaiting guidance on what WBS element to use for the additional budget for the enlarged buffer.
The "documents affected" is "Unclear" because it has not been completely decided whether to implement this as a change to requirements or as a specification that exceed the requirement. This is a separate question both at system and at Camera level.
Provide a means for the OCS to launch predefined batch processing actions at the Archive Center. Likely to be used for, e.g., producing synthetic calibration images following the collection of the input flats, bias frames, etc.
Requires that DM be able to handle two types of standard visits: two 15s exposures, or one 30s exposure. Somewhat vague on the question of how closely the two types of visits could be interleaved.
A further round of technical updates to the OCS-to-subsystem device interface. The draft already serves as the basis for the prototype and early integration work that is ongoing.