RStDGangaGuideGangafourzerzerbetafiveHWJobSubmissionScreenDump

The dialog below is what comes back to the screen when the first job object is created. Some things to note:

  • There is a wanring that comes up: ignore it
  • Messages come asynchronously to the screen. So the INFO messages below appear at any time. Looking through the screen shots, you will see that messages from the first job are appearing in the middle of typing the second job.
In [3]: j.application.exe='/bin/echo'
/afs/cern.ch/sw/ganga/install/slc3_gcc323/4.0.0-beta5/python/Ganga/GPIDev/Base/Proxy.py:232: FutureWarning: hex()/oct() of negative int will return a signed string in Python 2.4 and up
  return '<'+repr(self._impl)+' PROXY at '+hex(id(self))+'>'
 
In [4]: j.application.env={'MESSAGE':'Hello World'}
 
In [5]: j.application.args=['$MESSAGE']
 
In [6]: j.submit()
Ganga.GPIDev.Lib.Job               : INFO     submitting job 1
Ganga.Lib.Localhost                : INFO     job 1 submitted, local pid = 19209
Out[6]: 1
 

Now create the second job by making a copy. Note the asynchronous message about job 1 completing. It came as I was typeing what the backend was for j2. This unfortunately messes up the screen so the () are displaced by the message. Follow the syntax on the example!


In [7]: j2=j.copy()
 
In [8]: j2.backend=LSFGanga.Lib.Localhost                : INFO     Local job 1 completed with exitcode 0
()
 
In [9]: j2.submit()
Ganga.GPIDev.Lib.Job               : INFO     submitting job 2
Ganga.Lib.LSF                      : INFO     LSF: submitting job 2
Ganga.Lib.LSF                      : INFO     using default queue "8nm"
Ganga.Lib.LSF                      : INFO     job 2 submission OK
Out[9]: 1
 

Now prepare the third job for the Grid. Note again the LSF job (number 2) sent an asyncrhonous message as I was typing in the backend for job 3. The screen shot below was collected by leaving for about 10 minutes and then hitting a carriage return a few times. In that time the jobs seem to have completed. This is not necessarily going to happen. The local job will complete quickly, but the LSF and Grid jobs can take any time.


In [10]: j3=j.copy()
 
In [11]: j3.backend=LCGGanga.Lib.LSF                      : INFO     2: LSF job status changed to RUN
()
 
In [12]: j3.submit()
Ganga.GPIDev.Lib.Job               : INFO     submitting job 3
Out[12]: 1
 
In [13]: Ganga.Lib.LCG                      : INFO     job 3 has changed status to Ready
Ganga.Lib.LCG                      : INFO     job 3 has been assigned to ce-egee.bifi.unizar.es:2119/jobmanager-lcgpbs-atlas
Ganga.Lib.LCG                      : INFO     job 3 has changed status to Scheduled
Ganga.Lib.LCG                      : INFO     job 3 has changed status to Running
Ganga.Lib.LSF                      : INFO     2: LSF job status changed to DONEGanga.Lib.LCG                      : INFO     job 3 has changed status to Done (Success)
 


Major updates:
-- RichardStDenis - 19 Oct 2005

%RESPONSIBLE%
%REVIEW%

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2005-10-19 - RichardStDenis
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback