Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Pau Hana at the DSSC - 5/22

  • DKIST Shake and Bake - 5/22 & 5/23

  • Start of Science Observing period OCP 2.7 - 5/24.

Personnel

SciOps and OpsTools team

Accomplishments

  • Released the Cycle 3 Proposal Call and announced the opening of the submission window through email to all of the registered DKIST users, on the NSO webpages, and on Solar News and the SHINE NewsLetter.

  • Prepared and finalized the observations for co-observing with the Sunrise III Balloon project. The Balloon is planned to launch sometime during a 7 week launch window opening on May 25 and closing around July 15, 2024.

  • Released and supported the Cryo-NIRSP Status announcement for Cycle 2 and Cycle 3 PIs: CryoNIRSP status for Cycle 2 PIs and Prospective Cycle 3 PI's.

  • Finalized plan for OCP2.7 observing window.

  • Resolved a problem on the production OpsTools stack that prevented experiments from being sent. Troubleshooting was difficult because the issue did not occur on the development/test stack, and it was unclear why it was occuring on the production stack.

TechOps team

Accomplishments

...

  • generated and tested an emergency procedure to recover the monitors in a ceph cluster after the loss of all monitors. The next ceph upgrade is planned to be done during normal DC operations in all environments including prod. Although this issue is not expected to occur, if it does occur then I need to be ready to handle it because prod ceph and everything that uses it - including transfers from the summit - will be blocked.

  • Implemented parallel paging in the processing-preparation-worker to reduce load time. The load time was reduced by an order of magnitude with the solution. This query was taking 30-40 seconds per page, and frames were taking hours just to load. Resolved a problem on the production OpsTools stack that prevented experiments from being sent. Troubleshooting was difficult because the issue did not occur on the development/test stack, and it was unclear why it was occuring on the production stack.