Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to define the cutoff values in the taxonomy file? #6

Closed
TurbulentCupcake opened this issue Jun 12, 2018 · 1 comment
Closed

How to define the cutoff values in the taxonomy file? #6

TurbulentCupcake opened this issue Jun 12, 2018 · 1 comment
Labels

Comments

@TurbulentCupcake
Copy link

I'm kinda confused about how the cutoffs must be defined in the taxonomy files. What do the numbers on either side of the double colons mean?

@jfmrod
Copy link
Owner

jfmrod commented Jul 2, 2018

Hi,
The numbers on the taxonomy files are identity cutoffs and a scaling parameter. For example:
#cutoff: 0.00:0.08 0.70:0.35 0.70:0.35 0.70:0.35 0.80:0.25 0.92:0.08 0.95:0.05
Each pair of numbers (separated by the colon ":") corresponds to a different taxonomic level.
In the species level: 0.95:0.05, indicates that below 0.95 (95% identity) the confidence (based on identity) assignment will be 0.0. The confidence above 0.95 is given by: confidence(id)=(id - 0.95 + 0.02)/0.05. Where 0.05 is the scaling parameter. So for example if the identity for the top hit was 96%, the identity confidence would be: confidence(0.96)= (0.96-0.95+0.02)/0.05 = 0.6 . Values above 1.0 or below 0.0 get clamped to 1.0 or 0.0, respectively. Please note that the final confidence (combined) is the minimum of the identity confidence and the score confidence. In simple terms, the score confidence measures the difference in score between the top hit and the second best hits.

@jfmrod jfmrod added the question label Jul 2, 2018
@jfmrod jfmrod closed this as completed Nov 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants