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.

Sign up for GitHub

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

Jump to bottom

Retention time for spike-ins #96

Open

KarinSchork opened this issue Sep 25, 2024 · 2 comments

Labels

discussion publication

Member

KarinSchork commented Sep 25, 2024

give retention time (and maybe total RT duration) in minutes instead of seconds?
retention time delta column can be confusing, especially as expected retention times are hard to determine

KarinSchork added discussion publication labels

Member

julianu commented Sep 25, 2024

Do we generally use minutes? Maybe wait until the mzQC hackathon and see, whether there is a defined unit.
total RT for the spike in? This is not monitored right now, or is it?
Hm, I was under the impression that exactly the delta would be the most interesting between the runs, as it directly shows you the shift from the expected value

Member Author

KarinSchork commented Sep 25, 2024

we use seconds but @SvitiMPC said they use minutes all the time in the lab and it may be more intuitive
there are the columns SPIKE_MPCSPIKE2_MZ_895.9493_RT_4212_RT_at_Maximum_Intensity and the delta is the difference between that and the expected RT
I think the problem is that the expected RT cannot really be set accurately, especially when gradients change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment