Closed emarinier closed 3 years ago
It appears that when running Mash screen on the above test file with the same default values RefSeq Masher uses (mash screen -v 0.01 -p 1 -i 0.9
), Mash screen reports no output. That is, the output file is empty. RefSeq Masher then tries to process this file with the assumption that there will be a certain number of columns in the Mash output, but there are no columns because the file is empty.
I've opened a pull request (#4) that handles empty Mash output by returning None
instead of a dataframe is some places. I've added logic to check for None
dataframes.
I think the winner-takes-all strategy (mash screen -w ...
) was added to Mash screen soon after I wrote this tool and I was using certain options to filter out most of the spurious looking results. Those options could probably be replaced with the -w
flag, but that might require some testing.
Resolved in #4.
I'm getting a crash when I run RefSeq Masher on very few input reads.
I can run Mash on the command line using my data and the Mash sketch provided from RefSeq Masher (the output is the same with or without the -w flag):
However, when I run RefSeq Masher:
I cannot upload my mock reads (tiny.fastq), so I will post them as text here: