CRS Farm Status Window

The window is divided into two sections: The top for monitoring the specific nodes (i.e computer, with dual processor). The bottom for monitoring each job currently running or queued for the farm.

Note: This window does not automatically refresh itself, therefore to see the current status hit the Refresh button.

Description of Top Window:

• Node: The name of the machines connected to the CRS farm
• Status: The current status of the node.
• Job Limit: The maximum number of jobs that can run of the node. As each machine is a duel processor, it can run two jobs at once. The job limit is usually 3, because for efficiency reasons, one job is staged sitting ready to go when either of the processors is freed up.
• Running Jobs: This shows the number of jobs "running" on the node. If 3, then 2 are processing and 1 is waiting.

Description of Bottom Window

• Subjob ID: Every job submitted to crs, is given a job id, this is it.
• Status: This is the current stage that the job is at. General jobs go through the following stages
                  constructing->staging -> queuing -> transferring in ->running -> cleaning mode
     Constructing/Staging: Everything necessary to run the job, is assembled
     Queuing: Waiting for a node to become available
     Transferring in: All the files etc necessary to run the job, are transferred onto the local disk/processor of the particular farm computer.
     Running: The job is currently running on that node
     Cleaning node: The job is finished, and the files are transferred to where they should go, and the node is cleaned so the next job can run fresh.
• Node: The name of the node on which the job is running
• Job File: The name of the "job file" that was submitted to the farm. The job file contains all the information that is used by the batch system to construct the job on the crs node. For data validation it is a file that has the following form DV######s###_DateYYYYMMDD_TimeHHMMSS_Set1.jf