Skip to content

be sure to use same perl interpreter for inner calls #6

@EricDeveaud

Description

@EricDeveaud

Hello,

in some cases installation may be performed with a perl intreperter different for the one avaiable on user path.
(it is our case).

so in order to use the same perl interpreter it would be nice to change the perl calls to $^X that refers to the running perl used by the scripts.

as example in autoAugTrain.pl
change $cmdString = "grep complete ../pasa/$pasaDBname.assemblies.fasta.transdecoder.cds | perl -pe ".'\'s/>(\S+).*/$1\$/\' | perl -pe \'s#\\.#\\\\.#g\' 1> pasa.complete.lst';
to
$cmdString = "grep complete ../pasa/$pasaDBname.assemblies.fasta.transdecoder.cds | $^X -pe ".'\'s/>(\S+).*/$1\$/\' | $^X -pe \'s#\\.#\\\\.#g\' 1> pasa.complete.lst';

this could be applied to the following perl scripts.

autoAug.pl
autoAugPred.pl
autoAugTrain.pl
evalCGP.pl
eval_dualdecomp.pl
eval_multi_gtf.pl
hal2maf_split.pl
optimize_augustus.pl
parseSim4Output.pl
peptides2hints.pl
runAllSim4.pl
writeResultsPage.pl

NB augustify.py and fix_in_frame_stop_codon_genes.py required a manual edition (in our case) in order to set perl interpreter to the correct one.

regards

Eric

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions