A few further points to note:-

• Use the three-argument form of open with lexical file handles and check for success, giving the o/s error on failure, e.g.

  open my $uniqueFH, '<', $uniqueFile
     or die "open: < $uniqueFile: $!\n";
  [download]

• You can do your chomping in one fell swoop

  chomp( my @data_in = <$uniqueFH> );
  [download]

  rather than piecemeal.

• You could consider using a hash slice rather than looping although this might not be practicable with very large data sets

  my %strSpec_protein_hash;
  @strSpec_protein_hash{ @data_in } =
     @goodProteins_hash{ @data_in };
  [download]

• I wonder if you have a cut'n'paste error in your post, my %strSpec; versus $strSpec_protein_hash{$id} = $seq;

I hope these points are helpful.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.