Johannes Rainer

One possibility could also be to not throw an error if there are no MS1 spectra but *only* a warning - I could implement that. But you're still using the...

I fixed it now for the new functions/objects. I also had a look at the old code base and it is not clear to me where the error is thrown...

First of all, please install `devtools::install_github("sneumann/xcms", ref = "jomaster")`. Could you try to first load all data into `xdata` (i.e. the MS1 and MS2 files) and then run the peak...

With the latest code from the *jomaster* branch (install with `devtools::github_install("sneumann/xcms", ref = "jomaster")`) I did the following: ```r library(xcms) fls

Re `featureValues`: so far, correspondence analysis (`groupChromPeaks`) can only be performed on MS1 data, which means that only MS1 peaks get grouped and you will only have MS1 features defined....

Thanks for the update @cbroeckl . In addition to your workaround I will implement option 1) - I think that would be the cleanest solution, also because all the data...

Problem is we can not add yet another vignette to `xcms` because the build time is already very long - also, we would need the mzML files - which I...

After some discussions I think it might be better if, instead of a common repository with workshops, we have a central index side listing all. Then each workshop is under...

@cbroeckl , I have now implemented everything you need for option 1) (I hope) in the *jomaster* branch: - You can work with the full data now (no need to...

Had the same issue with people from my lab running Windows. This should do the trick: ```r Sys.setenv(R_REMOTES_NO_ERRORS_FROM_WARNINGS="true") devtools::install_github("sneumann/xcms", ref = "xcms") ```