First of all thanks for an amazing set of tools! They really make genome assembly much more fun.
I have noticed that miniasm does not handle it as I would expect when I mistakenly run it with a filename that does not match a file (I know I should just provide the right name but typos happen).
When I run:
"miniasm -f nanopore.fastq nonexisting.paf > miniasm_assembly.gfa"
I get
"[M::main] ===> Step 1: reading read mappings <===
Segmentation fault (core dumped)"
I would have expected something like "nonexisting.paf: No such file or directory"
If I on the other hand run
"miniasm -f nonexisting.fastq reads.paf > miniasm_assembly.gfa"
It seems as if miniasm does not check if the file exists before it starts running. Here again it would be nice to get something like "nonexisting.fastq: No such file or directory".
Hi
First of all thanks for an amazing set of tools! They really make genome assembly much more fun.
I have noticed that miniasm does not handle it as I would expect when I mistakenly run it with a filename that does not match a file (I know I should just provide the right name but typos happen). When I run: "miniasm -f nanopore.fastq nonexisting.paf > miniasm_assembly.gfa" I get "[M::main] ===> Step 1: reading read mappings <=== Segmentation fault (core dumped)" I would have expected something like "nonexisting.paf: No such file or directory" If I on the other hand run "miniasm -f nonexisting.fastq reads.paf > miniasm_assembly.gfa" It seems as if miniasm does not check if the file exists before it starts running. Here again it would be nice to get something like "nonexisting.fastq: No such file or directory".
Best regards Rasmus Kirkegaard