-
Hi, I'm trying to run the Nextflow pipeline for trans analysis for my high MOI perturb-seq data. I've run steps on R console to create .odm files and the .rds object and now at the step of running the nextflow pipeline. I created a .sh script in the terminal of our university's computing cluster, but I'm getting the follwing error:
Here's a part of the code I'm running:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 8 replies
-
Sorry I might have posted this question here prematurely. I'll look into how to fix the |
Beta Was this translation helpful? Give feedback.
-
Yes. I was able to run SCEPTRE trans on Nextflow on our computing cluster. I ran it on a development node instead of submitting as a job on the computing nodes since it required internet connection. If you have a tip on how to run it offline with qsub please let me know. I would also like to know if you have some insight on what to expect with regards to callibration for trans discovery. I didn't run the massive-scale. Here's the trans analysis summary of my data.
In your experience, is it possible to get good calibration for a trans analysis of this scale? This was my first pass at trans analysis; I will make more adjustments as proposed in SCEPTRE documentation. |
Beta Was this translation helpful? Give feedback.
-
That is good to hear. I have never tried to run Nextflow on a system without an internet connection, sorry. Perhaps this page might be useful? The setup of your analysis looks good. I do see that there are ~15,000 false discoveries. The difficulty of obtaining good calibration is not about cis versus trans per se, but rather the number of pairs in the discovery set. I see that you have ~450,000 pairs in your discovery set. IMO this is not a crazy number; I have seen good calibration out to ~450,000 pairs before. Fortunately, your mean log-2 fold change on the negative control pairs looks quite good. My initial recommendation would be to decrease |
Beta Was this translation helpful? Give feedback.
Sorry I might have posted this question here prematurely. I'll look into how to fix the
curl: (6) Could not resolve host: www.nextflow.io
Nextflow issue itself first.