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

Need faster way to select neuropil cut. #17

Open
mjlm opened this issue Apr 30, 2015 · 0 comments
Open

Need faster way to select neuropil cut. #17

mjlm opened this issue Apr 30, 2015 · 0 comments

Comments

@mjlm
Copy link
Contributor

mjlm commented Apr 30, 2015

Selecting the neuropil has become slower now that we're typically getting a larger number of cuts.

Two non-exclusive options:

  1. Manual: Update the neuropil scatter and traces while Tab-ing through the clusters to select a neuropil region. I did a test implementation and it's a little slow (but OK). Most of the time is taken by the debleaching (precisely, the call to robustfit within the debleaching function) and could be sped up by using simpler debleaching for this feature...
  2. Automatic: My main criterion for assessing the quality of a neuropil fit is the amount of negative-going transients in the subtracted trace. We could calculate the trace for all potential neuropil ROIs and automatically pick the one with the smallest mean(trace(trace<0)). Problem: This might not be robust to selecting nonsensical choices so we might have to pre-select potential neuropil ROIs with another criterion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant