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

Direct A excitation correction #60

Closed
DanielisRutkauskas opened this issue May 30, 2017 · 5 comments
Closed

Direct A excitation correction #60

DanielisRutkauskas opened this issue May 30, 2017 · 5 comments
Labels

Comments

@DanielisRutkauskas
Copy link

Hi,
a question about the definition of the correction factor for direct excitation of acceptor with donor excitation.
Excerpts from the tutorial notebook:
d = loader.photon_hdf5(filename)
d.dir_ex = 0.04

What is the meaning of dir_ex - is it d according to Lee et al. and also dAA according to "Derivation of FRET and S correction formulas", or is it dT according to "Derivation of FRET and S correction formulas" and also dir_ex_t according to "FRET Correction Formulas" in the online manual?

@tritemio
Copy link
Owner

tritemio commented May 30, 2017

Data.dir_ex is the coefficient "dAA" as defined by Lee et al. 2005 and as in eq. (21) in Applying Corrections in Single-Molecule FRET.

The coefficient dir_ex_t corresponding to eq. (24) in the "applying correction ..." paper is used to correct FRET values when calling the function fretmath.correct_E_gamma_leak_dir() (docs).

Historically, I first implemented Data.dir_ex following Lee et al. 2005 as a property that corrects all the bursts values (so when you plot histograms the correction is applied).
Later I realized that, you can express the A direct excitation in terms of physical parameters (dir_ex_t), so you can correct also non-ALEX measurements. At the same time I found that all the corrections are better applied after fitting the uncorrected E_PR.
So now my recommended approach is estimating E_PR_mean for a population and then correcting this value with fretmath.correct_E_gamma_leak_dir().

See also this discussion.

@DanielisRutkauskas
Copy link
Author

Thank you for the reply.
What is your suggestion for finding gamma, in the case of adopting your recommended approach? The question exists because according to Lee et al. leakage and direct excitation correction factors are found from D-only and A-only species in EPRraw/Sraw histogram, respectively. Correcting EPRraw and Sraw with these corrections then yields EPR/S histogram from which gamma is calculated given there exist at least two spiecies with different EPR and medium S. However, with your approach, I understand, this corrected EPR/S histogram is not calculated.

@tritemio
Copy link
Owner

tritemio commented May 30, 2017

From a set of ALEX measurements you should definitely follow Lee at al. to compute gamma. As a first step you have to estimate leakage and direct excitation (d_aa coefficient). Then the gamma-fitting procedure also gives you beta which is the factor linking d_aa with dir_ex_t. So, with this procedure you can estimate also dir_ex_t that can in principle be used in non-ALEX measurements on the same samples.

When you plot FRET or ALEX histograms you can apply all the corrections and visualize the corrected histogram (or not, it's your choice). For plotting, if you want to apply direct excitation correction you should correct the burst data using Data.dir_ex.

But beyond plotting, you probably want to obtain the corrected E (mean) for one or more populations. What I'm suggesting is simply fitting the RAW E_PR histogram instead of the corrected E histogram. Then, apply the formula to correct this fitted value and obtain E for the population of interest. I suggest this because applying the correction to the entire histogram (i.e. to the burst-level data) can distort the shape of the peaks and render fit less accurate (especially using Gaussian fit).

@DanielisRutkauskas
Copy link
Author

All right, I see what you mean. Thanks for additional clarifications.

@tritemio
Copy link
Owner

This issue was moved to OpenSMFS#2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants