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

Add QC to evaluate full field fluorescence trace #317

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

Add QC to evaluate full field fluorescence trace #317

matchings opened this issue Sep 26, 2023 · 0 comments
Labels
issue type: feature request new metrics, plots or features for software

Comments

@matchings
Copy link
Collaborator

Feature Request Motivation

Some weird features have shown up in the full field trace lately, particularly in the SST gamma project, that appear to be due to light leak, but could indicate a variety of other issues. Here are some examples:

image (39)
image (38)
image (37)
image (34)

Requested Feature/Solution

I think it would be useful to have a visual or quantitative check on the full field fluorescence trace (raw fluorescence and/or dFF) for each experiment to check for weirdness. Some forms of "weirdness" that could be quantifiable:

overall range of values (min and max shouldn't be outside of a few standard deviations of the distribution from all past experiments)
difference of sequential values to identify sharp increases in dFF that are unexpected (like in the plot above)

also visual comparison to provided images of what a "good" or "normal" fluorescence trace looks like would be useful to catch edge cases not covered by any metrics we come up with.

Scope
all ophys experiments

@matchings matchings added the issue type: feature request new metrics, plots or features for software 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: feature request new metrics, plots or features for software
Projects
None yet
Development

No branches or pull requests

1 participant