Skip to content
This repository has been archived by the owner on Nov 30, 2023. It is now read-only.

Error in Negative mode #2

Closed
ykim7263 opened this issue Feb 16, 2021 · 5 comments
Closed

Error in Negative mode #2

ykim7263 opened this issue Feb 16, 2021 · 5 comments

Comments

@ykim7263
Copy link

Hi,

I have tried running MS-Clean R with my MS Dial data.
I have both positive and negative datasets and I am trying to use them separately
Everything went well with the positive mode data set. But the error popped up whenever i tried to use the negative data set.
The error is described below.

Warning: Error in $<-.data.frame: replacement has 0 rows, data has 30997
[No stack trace available]

@guikool
Copy link
Collaborator

guikool commented Feb 16, 2021

Please check the previously closed issue
most of the errors come from no MS/MS data available in one of the scan mode (here probably negative)
If you try to merge pos and neg mode, be careful to have exactly the same samples number in the same order in MS-Dial
in case, send me the output files of MSdial on the email of the MScleanR corresponding author.
Best regards
G.

@ykim7263
Copy link
Author

ykim7263 commented Feb 16, 2021 via email

@guikool
Copy link
Collaborator

guikool commented Feb 20, 2021

Dear Kim
According to the size of .txt files, I think R cannot handle this data, its too big...

To my mind you need to increase the baseline treshold in MSdial (minimum peak height), its a critical parameter as noticed in our tutorial.

If you use an orbitrap, test it between 1e6 to 5e6, for TOFMS you can try between 5000 and 10 000.

For complex samples, a feature number between 500 and 2000 is usual (for the height file after MSdial processing), if you exceed this number, you may reconsider your MSdial parameters.

Best

G.

@ykim7263
Copy link
Author

Hi,

I have modified the MSDIAL parameter, but it still shows the same error.
It does work well with positive mode, even though it has a higher file size.

Best regard,
Kim

@ykim7263
Copy link
Author

Just want to let you know I solve the problem with the negative mode error, so you can close the error.
I have done two things, first I downgraded the vroom.
Also, I overwrote the negative data (Height and normalized) onto the txt file generated from the positive mode.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants