Open jolespin opened 11 months ago
With the threshold values from the "ko_list" our group build a little helper script for the formatting and enforcement of KO cut-off thresholds in hmmsearch output files.
We discard the rare (≈1%) secondary (lower score) K assignments so keep an eye out for that. Depending on your use case, this might not be desirable.
Disregarding the dual assignments, the resulting output is functionally identical (>99.999% for our data/settings) to Kofamscan.
I uploaded a code example, which you can modify for your case. I hope this helps.
I'm looking at the code here but not very familiar w/ Ruby:
Here's what
ko_list
looks like:I'm seeing a score threshold but not e-value threshold. Can you elaborate on the scheme used for determining significant hits?