-
Notifications
You must be signed in to change notification settings - Fork 9
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
Error when executing ksrates test in nextflow #38
Comments
Hi dawickell, Thanks for pointing this out! I managed to recreate the same error when using the latest version of Nextflow (22.04.0.5697). Can you try using an older Nextflow version (21.10.6.5660, the version we used to test the code)? In the meantime I will look into how to make the code work with the latest Nextflow version. A quick way to use a specific version of Nextflow is by adding the
Best, |
Thanks for the quick response. So using the previous version of Nextflow, I definitely made it farther along but now the test example terminates with the following error:
I'm pretty sure this is the result of my local installation failing (a common problem with python packages since upgrading to my current computer) on my laptop. As inspection of the setup_adjustment.log file reveals:
I have a similar issue on the server and am going to try to get singularity installed and try going that route instead. That being said, this does seemed to have solved my immediate problem with nextflow! Thanks again, |
I'm glad it helped. |
I attempted to install the dependencies manually on my laptop. That being said, I have been able to get the example working on our server using singularity. Thanks again for all your help! |
Hi, I'll now close this issue, but feel free to add other posts or open a new issue if needed! |
I am trying to get ksrates running on my laptop (Macbook M1 Pro running macOS Monterey) using nextflow. I am able to get nextflow to run successfully but when I try to run the test example I get the following error:
When I check the .nextflow.log file it doesn't tell me much more than the initial error message
I have also tried running the next flow pipeline on our server (running Ubuntu 14.04.5) and get the same error.
Any idea what might be going wrong?
The text was updated successfully, but these errors were encountered: