Versions Compared

Key

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

DKIST General

Operational Status

  • We are currently in week 3 of Engineering Period 2024b

Events

  • DKIST Ambassadors workshop - 5/13 - 5/16

  • NSO Users Committee meeting - 5/13 14 - 5/1415

  • Release of DKIST Cycle 3 Proposal Call - 5/15

  • 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.

...

  • Completed all remaining (preparatory) work for the release of the Cycle 3 Proposal Call opening on 05/15/2024, including finishing and approval of the call document and all updates required for the NSO webpages and other documentation. 

  • The Science Operations Specialist (SOS) Team delivered the first draft of one of the papers they will present at the next SPIE conference, titled: "DKIST Science Operations Specialists’ Training Program and Document Management." 

  • The OpsTools Team stood up a new production Stack on AWS that is completely segregated from the test and development stacks. The new production stack includes more memory, which will alleviate some of the problems the Ops team has had with the AWS servers hanging with large data transfers. This is the culmination of a 3-month effort.

  • The OpsTools team completed Proposal Architect changes required prior to the OCP 3 proposal call. This included changes in available instruments and wavelengths.

TechOps team

Accomplishments

...

Data Center team

Accomplishments

...

  • The OpsTools team completed Proposal Architect changes required prior to the OCP 3 proposal call. This included changes in available instruments and wavelengths.The DC team reduced the size of quicklook movies that are viewed/downloaded from the portal. A number of movies exceeded 20-minute lengths, which does not fit within the "quick look" description.

  • The DC team repaired issues on the portal related to dates and times.  Previously, it was noticed that some date/times were 

    • not reflecting the actual description of what the date/time was supposed to be.

    • some data/times were local when they should have been UTC.

...