2024-01-11: QC Ops Meeting

[macarenasa]

Agenda: Please include any additional agenda items below as new comments!

• Operational issues @samiamseid @shiellac Issues Page
• Moving to Mouse-QC - @seanmcculloch

[macarenasa]

Operational Issues:
Mouse QC-Dev v Mouse-QC production

• Older reports, older than 11/16 will not open. After 11/16 reports open. Dev system was intended to have recent data to test Mouse-QC -- use production Mouse-QC space.
• Saturated pixels metric (example) - back populating required. only available in QC-Dev? Yes. We won't be able to go back and fill in older sessions in Dev space. In Mouse-QC we'll have ability to backfill up to 2 years ago (3-6 months of back populating saturated pixels metric is priority).
• Training history (towards bottom) swapping to the top - a "nice to have" - not a blocker to move to production space.

Moving to Mouse-QC production space:

• Copy logs and acquisition logs to Mouse-QC from Mouse-seeks
• Timeline: Ready Tuesday morning
• @seanmcculloch send out an email to Sam and Shiella to communicate Mouse-QC production space is ready to go
• Checking reports have been populated in dev space v production space? should populate on both. Prioritize data in Mouse-seeks to move to production space.
• @samiamseid and @seanmcculloch connect to go over QC data that needs to move to production space.
• Okay to work in Mouse-seeks until data are ported over Mouse-QC production? Users, please use Mouse-seeks and move to Mouse-QC on Tuesday.

[macarenasa]

• Container view of reports - Mouse-QC production space could handle container report upgrades. Agenda item for QC stakeholders meeting.
• Timeline: TBD - discuss at QC stakeholders meeting.