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

MS1 precursor ion/s with 34S isotope pattern #213

Open
Mattesimone opened this issue Mar 18, 2022 · 3 comments
Open

MS1 precursor ion/s with 34S isotope pattern #213

Mattesimone opened this issue Mar 18, 2022 · 3 comments

Comments

@Mattesimone
Copy link

Hi,

I run massql tool (Commandline) to search for sulfur-containing signals with the following query:
QUERY scaninfo(MS1DATA) WHERE MS1MZ=X AND MS1MZ=X+1.996:TOLERANCEPPM=2
I'm attaching the unexpected output in which the difference between mz_lower and mz_upper mz is always 20.

Then I execute the same MassQL query against my data at GNPS but the job failed: ID=be0a38f7bdd2472da1f5cd5b4d58bdfc
Screenshot 2022-03-18 at 14 37 41

Thanks in advance for help

Matteo

@mwang87
Copy link
Owner

mwang87 commented Mar 18, 2022

Yes, your job just took too long on GNPS so it was killed. The mz_upper and mz_lower, are by definition above and below the "comment" which is the value of the X you found. Its mostly been used to make rendering much easier, though likely it should probably belong in an accompanying script rather than main MassQL.

To make it run faster, I'd recommend setting minimum peak intensity thresholds for your X peak.

QUERY scaninfo(MS1DATA) WHERE MS1MZ=X:INTENSITYPERCENT=5 AND 
MS1MZ=X+1.996:TOLERANCEPPM=2

@Mattesimone
Copy link
Author

Mattesimone commented Oct 11, 2022 via email

@mwang87
Copy link
Owner

mwang87 commented Oct 13, 2022

Awesome! Good luck with it and feel free to ask questions and contribute.

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

2 participants