Date

Attendees

Notes from the previous meeting

Discussion items

DiscussedItemNotes
(tick)Project news

Fritz Mueller :

  • no DLMT due to the holiday in Chile
  • SITCOM general assembly (monthly) this morning:
    • Troubles with a crane at Summit which affects the schedule for COMCAM
    • The camera ship from SLAC is scheduled end of March (may affect the schedule)
  • Hiring shift specialists


(tick)Next Qserv release

Fritz Mueller on the status of the release?

  • got tagged and built
    • Igor Gaponenko will get it tested at USDF
    • it may be deployed at IDF (`--int` tomorrow during the Thursday patch window
  • The new version of the Qserv operator has been merged into the main  branch.
(tick)"New" Qserv

Migration to Alma 9

  • passes the integration test
  • testing at USDF (TBC)
  • (warning) unit qhttp keeps failing
    • there is a bit of mystery here:
      • the GHA CI keeps failing 100%
      • the locally run test failure rate is 20%
      • Eliminating LSST logging at the qhttp brings the failure rate down to 0.
    • eliminated the BOOST test framework as an initial suspect by writing a replica of the test as an ordinary command-line application

(minus) (the actual discussion is delayed till next week)

Ingesting user-generated data products

Fritz Mueller :

  • still working on the requirements documents (a preliminary version should be available by the end of the day tomorrow, Thursday)
  • we will have an in-person meeting (Fritz Mueller John Gates Igor Gaponenko) next Tuesday to discuss this matter
  • still need to get feedback from Frossie
    • There will be a dedicated discussion on the proposed changes to the TAP service tomorrow
    • Next ADASS is planned for November (at Tucson) where we might have a chance to continue discussing this topic (as as well as plans for Qserv)
      • some of us could go travel to Tucson for the meeting
    • Colin Slater Qserv API (user interaction model) is the main concern here

Igor Gaponenko :

  • as a reminder, the last discussion was not limited to discussing extensions to the ingest API. Qserv by itself was a target as mentioned in Fall 2023 Qserv status and plans

Action items

  •