RTN-064
JOR recommendations#
Review recommendations extracted from Jira.
2025-01-09 17:08
Issue key |
Rec# |
Summary |
Report date |
Due Date |
Implementation Status |
Description |
Response |
Implementation Status Description |
|---|---|---|---|---|---|---|---|---|
OO-III.1-1 |
Prepare a readiness document for the start of the 10-year LSST |
JOR_2024_04 |
2025-08-31 |
Not Started |
Prepare a readiness document for the start of the 10-year LSST. Work with Rubin management and the agencies to define the start of the LSST by system performance criteria rather than by date. [By 2025 JOR] |
I am fine with that. It will need the full observatory to be ready. |
||
OO-III.1-2 |
Re-examine the night-time, steady-state staffing level |
JOR_2024_04 |
2025-03-28 |
Implemented |
Re-examine the night-time, steady-state staffing level to ensure efficient, long-term operation and the ability to accommodate both planned and unplanned staff absences. [By 2025 JOR] |
We have added 3 Observing Specialists to the operation plan for the full survey length (10 years). We are also looking into continuing support from the support scientists inside the summit operation group, especially at the beginning of the survey during which debugging and optimization might be happening more often. |
The added resources have been reviewed by an internal committee. Though tight, the lead OS is confident we will be able to begin commissioning successfully. We will continue to evaluate the plan and adapt as we complete SV and go in to Operations and start the LSST. |
|
DM-III.2-3 |
Ensure that specific individuals are given the authority |
JOR_2024_04 |
2024-08-30 |
Implemented |
Ensure that specific individuals are given the authority to develop and implement Rubin-specific cybersecurity policy and plans, even during the construction and commissioning phases. Roles and responsibilities between AURA, NOIRLab, SLAC, and Rubin regarding cybersecurity must be clarified immediately, even on an interim basis.[As soon as possible] |
The topic of this recommendation is completely and comprehensively covered in the NSF-DOE Data Management Standards Review and associated recommendations. We will report on further progress through that review process. Initial people at SLAC and NOIRLab have been identified to jointly discuss and agree to roles and responsibilities for cyber and data security for all the data no matter where they exist in the Rubin system. This will be well in hand before LSSTCam data are acquired. |
||
DM-III.2-4 |
Ensure that Rubin performs a 24-hour end-to-end DM system test at full scale |
JOR_2024_04 |
2025-08-13 |
In Progress |
Ensure that Rubin performs a 24-hour end-to-end DM system test at full scale, including alert and data production across the US, France, and UK, before accepting handover from construction to operations in February 2025. |
Yes we shall carry out a > 24 hour end to end test from summit through prompt processing. |
This is a compound recommendation. The multi site processing is not needed until end of Year one so Dec 2026. We may demonstrate it in 2025. Hando over to ops is also no longer Feb 2025. OR4 demonstrated alerts and full processing but on ComCam. Since we have the camera in the clean room it is sending full exposures (205 ccds including guiders and corners) at a rate faster than we will see in nighttime ops. After some adjustments most images do make it 7 seconds - given that the rate of image taking is quite quick (i.e. there is far less tan 30s between exposures) the transfer times are excellent. The config change and its impact is very visible on Oct 1 in this image (from [https://usdf-rsp-dev.slac.stanford.edu/times-square/github/lsst-dm/image-transfers-info/ImageLatency-Summit-USDF?day=20241001&ts_hide_code=1|https://usdf-rsp-dev.slac.stanford.edu/times-square/github/lsst-dm/image-transfers-info/ImageLatency-Summit-USDF?day=20241001&ts_hide_code=1]) which shows the slowest and fastest CCD transfer within each of the 1609 exposures taken (reminder we expect 800-1K exposures per night). Time between these exposures was typically 10-20s (not 34 as a nominal night). I believe this was the real issue we were after. !image-20241002-193300.png|width=589,height=453,alt=”image-20241002-193300.png”! |
|
SP-III.3-5 |
Develop and implement a plan for augmenting the current DP2 data release plan |
JOR_2024_04 |
2025-06-02 |
In Progress |
Develop and implement a plan for augmenting the current DP2 data release plan to include a set of LSST representative science observations [To be defined and approved before the end of DP1 commissioning observations]. |
Based on LSSTCam on-sky data, a plan will be developed to make DP2 representative of LSST science goals |
Any plan developed “before the end of DP1 commissioning observations” will be tentative at best. We need to know what can and will be observed during the LSSTCam on-sky observing campaign to work out how best to augment the plans for DP2 |
|
SP-III.3-6 |
Continue developing and automating the evaluation toolkits |
JOR_2024_04 |
2025-06-02 |
In Progress |
Continue developing and automating the evaluation toolkits to incorporate automatic checking of performance indicators, to speed up evaluations and provide consistent feedback independent of the observers performing the assessments. [Complete before commencement of DP2 Survey operations] |
Performance evaluation tools are under constant development and testing on Rubin commissioning data |
Yes we acknowledge this. Performance evaluation tools are under constant development. |
|
SP-III.3-7 |
Update the Rubin Early Science Program Document RTN-011 |
JOR_2024_04 |
2025-06-02 |
Implemented |
Update the Rubin Early Science Program Document RTN-011 to reflect any changes to the scope of DP2. [To be completed before the end of DP1 commissioning observations]. |
RTN-011 is a living document that is regularly updated in response to program changes and scope |
Yes we acknowledge this. RTN-011 is a living document that is regularly updated in response to program changes and scope |
|
CS-III.4-8 |
Communicate to the department heads the importance of data accuracy |
JOR_2024_04 |
2024-07-31 |
Implemented |
Communicate to the department heads the importance of data accuracy at the lowest levels of the scheduling milestone database in Jira as the information feeds into the overall schedule milestones and is relied on for short and long term decisions and shared in formal published reports. The Director’s office must provide oversight by monitoring the uploads to Jira are in fact timely and accurate. [by July 2024] |
We will make this clear to the ADs. |
A communication has been sent to the ADs (Monday, 8am MST August 26, 2024). |
|
CS-III.4-9 |
Develop a consolidated financial report |
JOR_2024_04 |
2024-10-31 |
Implemented |
Develop a consolidated financial report showing plan versus actuals by WBS and managing organization by month. [by October 2024] |
This has been completed and is included in each joint NSF-DOE monthly report. Due to the time it takes for the month close to come through the year-to-date quarterly does lag but this review recommendation is fully implemented |
||
ESH-III.5-10 |
Ensure that a thorough review of Industrial Hygiene hazards is performed |
JOR_2024_04 |
2025-02-28 |
In Progress |
Ensure that a thorough review of Industrial Hygiene hazards is performed by conducting a thorough industrial hygiene site survey within one year. This assessment should evaluate potential workplace hazards including: Volatile organic compounds (VOC’s), Dust (total and respirable), Welding fumes, Carbon monoxide, Isocyanates, and Noise. |
We fully acknowledge the critical importance of prioritizing the development of initiatives related to the review of Industrial Hygiene hazards. To ensure a thorough approach, we are committed to conducting a comprehensive industrial hygiene site survey within the next year. This assessment will meticulously evaluate potential workplace hazards, including but not limited to Volatile Organic Compounds (VOCs), total and respirable dust, welding fumes, carbon monoxide, isocyanates, and noise. |
||
ESH-III.5-11 |
Implement fall and confined space rescue plans |
JOR_2024_04 |
2025-03-31 |
In Progress |
Implement fall and confined space rescue plans as soon as possible. These plans should include retrieving a worker soon enough to minimize the effect on the worker and without endangering the lives of individuals conducting the rescue operation. These plans should include a review of rescue operation considerations, rescue equipment, and identification and training of fall and confined space rescue teams. |
We will prioritize the development and execution of fall and confined space rescue plans . |
||
M-III.6-12 |
Define a draft set of threshold criteria |
JOR_2024_04 |
2024-10-31 |
Implemented |
Define a draft set of threshold criteria that must be in place to start the survey (Oct 2024). This is the first stage in completing recommendation #1 from SC-1. |
We will provide a draft list of criteria to guide starting LSST in full operations. |
I think we can mark this one as “Implemented” (and I was able to do that). |
|
M-III.6-13 |
Complete an assessment of the Rubin staff concerns |
JOR_2024_04 |
2024-08-31 |
Implemented |
Complete an assessment of the concerns of the Rubin staff regarding the move to operations and the revise risk register as appropriate (August 2024). |
Transition to operations is what we are most concentrating on continuously. Rather than assess concerns with the transfer to NOIRLab in a general way, we are talking to ADs, teams, and individuals about their roles in Operations. The Director and RSO AD have visited Chile specifically to engage with staff. In August we spoke with 3 teams, the site manager, engineers, and other staff. We debriefed the Project Manager and will continue this approach through the transition period. Transition is a primary topic of the October 2024 NMOC meeting in Chile for Rubin. The Director and AD are engaging with NOIRLab leadership and ES leadership directly on transition issues. In October, the Director initiated team-by-team communications about the transition. More communications will occur throughout FY25. It is not useful to put this in the risk register at this point. We are actively working on staff concerns. |
Thu Jan 9 17:08:19 UTC 2025