Blame view

help/jobsHelp 1.65 KB
16035364   Benjamin Renard   First commit
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
<h2><img src="js/resources/images/16x16/view_tree.png" style="margin: 0px 10px 0px 0px;"/>WorkSpace Explorer : Jobs Tree</h2>
<h2>1. Starting Job</h2>
<p>
<img src="help/images/jobs_1.png" align="left" style="margin: 0px 15px 0px 0px;" />
The situation often arises when your request is too long to be processed interactively. 
In such a case it is forked into <b><i>a batch mode</i></b>. 
</p>
<p>
"Too long" means 5 sec for Data Mining, Data Downloading
and Plotting in PDF/PS formats. In the case of Interactive Plot Session (PNG Plot output) this time increses
to 500 sec.
</p>
<p> You receive warning message, new
<b><i>job node</i></b> is added to the corresponding folder in the <b><i>Jobs In Progress</i></b> tree of
<b><i>Jobs Tab</i></b> and job information is added into <b><i>Log</i></b> as well.
</p>
<p>
Job name is constructed by adding of the <i>Process ID</i> to the "job" prefix.
In case of an error you may always kill your job by opening contex menu (right click on job name) and selecting <b>Stop/Delete Job</b>
item.
</p>
<p>
You may continue with the other tasks in AMDA, or logout. 
</p>
<br/><br/><br/><br/><br/><br/><br/><br/>
<h2>2. Finished Job</h2>
<p>
<img src="help/images/jobs_2.png" align="right" style="margin: 15px 0px 15px 0px;" />
 
When your job is finished 
you receive a corresponding info message, <b><i>job node</i></b> is moved to <b><i>Finished Jobs / Results</i></b> folder
and <b><i>Log</i></b> information is updated.
</p>
<p>
To access the result right click the job name and select <b>Show Result</b> item from the context menu.
</p>
<p>
Think of regular deleting of the old results (<b>Delete Result</b>) - not to explose your WS...
</p>