Is the bug primarily related to salmon (bulk mode) or alevin (single-cell mode)?
Salmon (bulk mode)
Describe the bug
For one of our 41 samples, salmon fails (quits, without any substantial output) when using the orphan recovery option (where Salmon attempts to try harder to pair up read alignments when one of the reads in a read pair fails to map properly). Given that it's only related to the orphan recovery option, and only one sample out of 41, I don't expect it'll affect our results in any substantial way, but I'm reporting this bug just in case it exposes other software issues that are more concerning.
To Reproduce
Steps and data to reproduce the behavior:
Which version of salmon was used?
v1.10.0 (the latest release that had a compiled executable)
How was salmon installed (compiled, downloaded executable, through bioconda)?
Is the bug primarily related to salmon (bulk mode) or alevin (single-cell mode)?
Salmon (bulk mode)
Describe the bug
For one of our 41 samples, salmon fails (quits, without any substantial output) when using the orphan recovery option (where Salmon attempts to try harder to pair up read alignments when one of the reads in a read pair fails to map properly). Given that it's only related to the orphan recovery option, and only one sample out of 41, I don't expect it'll affect our results in any substantial way, but I'm reporting this bug just in case it exposes other software issues that are more concerning.
To Reproduce Steps and data to reproduce the behavior:
Working:
Working produced the following file structure:
Not working:
Not working produced the following file structure:
The file
mapped/salmon_03_withRecover/logs/salmon_quant.log
has nothing inside it.Expected behavior
Properly-mapped reads, as demonstrated by the following metadata:
Screenshots
Program output from a failed process (with the
--recoverOrphans
option):Desktop (please complete the following information):