-
Notifications
You must be signed in to change notification settings - Fork 3
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
Correction factors #38
Comments
Maybe. To think about:
In general I see the Photon-HDF5 file as "immutable raw data". Any post-analysis data should go in a different file (every time we write the file there is a risk of corruption). But for these 3 parameters it may be ok to do an exception. |
@smXplorer, after more thoughts I think it would be useful to provide these 3 fields as a standard place where to store these parameters. Even with the limitation that the source of these parameters would be not specified, a standard place is useful. They would be optional. These parameters depend on both sample and setup, but it is hard to choose between
These fields are spot-specific and would also be compatible automatically compatible with the multispot layout. This fields would not work for 3 or more color ALEX, and I think it's ok to leave this case out for now. |
You could add a field (URL, DOI) for each parameter to specify its origin (Notebook, publication, etc). |
Yes, we could add a new filed |
There is the issue of which direct excitation definition to use. Using reference: https://doi.org/10.1101/083287, the direct excitation Dir term can be expressed as a function of n_aa as in ALEX:
or as a function of physical parameters
The link between the two is:
The advantage of the second definition is that the same coefficient is valid for all measurements using the same A fluorophore and D laser (regardless of A-laser). In particular it can be used for single-laser smFRET measurements. We can use the definition |
It would seem useful to offer the ability to save calculated correction factors for 2-color smFRET:
The text was updated successfully, but these errors were encountered: