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

Retention Time Deletion #4

Open
bouranij opened this issue Oct 31, 2019 · 0 comments
Open

Retention Time Deletion #4

bouranij opened this issue Oct 31, 2019 · 0 comments

Comments

@bouranij
Copy link

Hello WarpGroup team,

Your suite of software (X13CMS and WarpGroup) have been super helpful for completing my untargeted analysis, however, I am running into a strange issue with WarpGroup. I am feeding an xcmsSet object which has been preprocessed using XCMS (centwave, obiwarp, density-grouping) into WarpGroup and it works no problem. However, when I call the resulting WarpGroup object the run time has been changed to NaN-NaN.

The xcmsSet object fed into WarpGroup
'> xs.rg
An "xcmsSet" object with 60 samples

Time range: 226.7-2415.6 seconds (3.8-40.3 minutes)
Mass range: 61.9879-999.0991 m/z
Peaks: 27029 (about 450 per sample)
Peak Groups: 49
Sample classes: D2O_4h, D2O_Baseline, H2O_4h, H2O_Baseline, QC

Feature detection:
o Peak picking performed on MS1.
o Scan range limited to 1 - 7463
Profile settings: method = bin
step = 0.1

Memory usage: 46.3 MB'

The object after WarpGrouping
`> xs.wg
An "xcmsSet" object with 60 samples

Time range: NaN-NaN seconds (NaN-NaN minutes)
Mass range: 96.9592-919.2379 m/z
Peaks: 28740 (about 479 per sample)
Peak Groups: 479
Sample classes: D2O_4h, D2O_Baseline, H2O_4h, H2O_Baseline, QC

Feature detection:
o Peak picking performed on MS1.
o Scan range limited to 1 - 7463
Profile settings: method = bin
step = 0.1

Memory usage: 46.4 MB`

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

1 participant