-
Notifications
You must be signed in to change notification settings - Fork 80
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
There's something wrong with maxo's calculations. #759
Comments
This is indeed surprising - do you have a reproducible example for me to check? ideally using some of the data files from the msdata R package (thus no need to share data). |
That's so weird, I tested the example in msdata with the same process and everything works fine. And this is my workflow: msdatamzMLpath <- file.path(find.package("msdata"), "iontrap") When I use my own data, which is a Waters MSe mode acquisition, the maxo of its primary chromatogram peaks (findChromPeaks) does not coincide with the highest point of the EIC (chromPeakChromatograms). So I'm guessing it's due to the data, but I'm not sure why. msdata and MSe data I'm using the same cwp parameter for both. |
Can I share the data with you for a test? |
I changed the ppm parameter from 180 to 20 and everything is working fine. So the ppm parameter can't be set too large? And how do I get the limit of this value? |
Generally, the Also, if you say you have MSe data... I assume your data file distinguishes between the MS1 and MS2 spectra (i.e. you have MS1 and MS2 spectra once you import the data) and you perform the peak detection on MS1 data. |
Hello,
I'm having some problems.
When I finished finding peaks using findChromPeaks, I wanted to extract the corresponding peaks, so I used the function chromPeakChromatograms. the code ran fine, but the results were abnormal, the maximum intensity of most of the peaks did not agree with the result of findChromPeaks (maxo). What is the reason for this?
I also change the parameter aggregationFun, like "sum", "max", in chromPeakChromatograms, but the problem persists.
The text was updated successfully, but these errors were encountered: