Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Follow up actions should actually lead to something #319

Open
matchings opened this issue Sep 26, 2023 · 0 comments
Open

Follow up actions should actually lead to something #319

matchings opened this issue Sep 26, 2023 · 0 comments
Assignees
Labels
issue type: information &/or decision More information or a decision is needed. Also relates to inter team communication

Comments

@matchings
Copy link
Collaborator

Description of needed information

The new QC system updates include very useful follow up actions when specific metrics are flagged or fail, but currently we do not have a process for implementing the necessary follow up. Ophys RAs do refer some issues to MPE for consideration, but project leads and other stakeholders typically dont know when QC issues pop up in their data.

Here is what is in the follow up actions part of the report:

image (36)

Describe the solution you'd like

Ideally we would have some kind of automatic notification system for project leads, analysts, MPE, etc that are triggered whenever a given flag / fail tag is detected.

Another potentially helpful solution would be for Ophys Operators & Scientists to review the fail / flag occurrences for recently collected data at the QC Ops meeting each week, and/or by the ophys team at their weekly meeting. This would require some kind of dashboard or roll-up visualization of what tags occured, and on which rigs, cre lines, etc.

Finally, Scientists and Data Analysis should receive instructions on how to find data for their projects in the mouse QC system so that they are empowered to check the QC on their own and provide feedback to the ophys team if they have any concerns.

@matchings matchings added the issue type: information &/or decision More information or a decision is needed. Also relates to inter team communication label Sep 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue type: information &/or decision More information or a decision is needed. Also relates to inter team communication
Projects
None yet
Development

No branches or pull requests

3 participants