Open mwang87 opened 5 years ago
@abisarvepalli Any ideas?
Failures:
https://proteomics3.ucsd.edu/ProteoSAFe/status.jsp?task=30880cb91f624271bdb491a4f49d006a https://proteomics3.ucsd.edu/ProteoSAFe/status.jsp?task=a500055a171b48c39d85e04c01b19dbc https://proteomics3.ucsd.edu/ProteoSAFe/status.jsp?task=f23deedcb24f4fa89dff3ef0ccada37b
Will take a look at it today! On Sep 9, 2019, 9:18 PM -0400, Ming Wang notifications@github.com, wrote:
@abisarvepalli Any ideas? Failures: https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=30880cb91f624271bdb491a4f49d006a https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=a500055a171b48c39d85e04c01b19dbc https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=f23deedcb24f4fa89dff3ef0ccada37b — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Hi @abisarvepalli , there is indeed an issue with the python wrapper. https://gnps.ucsd.edu/ProteoSAFe/status.jsp?task=a000a574dc9e4eec9b5fc64ab36e836f
The workflow works great 👍. Currently, we are running into scalability, probably due to the RAM allocated by default. These are various test jobs:
Identifying determinism of MapAlignerPoseClustering +/or MetaboliteAdductDechargerSteps by cloning QTOF 1K
job 10 times:
https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=e456b747d2844ebd96bbedf81ad687e7 https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=f4883ae04a0b45c59461a977852189bf https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=85af02dc2cd44811b86422e26b9b5ba7 https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=46f16333897f4a7f96413906bc7c1baf https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=2ae0ffbbbd424c998c3264180d22678a https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=29fef784da9f428d85ae078f32a2df50 https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=d7c7a30ae8404fd9b7b4f2938f18c98d https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=f4883ae04a0b45c59461a977852189bf https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=bf501a7128b94d52a95e9ea96b361032 https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=81c34c4bd6e44d5b9f22051cbe8ae374
Like before, all jobs failed at the MapAlignerPoseClustering. I tested the parameters from Optimus that were used to scale up to 2K. https://proteomics2.ucsd.edu/ProteoSAFe/status.jsp?task=b74a82124fc34f7a98fd08c88ddb0a8d
Unfortunately, I got the same issue as before for the 1K samples jobs. @abisarvepalli @mwang87 can we test with more RAM to see if that helps.
This has already been given 20GB of RAM, and the error is not an error indicating a lack of ram.
@abisarvepalli can you open an issue on the OpenMS repo ?
@abisarvepalli Is the OpenMS workflow ready for merge into master and deployment into GNPS?
Current Status: Merged code in and deployed to proteomics2 and testing
The test workflows will be:
Small Large Large 2