-
Notifications
You must be signed in to change notification settings - Fork 18
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
pAGC for MS3 scans #32
Comments
The scan from which pAGC data is derived must be an ion trap full scan. If it's not, i.e. if you set the IsPAGCScan to true for anything else, you'll see a message in the console saying "WARNING:: IAPI pAGC scan definition must be a linear ion trap full scan. Executing scan, but not as a pAGC scan." To answer the last question, if you set the pAGCGroupIndex for your MS3 to match the last pAGCGroupIndex for the last pAGC LIT full scan, it'll take the pAGC data from that scan. If you want the MS3s to have different injection times, you can set the AGCTarget parameter to different values. |
Thanks for the fast reply - just to clarify, the AGCTarget parameter is the only way to modulate the injection times of MS3 precursors that share an MS2 parent mass belonging to the same pAGCGroupIndex? |
That's correct, but you could also do something like set a very high target value, and then set the MaxIT parameter to something relatively small. That way you set up a situation where you expect the injection time to max out, but it'll max out at the time you specify, scan-by-scan if you want. |
Is there any way through to API to designate an MS2 spectrum to provide pAGC data for a set of MS3 scans, or does the IsPAGCScan bool only apply for MS1 scans? I observe that if I spin out multiple MS3s on different precursors from a single MS2 (i.e. schedule a distinct MS3 for the top 3 peaks in an MS2 spectrum), all of the resulting MS3 spectra have the exact same (not maxed) injection time independent of their MS3 precursor. Maybe more basically - what spectrum does an API inserted MS3 scan refer to for its pAGC data?
The text was updated successfully, but these errors were encountered: