-
Notifications
You must be signed in to change notification settings - Fork 1
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 executing process > 'GuppyDemultiplexExisting' #12
Comments
Thanks for writing @fernanarr, sorry for the delay. I was able to fix the issue by using full paths for the |
Hi! Thanks a lot for your answer. Now, my run_nf.sh looks this way
When I run it, I get this result:
In the results folder, I get two new folders: "aggregate_assembly_assessment" and "aggregate_contamination" but I can't open the files "all_nextpolish2.stats" and "all_contamination_stats.txt" (both with 1KB) inside of those folders. Am I doing something wrong again? Sorry for my insistence, but I can't figure out what to do to solve this on my own. Thanks again for your help |
Hello @fernanarr two quick thoughts.
|
Hi Francesco, Of course, here is my .nextflow.log file I've cloned the code and downloaded the singularity in september the 7th, so both are quite recent. Thanks to all for your help |
As a sanity check I just cloned the github again and set it up again. And it's running fine on my end. I think there may be a singularity problem on your end. Based on your path I assume you're running this on a local machine? Have you run pipelines with Singularity successfully in the past? Another possibility is a GPU problem, do you have GPUs that work with guppy? We currently have guppy_barcoder set up to also use GPUs for speed, I've never tried running it on a machine without GPUs. -Francesco |
Hi Francesco, Our GPU works fine with Guppy. We have an Nvidia GTX 3070TI. We also have CUDA installed. Running
We are running Ubuntu 20.04 in WSL2 and this is the first time that we try to run a pipeline with Singularity. Thanks again for your help. |
I'm running into this same error, and am similarly having difficulty troubleshooting it. I'm still not sure that my barcode specification is correct, so I tried to run
I'm not terribly familiar with Singularity, so it's possible that my test is missing something. But I think this could explain the mystery failures.
|
Sorry for dropping the ball on this. @fernanarr Aaron recently update the singularity container, it might be worth trying the new one. I can't make promises but on my end i wasn't able to reproduce that error. So i really have no other explanation. I know of at least another person who used the latest container at another institution on their own system and had it work starting from the barcoding step. @pdexheimer, I have just learned a neat little trick about singularity from Aaron. To let singularity use the computers gpus you have to add without --nv i get the same error
with --nv error goes away
and just for good measure, here is guppy_barcoder working on our example data
another thing to keep in mind is that if you are using custom barcode sequences, we have ours in the singularity container, if you want to test your own you have to mount them in the singularity container, i gave an example of how i mounted some fastqs above I would recommend testing out that barcode configs are working outside of the container first since the singularity step just adds more complexity, once it's working outside it should work inside. |
I'm trying to run Circuit-seq using the example data (run starting with fastqs), and I'm having a problem. ambl@ambl-H97M-D3H:~/Circuitseq/example_data/run_starting_with_fastqs$ bash exrun_nf.sh After running, there are two folders in the repository (run_starting_with_fastqs), named "results" and "work". and named all_contamination_stats. This is my run_nf.sh Am I doing something wrong? Thanks very much for your help. Sincerely. |
Hi @AMBL-CW, This looks like a sample sheet issue? I put a new python script in the base folder called pre_flight_check.py. You can run it like:
I've tried to enumerate some of the common setup errors, and as we find more, I'll put them in. Could you try running this on your sample sheet and let me know what it says? If it passes, I'd love to learn more about your setup. Thanks! -Aaron |
Thank you for reply, Aaron! **ambl@ambl-H97M-D3H:~/Circuitseq$ python pre_flight_check.py -s example_samplesheet.tsv +-----------------------------------------------------------------------------+ Is there any problem with example_samplesheet.tsv? Thanks again your help. Sincerely. |
hi @AMBL-CW, The references described in your sample sheet should be set to the path of any references you have for your known plasmids (and should be NA if a map doesn't exist). Moreover, you do need to fill in your sample sheet with any samples you might have loaded on the run, one row for each. There's a lot in the configuration, so I made a simple example that should run with the respository and the singularity sif file. In the run_with_basecalling directory there's now a script called run_nf_with_example_data.sh Aaron |
Good morning,
I'm trying to run Circuit-seq using the example data before trying it with our own, and I'm having a problem that I can't solve.
Everytime I run
bash Circuitseq/pipelines/run_nf.sh
, I get this error:This is my run_nf.sh
I've tried to modify the path value for --basecalling_dir several times without success. I'm not able to figure out what might be happening.
Perhaps, there is an error in my run_nf.sh that I can't see. Could you please chek it out?
Thanks a lot in advance.
Regards
The text was updated successfully, but these errors were encountered: