Before you start optimizing your code I recommend writing a test suite that verifies the current behaviour. That way when you introduce errors during optimization they will be easier to spot. You have done the manual verification, put that in a test script.
For example you could do this (and leave alpha_index as it is):
#!c:\perl\bin\perl
use strict;
use warnings;
use Math::BigInt;
use Data::Dumper;
use Test::More qw(no_plan);
my %index_val = ( A => 2,
C => 3,
D => 4,
N => 2,
M => 2,
T => 1,
G => 4);
my $sequence = "ACTGACN";
my $distance_index = 3;
my $window = 2;
my $arr_ref = alpha_index({ sequence => $sequence,
distance => $distance_index,
aa_index => \%index_val,
window_size => $window });
ok($arr_ref);
diag("Testing alpha_index with window: $window, distance: $distance_in
+dex, sequence: $sequence");
is(ref($arr_ref),'ARRAY','alpha index returned an array');
is(@$arr_ref,7,'7 entries are in the array');
is($arr_ref->[0]{A},2.51025682971601);
Take a look at
Test::More for other ideas on what you can test.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.