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

Updates to epilepsy metrics and plotting #12

Open
DowntonCrabby opened this issue Sep 10, 2021 · 3 comments
Open

Updates to epilepsy metrics and plotting #12

DowntonCrabby opened this issue Sep 10, 2021 · 3 comments
Assignees
Labels
issue type: feature request new metrics, plots or features for software issue type: QC Issue QC issue or trend not captured by existing reporting question Further information is requested

Comments

@DowntonCrabby
Copy link
Collaborator

DowntonCrabby commented Sep 10, 2021

Describe the Issue
The epilepsy probability and interichtal events plot currently only uses the first 5 minutes of the motion corrected movie for its calculations. This should be run for the whole movie. Additionally the failure threshold is currently if the epilepsy probability metric is above 0%, but instead of failing the session, this actually triggers qcers (and usually a manager/scientist as well) to review the 2p movie and behavior movie to determine whether or not there was actual epileptic activity.

This process seems subjective and up for interpretation. Two additional questions arise: are we worried about aberrant brain activity or animal health? Depending on our concerns we might have different approaches to what causes data or a mouse to fail.

Clearer guidance is needed.

Expected behavior

  • Calculations should be run on the entirety of the motion corrected movie and not the first 5 minutes.
  • clear flag and failure thresholds should be established
  • a protocol for manually reviewing the data should be established, with specific guidance on animal health & behavior, and separately aberrant brain activity

Scope
Interichtal events are usually related to a few specific cre lines but this is really run on every experiment and has a broad scope.

Additional context
In the future we should also investigate whether the presence of transient laser/scanner noise (issue #1 )on the Mesoscope impacts the probability calculation.

There could also be issues with the lowered frame rate per FOV on the mesoscope impacting this calculation.

This was originally a trello card: https://trello.com/c/xwCx8qMa/50-issues-with-epilepsy-plot

@DowntonCrabby DowntonCrabby added question Further information is requested issue type: feature request new metrics, plots or features for software issue type: QC Issue QC issue or trend not captured by existing reporting labels Sep 10, 2021
@DowntonCrabby DowntonCrabby added this to Needs triage in Issues_Triage Oct 4, 2021
@DowntonCrabby DowntonCrabby moved this from Needs triage to kick to stakeholders in Issues_Triage Oct 4, 2021
@DowntonCrabby DowntonCrabby moved this from Needs triage to Low priority in Stakeholders Group Prioritization Jun 8, 2022
@DowntonCrabby DowntonCrabby moved this from Low priority to Needs triage in Stakeholders Group Prioritization Jun 8, 2022
@samiamseid
Copy link
Collaborator

Following up with details from a recent slack thread on this topic:

Examples of a session that triggers the current epilepsy metric, but we suspect is not due to epilepsy: \allen\programs\mindscope\production\learning\prod0\specimen_1213623863\ophys_session_1221545894\ophys_experiment_1221714233\processed\1221714233_suite2p_motion_preview.webm
http://mouse-seeks/qc/1223267374
http://mouse-seeks/qc/1223027165

Marina suggests that we calibrate the metric for each reporter line due to differences in event magnitudes.

Literature on event magnitudes in interictal events https://www.eneuro.org/content/4/5/ENEURO.0207-17.2017

@matchings
Copy link
Collaborator

@matchings
Copy link
Collaborator

@seanmcculloch has this been resolved in the new mouse QC system, or does it need to be included in the "need to haves"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue type: feature request new metrics, plots or features for software issue type: QC Issue QC issue or trend not captured by existing reporting question Further information is requested
Projects
Issues_Triage
Stakeholders
Development

No branches or pull requests

5 participants