[Bioperl-l] Mysql columns and Blast evalues
skirov at utk.edu
Wed Mar 9 22:25:46 EST 2005
Try to store it as a varchar, it will not make much difference.
You printf is OK I guess, I guess either $blast or $i is actually undef
and undef/anything (except undef or 0) is 0. You can use CGI::Debug (for
example use CGI::Debug (report=>'everything', on=>'anything'); to trace
the vars in a CGI script. There are other ways to debug CGI script,
including command line -d (try searching google for debug CGI).
Hope this helps.
>Not sure you already discussed this but I was not able to find anything by using google...
>I am trying to store parsed Blast e-values (parsed with SearchIO) into mysql tables (MyISAM), the column in question is double(11,2)... would it be ok for really small e-values (eg: 1e-197) ? I am using MySQL 4.1.10 and only see "0" (zero) in the tables... when I set the column to double(11,3) then can see smaller evalues (like the above mentioned) ...
>Another problem is to print in the screen those evalues, actually we are using CGI and sprintf like this:
>$e_value = sprintf ( "%0.1e", $blast_hits->[$i]/1e200 );
>But can only see values as "0.0e+00" in the screen...
>Any tips, would be greatly appreciated.
>Kindest regards, Alberto
>Bioperl-l mailing list
>Bioperl-l at portal.open-bio.org
More information about the Bioperl-l