-
Notifications
You must be signed in to change notification settings - Fork 10
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
Process ALIGNER:chainMerge (chainmerge)
terminated with an error exit status (1) -- Execution is retried (1)
#3
Comments
@zhoudreames thank you for using nf-LO! I probably need a bit more information on how you run the workflow. Do you mind sharing the Best |
Hi
Probably an error about mafstats installation? |
Hi @KristinaGagalova
Best |
Thank you for the fast reply @RenzoTale88 Here some more details:
so its probably chainMerge that doesn't produce the output. Thank you in advance |
@KristinaGagalova Thanks, this suggests me that some step before that probably failed for one reason or another.
In this way we can try to trace back where the issue originated. |
|
Ok for whatever reason the chain file is effectively empty. The issue lies upstream from this. We can trace back the issue by looking at the folder in which |
I don't get the same error on the test set so its probbaly something related to runs on local files
|
Yeah I suspect that too. You can trace back each process, and see what went wrong and in which stage. To do so, I recommend you open the |
That's weird, if I check the output in the directory with the symlink there is no error (.exitcode is 0)
This is my .nexflow.log
|
Is the file |
Ok, I found the error. the src16.tgt19.psl was indeed empty and tracing back I fount this error:
I am not familiar with chainfiles or coordinates liftover but is there possible that I need to change the overlap or src sizes to different values? Is there any rule you follow based on the genome size? |
I see! That is a situation I haven't considered (working on larger genomes I never came across this type of situation).
And reducing progressively while you perform the reduction. On my side, I'll work on a possible fix for this tomorrow. Thanks for spotting this! Andrea |
@KristinaGagalova @zhoudreames thank you both for your patience. This turned out to be a possible relevant issue, and thanks to this it is probably now fixed. I've uploaded a new version of the workflow, that should sort the problem out. If you are running the previous version of the workflow, I would suggest you to drop the previous version and then repeat the analyses:
Or alternatively to run everything using the
Please, do let me know if you come across further issues, and thank you again for using nf-LO! Andrea |
thanks for your help, I resolved it. |
tell me to close this problem if you solved it, thanks~ |
@zhoudreames thanks, I'll wait for @KristinaGagalova to confirm or rise more points on this. If it works for her I'll close it. Thanks again! |
@RenzoTale88 looks good now! Thank you for the fast fix |
@KristinaGagalova glad to have fixed this :) |
I got the error information when runing the n-Lo,this log showing in blow:
WARNING: Could not load nf-core/config profiles: https://raw.githubusercontent.com/nf-core/configs/master/nfcore_custom.config
Launching
https://github.com/evotools/nf-LO
[pedantic_ptolemy] DSL2 - revision: 312fb56 [main]======================================
__ _ ____
/ | | | / __
_ __ | | ______ | | | | | |
| '_ | | || | | | | | |
| | | | | | || || |
|| ||| |____/
======================================
source : chrY.oldVersin.fa
target : DRC.chrY.fa
aligner : minimap2
distance : medium
custom align : -cx asm5 -l 10000
custom chain : false
source chunk : 20000000
source overlap : 0
target chunk : 10000000
target overlap : 100000
output folder : ./liftover_Minimap2
liftover name : liftover
annot : false
annot type : false
liftover meth. : liftover
igenomes_base : s3://ngi-igenomes/igenomes/
igenomes_ignore : false
no_maf : false
skip netsynt : true
max cpu : 143
max mem : 26 GB
max rt : 240.h
Using CrossMap
executor > local (5)
[13/61a6e5] process > PREPROC:src2bit (src2Bit) [100%] 1 of 1 ✔
executor > local (10)
[13/61a6e5] process > PREPROC:src2bit (src2Bit) [100%] 1 of 1 ✔
[cb/e667b4] process > PREPROC:tgt2bit (tgt2Bit) [100%] 1 of 1 ✔
[3e/c206c5] process > PREPROC:splitsrc (splitsrc) [100%] 1 of 1 ✔
[83/de485d] process > PREPROC:splittgt (splittgt) [100%] 1 of 1 ✔
[73/c5a594] process > PREPROC:pairs (mkpairs) [100%] 1 of 1 ✔
[58/cefc2c] process > ALIGNER:minimap2 (minimap2.medium.src.tgt) [100%] 1 of 1 ✔
[26/7d4da4] process > ALIGNER:axtChain (axtchain_m) [100%] 1 of 1 ✔
[33/4e27ca] process > ALIGNER:chainMerge (chainmerge) [100%] 3 of 3, failed: 3, retries: 2 ✔
[- ] process > ALIGNER:chainNet -
[- ] process > ALIGNER:chainsubset -
[- ] process > ALIGNER:chain2maf -
[- ] process > ALIGNER:name_maf_seq -
[- ] process > ALIGNER:mafstats -
[c7/cb6d2d] NOTE: Process
ALIGNER:chainMerge (chainmerge)
terminated with an error exit status (1) -- Execution is retried (1)[8d/9085f1] NOTE: Process
ALIGNER:chainMerge (chainmerge)
terminated with an error exit status (1) -- Execution is retried (2)[33/4e27ca] NOTE: Process
ALIGNER:chainMerge (chainmerge)
terminated with an error exit status (1) -- Error is ignoredThe text was updated successfully, but these errors were encountered: