[interhelp #36687] PIRSF HMMER3 raw match parser is storing the wrong evalue

thiagomaframg / interproscan

Automatically exported from code.google.com/p/interproscan

0 stars 0 forks source link

[interhelp #36687] PIRSF HMMER3 raw match parser is storing the wrong evalue #60

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

InterProScan version 5.9-50.0 is affected by this.

The PIRSF matches itself are OK and valid, but the Evalue shown in the result 
files (TSV, GFF3 or XML) is incorrect.

It doesn't matter if you have the match lookup service switched on or off.

What would be the expected TSV output?

P02939  78  PIRSF   PIRSF002855     1   78  1.5E-41

What do you see instead?

P02939  78      PIRSF   PIRSF002855             1       78      79.0

Original issue reported on code.google.com by Maxim.Sc...@gmail.com on 12 Feb 2015 at 10:38

GoogleCodeExporter commented 8 years ago

Work has started to fix this issue, which will lead into a new InterProScan 5 
release, potentially 5.10-50.0.

Original comment by Maxim.Sc...@gmail.com on 12 Feb 2015 at 10:40

GoogleCodeExporter commented 8 years ago

Original comment by Maxim.Sc...@gmail.com on 12 Feb 2015 at 11:56

Changed title: [interhelp #36687] PIRSF HMMER3 raw match parser is storing the wrong evalue

GoogleCodeExporter commented 8 years ago

This issue has been fixed in the InterProScan 5.10-50.0 release. To benefit 
from the fix, please run with the match lookup service turned off (e.g. use the 
-dp option). 

The latest version of the match lookup service to use with this new release is 
still 5.9-50.0 (which contains this issue). Therefore please be aware that any 
PIRSF 3.01 evalues returned by the 5.9-50.0 lookup service will continue to be 
incorrect.

Original comment by Mr.Matth...@gmail.com on 20 Feb 2015 at 3:00

GoogleCodeExporter commented 8 years ago

Original comment by Maxim.Sc...@gmail.com on 27 Mar 2015 at 12:53

Changed state: Fixed