Skip to content

autotrace FRET lifetime less than 5 frames #16

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

Open
dsterry opened this issue May 20, 2025 · 0 comments
Open

autotrace FRET lifetime less than 5 frames #16

dsterry opened this issue May 20, 2025 · 0 comments
Assignees

Comments

@dsterry
Copy link
Contributor

dsterry commented May 20, 2025

Problem: autotrace's "FRET Lifetime" criteria is defined as the number of frames with FRET efficiency above a threshold in groups of at least five frames. This approach was taken to avoid the contribution of spurious 1-frame events to the total FRET lifetime. However, this behavior can be confusing to users who notice that 1 frame gives the same result as 5 frames. There is a tooltip on the control describing this, but users are likely to miss it.

Workaround:

  1. Use the criteria "maximum FRET value" to define a threshold for detecting single-frame events.
  2. In cascadeConstants.m, set rle_min=1, which will disable the feature.

Development ideas:

  • In autotrace, don't allow user to set a FRET lifetime criteria value less than rle_min.
  • In autotrace, allow user to adjust rle_min or disable the feature.
@dsterry dsterry self-assigned this May 20, 2025
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