Re^2: hash access with a variable

Printing $gene_name produces what I expect (ENSG0000017672) and I am chomping the input.

The error I get is:

Use of uninitialized value $sequence in concatenation (.) or string at
+ startend-mod3.pl line 48, <FILE1> chunk 1.

Use of uninitialized value $sequence in substr at startend-mod3.pl lin
+e 49, <FILE1> chunk 1
[download]

lines 48 & 49 are:

  print "$sequence\n";
   my $sub_sequence = substr $sequence, ($startres - 11), ($endres - $
+startres + 11);
[download]

Thanks again

Comment on Re^2: hash access with a variable Select or Download Code

Replies are listed 'Best First'.
Re^3: hash access with a variable by AppleFritter (Vicar) on Aug 06, 2014 at 18:16 UTC
This shouldn't be possible. If `$gene_name` contains precisely the string "`ENSG0000017672`", then `$fastas{ENSG0000017672}` and `$fastas{$gene_name}` will both compute to the exact same value. So either `$gene_name` is getting mangled before your hash access, or `$sequence` afterwards. Could you share some more of your code so we can try and figure out where it's going wrong?	[reply]
Re^3: hash access with a variable by graff (Chancellor) on Aug 07, 2014 at 00:01 UTC
When line 48 of your script is this: `print "$sequence\n";` [download] And the warning that perl gives you is "use of uninitialized value $sequence in … string", it means that as of line 48 in your script, no value has ever been assigned to the variable $sequence. If that fact does not agree with your assumptions about the state of things when your script reaches line 48, then your assumptions are wrong, and this is probably related to the fact that when you try to use $sequence as a hash key, you don't get what you expect. You could try forming a minimal, self-contained, runnable (small) script that demonstrates the problem you're having, and if that exercise by itself doesn't reveal the problem for you, post that script in full.	[reply] [d/l]
Re^4: hash access with a variable by Anonymous Monk on Aug 07, 2014 at 00:21 UTC
... no value has ever been assigned to the variable $sequence. No, it means `$sequence` is `undef` at that point, which was probably assigned to it by the statement the OP is having trouble with, `$sequence=$fastas{$gene_name};`. (`$sequence` could very well have held a value before then.) ... when you try to use $sequence as a hash key... They're not, you probably mean `$gene_name`.	[reply] [d/l] [select]
Re^3: hash access with a variable by Monk::Thomas (Friar) on Aug 07, 2014 at 09:33 UTC
The following script `#!/usr/bin/perl use strict; use warnings; use Data::Dumper; my %fastas = ( 'ENSG0000017672' => 'eureka', ); my $gene_name = 'ENSG0000017672'; print 'test1: ', $fastas{ENSG0000017672}, "\n"; print 'test2: ', $fastas{$gene_name}, "\n"; local $Data::Dumper::Useqq = 1; print Data::Dumper->Dump([$gene_name], ['gene_name']);` [download] ... should result in: test1: eureka test2: eureka $gene_name = "ENSG0000017672"; If you get the same result then something else is wrong with your code. If not then something is wrong with your perl. The most reasonable explanation is that $gene_name does not contain what you think it should. If there is a mismatch, then perl will not warn you about that, but silently create a new hash key and return 'undef' as it's value. You can explicitely check if a key exists using 'exists $hash{$key}', e.g.: `use Data::Dumper; [...] if (exists $fastas{$gene_name}) { $sequence = $fastas{$gene_name}; } else { die Data::Dumper->Dump([$gene_name, \%fastas], ['gene_name', 'fastas +']); }` [download] or `use Data::Dumper; [...] exists $fastas{$gene_name} or die Data::Dumper->Dump([$gene_name, \%fastas], ['gene_name', 'fas +tas']); $sequence = $fastas{$gene_name};` [download] Both examples are a bit more complicated then strictly necessary but they will not only tell you something is wrong but also what the current content of the relevant variables is.	[reply] [d/l] [select]