i know it's a bit late and you probably solved the problem but here is an extra solution

if the output of the job is some kind of a file or a bunch of files that you cp in some directory you can check if all the files are there and then continue:

my $qsub = qx/qsub -pe mpi 5 -t 1:$filecount:2 $bash/; print "$qsub\n"; # check for sge to finish my $r; my $fileoutcount = $filecount + 2; while($r < $fileoutcount){ opendir(DIR, "./out/BLAST/out") || die "$!"; $r = 0; foreach (readdir DIR){ $r++; } closedir DIR; sleep 500; }
this was my solution, running the job on sge by bash script. and now i'm looking for a more direct approach, and SGE module looks pretty ok for now.

baxy


In reply to Re: submitting job to a queue by baxy77bax
in thread submitting job to a queue by mjr1n1

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.