comment on

I'm sure there are more elegant and probably better solutions, but this is one way to do it.

#!/usr/bin/env perl
use strict;
use warnings;

my %fields;
my $header = <DATA>;
while (<DATA>) {
    chomp;
    next if /\A\s*\Z/;
    my ($f1, $f2) = split;
    push @{ $fields{$f1} }, $f2;
}

for my $k (keys %fields) {
    my ($one, $three) = (0, 0); # if either of these remain zero, ID i
+s invalid

    for my $values ( @{ $fields{$k} } ) {
        ++$one   if ( $values == 1 );
        ++$three if ( $values == 3 );
    }

    print "invalid ID: $k\n" unless $one * $three;
}

__DATA__
field1 field2
3-2000/7.48 1
3-2000/7.48 2
3-2000/7.48 2
3-2000/7.48 2
3-2000/7.48 2
3-2000/7.48 2
3-2000/7.48 2
3-2000/7.48 3

4-0000/8.40 2
4-0000/8.40 2
4-0000/8.40 2
4-0000/8.40 2
4-0000/8.40 2
4-0000/8.40 2
4-0000/8.40 3
[download]

In reply to Re: validating file with perl by farang
in thread validating file with perl by mmittiga17

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks