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
Chromatograms in row 1 have different mz #511
Comments
Uh, this is a really old version of |
I managed to update my environment but I seem to get the same error. Traceback
sessionInfo()
|
Hm, strange. Could you eventually provide one or two files (or a subset of that) for which this happens so that I could check that locally and fix? |
Hi, |
I'm working on a fix... thanks for reporting/reminding |
I get an error when trying to get the chromatograms (a call to the
chromatogram
function) of an XCMSnExp object with feature definitions present.Traceback.
My XCMSnExp object, `a2def_acetone`: a set of "full-size" GC-MS samples `filterRt`-ed to where we expect to find acetone.
Trying to figure out what was going on I debugged the failing
MSnbase:::.mz_chromatograms
call and saw that the returned mz ranges have as lower bound the actual minimum mz found in the sample (as perfilterFile(xcmsObj, n) %>% mz %>% unlist(use.names = FALSE) %>% min
).Finally, another thing that I observed, which I don't know if is relevant. I have 2 objects (both fail the same way when trying to use
chromatogram(.)
):a2def
, filtered withfilterRt(., c(70, 1400))
andfilterMz(., c(35, 250))
and processed to get featureDefinitionsa2def_acetone
, the object corresponding to the stack trace and the debugger output showed above, obtained fromfilterRt(a2def, c(245, 296))
The numbers from the
rngs
variable in the debugger output correspond to the minimum mz values of thea2def
object, rather than the minimum mz values in thea2def_acetone
variable which was passed to thechromatogram
function when debugging.Thanks for the read and let me know what you think.
Edit:
Realized I am using a quite outdated XCMS version: 3.8.2
`sessionInfo()`
The text was updated successfully, but these errors were encountered: