Question: BLAST Score vs E-value in BioPython
0
gravatar for dlawre14
4.6 years ago by
dlawre1430
United States
dlawre1430 wrote:

When I use the following in BioPython

    result.alignments[0].hsps[0].score

What value is this? Is it the alignment score based on gap and mismatch penalties or the e-value? When using the above, is a larger number or a smaller number better?

blast biopython • 1.8k views
ADD COMMENTlink modified 4.6 years ago by DG7.1k • written 4.6 years ago by dlawre1430

"better" implies you're trying to do something with the values.

The values are defined by the BLAST method, and are not specific to BioPython. Research what BLAST does and you'll see what each value means.

ADD REPLYlink written 4.6 years ago by karl.stamm3.6k

I know from the blast side the difference between BLAST score and e-value, I was unclear on my call which value BioPython is calling hsps.score, is that equivalent to BLAST score? I am doing a machine learning project on protein function prediction and one of my methods is to align the subject against a database of proteins and then return predicted functionality as the function of the closest aligned protein in the database.

ADD REPLYlink written 4.6 years ago by dlawre1430
2
gravatar for DG
4.6 years ago by
DG7.1k
DG7.1k wrote:

The documentation for BioPython has this information well defined. For HSPs: http://biopython.org/DIST/docs/api/Bio.Blast.Record.HSP-class.html hsp.score is the score, hsp.expect is the expect value.

As karl.stamm pointed out in his comments, deciding which to use and how to interpret it depends on what you are trying to do and these are well defined by BLAST as to what they mean.

ADD COMMENTlink modified 6 months ago by RamRS27k • written 4.6 years ago by DG7.1k

Ah thank you. I read the documentation and must have missed the hsp.expect choice for hsp records. Boy do I feel dumb.

ADD REPLYlink written 4.6 years ago by dlawre1430
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1418 users visited in the last hour