IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Jun 12, 2026, 2:47:49 PM (7 weeks ago)
Author:
eugene
Message:

convert the IPC::Cmd run calls to ps_run to handle inconsistent behavior between IPC:Cmd versions pre- and post-0.40

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/eam_branches/ipp-pstamp-20260421/pstamp/scripts/detect_query_read

    r41440 r43052  
    2020use Math::Trig;
    2121use Data::Dumper;
    22 use IPC::Cmd 0.36 qw( can_run run );
     22use IPC::Cmd 0.36 qw( can_run );
     23use PS::IPP::Config qw( :standard ps_run );
    2324
    2425use constant EXTNAME => 'MOPS_DETECTABILITY_QUERY'; # Extension name for table
     
    195196            my $cmd = "$regtool -processedexp -dbname $dbname -exp_name $colData{FPA_ID}[$i]";
    196197            my ( $success, $error_code, $full_buf, $stdout_buf, $stderr_buf ) =
    197                 run(command => $cmd, verbose => 0);
     198                ps_run(command => $cmd, verbose => 0);
    198199            unless ($success) {
    199200                # This is a problem, because I'm not sure how we handle a failure to read something.
     
    267268        }
    268269        my ( $success, $error_code, $full_buf, $stdout_buf, $stderr_buf ) =
    269             run(command => $cmd, verbose => 1);
     270            ps_run(command => $cmd, verbose => 1);
    270271        unless ($success) {
    271272            # This is a problem, because I'm not sure how we handle a failure to read something.
Note: See TracChangeset for help on using the changeset viewer.