trum994
trum994
Thanks for the response Wouter. I think you are correct that nanoplot didn't actually crash. Exit status was zero, and the output contained the html reports. However nfcore nanoseq workflow...
I have the same problem. Using singularity. ` guppy_basecaller: error while loading shared libraries: libcuda.so.1: cannot open shared object file: No such file or directory` I tried @asalhab's recommendation to...
So I ended up keeping the `-profile singularity` but added a custom config that looked like this: ``` singularity { enabled = true runOptions = '--nv -B /libs/current/lib64:/usr/local/nvidia/lib64 -B /libs/current/bin:/usr/local/sbin'...
I'm seeing a similar issue with other nanoplot processes: > Error executing process > 'NFCORE_NANOSEQ:NANOSEQ:QCBASECALL_PYCOQC_NANOPLOT:NANOPLOT (sample1)' > > Caused by: > Missing output file(s) `summary/*.png` expected by process `NFCORE_NANOSEQ:NANOSEQ:QCBASECALL_PYCOQC_NANOPLOT:NANOPLOT (sample1)`...
@wdiao-zju if you go into that summary directory and open the *log file what's the error message that you see? I created an issue at Nanoplot [here](https://github.com/wdecoster/NanoPlot/issues/284).
I have the same question.
Thank you for your quick response! I'm not too familiar with the legal side but their TOS recently changed and our organization did not renew our license. We're restricted from...
I'm new to methylseq analysis. One of the scientists in our lab need to run the analysis against the positive and negative control sequences (pUC19 and Lambda). I think this...