You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: