-
Notifications
You must be signed in to change notification settings - Fork 3
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
PMDDA Error in unserialize(node$con) : error reading from connection #3
Comments
Yes. This error is parallel computation related. I wonder where you run the xcmsrokcer? HPC or local computer? |
I am runing on a local computer, with 16 cores of CPU and 32 G of memory. |
How can I reduce the number of parallel calculation in order to keep it going? Although this will prolong the running time. |
You can add the following code before the error codes to skip the parallel computation: BiocParallel::register(BiocParallel::SerialParam(), default = TRUE) Another option is to use a local version of PMDDA. xcmsrocker is mainly designed for hpc and user need to know how to mapping local path through docker to use their own data. In your case, a local version might be much easier. You could clone this repo: https://github.com/yufree/pmdda Click 'PMDDA.Rproj' in RStudio to open the project. Then you will need install.packages('renv')
renv::restore() |
Thanks for this detailed information. I will try to follow the local version. |
Hi, |
It's wired. Anyway the csv file could be generated via the mzrt<-readRDS('srmxset.rds')
enviGCMS::getmzrt(mzrt,'srm') Then you should see |
Hi yufree,
I am trying to use this good tool xcmsrocker that you developed and try to repeat your PMDDA workflow, however, when I run the demo data, and reach to the step:
IPO
resultRetcorGroup <-
optimizeRetGroup(xset = optimizedXcmsSetObject,
params = retcorGroupParameters,
plot = F,
subdir = NULL)
I always got an error says "Error in unserialize(node$con) : error reading from connection".
From the internet, it seems to be a problem with parallel calculation, I wonder if you know how to deal with this issue?
Thanks very much for your help.
The text was updated successfully, but these errors were encountered: