-
Notifications
You must be signed in to change notification settings - Fork 14
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
Fail to load AmpliconArquitech files #69
Comments
Hi Alex, Yes, please use a full path (not relative). What are the contents of your data repo directory If the data repo files haven't been downloaded into that directory (presumably for GRCm38), then this may cause a bug. You can download the relevant ones here if not obtained already. Also possible that there is a bug with using GRCm38 and the nextflow version of AmpliconSuite. Thanks, |
Hi! My list of files is this:
I downloaded it from the repository you mentioned. The most strange thing is that the file |
Thanks Alex, This is very strange - can you try the 1.0.5 beta version of circdna? If you need a hold-over solution until this is resolved, there are Docker & Singularity images for AmpliconSuite available here. |
If you are able to download this small hg19-aligned BAM file from SRA it would be a good test of your installation as well (provided you download the appropriate data repo for this sample as well, e.g. create |
Hi! Now it seems to work, but I get the following error:
I'm not sure if I need to add any parameter to the config of nf-core. Thanks! |
Unfortunately, I am not able to reproduce this issue locally when I test the latest version of the tool on a GRCh38-aligned sample. If you do Did it work for your mm10 sample? |
Description of the bug
Hi!
I'm running the pipeline with the following pipeline:
In the process
NFCORE_CIRCDNA:CIRCDNA:AMPLICONCLASSIFIER_AMPLICONSIMILARITY
I get the following error:At first I though it could be a problem due to being a relative path or so, but using
Yields the same error but with the full path.
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: