view release on metacpan or  search on metacpan

lib/Astro/Catalog/IO/TST.pm  view on Meta::CPAN

        if (exists $star->{gsc}) {
            $construct{gsc} = ( $star->{gsc} eq '+' ? "TRUE" : "FALSE");
        }
        elsif ($params{gsc}) {
            $construct{gsc} = "TRUE";
        }

        # Magnitudes <- anything that ends in mag
        # Assdume filter is in X_mag
        # If no prefix assume R (yeah right) - we do not know the
        # source of the catalog at this point so can not even guess
        $construct{magnitudes} = {};
        $construct{magerr} = {};
        for my $key (keys %$star) {
            print "LOOPING KEY = $key\n" if $DEBUG;

            # Un-Goldy hack number #5 for the SuperCOSMOS catalog, for some
            # bloody stupid reason they've decided to label their magntitudes
            # B_J, R_1, R_2 and I. God help me, if I ever find the guy responsible
            # for this stupid idea. For now lets munge these here and cross our
            # fingers.

lib/Astro/Catalog/Query/SuperCOSMOS.pm  view on Meta::CPAN

        $col = new Astro::FluxColor(
                upper => 'BJ',
                lower => "I",
                quantity => new Number::Uncertainty(
                    Value => $cval,
                    Error => $err ) );
        push @cols, $col;

        # Push the data back into the star object, overwriting ther previous
        # values we got from the initial Skycat query. This isn't a great
        # solution, but it wasn't easy in version 3 syntax either, so I guess
        # your milage may vary.

        my $fluxes = new Astro::Fluxes( @mags, @cols );
        $star->fluxes( $fluxes, 1 );  # the 1 means overwrite the previous values

        # push it onto the stack
        $stars[$i] = $star if defined $star;
    }

    $catalog->allstars( @stars );