Closed NatJWalker-Hale closed 3 days ago
Hi @NatJWalker-Hale,
Thanks for the report. I will look into this more, but in the meantime, setting N=
like you indicated should fix the issue. You can always do a dry-run (using -n
with your abyss-pe
command) to confirm it will change the -n
parameter to that problem DistanceEst
step.
Thank you for your interest in ABySS! Lauren
Thanks @lcoombe, just confirming that explicitly setting N=15
did fix the issue. Thanks again!
Great, thanks for that update! I should have a chance to take a look at this later this week to get a more robust solution.
Hi @NatJWalker-Hale - Just an update that we fixed the issue in #487, and included that fix in the 2.3.10 release
Please report
abyss-pe version
2.3.9
lsb_release -d
Rocky Linux release 8.10 (Green Obsidian)
Assembly error
abyss-pe
command lineIterating over different k and kc
abyss-pe
However the actual error is at the distance estimation step:
It doesn't seem to be related to a failure to map any to contigs etc. as in previous issues.
Right now, I'm testing if specifying
n=10 N=15
to abyss-pe fixes this - it just seems an odd choice to have a default for N that isn't accepted internally? Maybe I missed something in the documentation.