Difference between revisions of "WAC"

From Hall A Wiki
Jump to: navigation, search
Line 14: Line 14:
  
 
For every run the database of runs must be updated.  The database structure is as follows.
 
For every run the database of runs must be updated.  The database structure is as follows.
 
+
<blockquote>
 +
<pre>
 
+-------------------+------------+------+-----+-------------------+----------------+
 
+-------------------+------------+------+-----+-------------------+----------------+
 
| Field            | Type      | Null | Key | Default          | Extra          |
 
| Field            | Type      | Null | Key | Default          | Extra          |
Line 31: Line 32:
 
| Production        | tinyint(4) | YES  |    | NULL              |                |  
 
| Production        | tinyint(4) | YES  |    | NULL              |                |  
 
+-------------------+------------+------+-----+-------------------+----------------+
 
+-------------------+------------+------+-----+-------------------+----------------+
 +
</pre>
 +
</blockquote>
  
 
The database can be interacted with using the addWACentry.pl script in the wac directory.   
 
The database can be interacted with using the addWACentry.pl script in the wac directory.   
Line 37: Line 40:
 
====Produce the slug summary====
 
====Produce the slug summary====
  
 +
Once the database is up to date, the slug summary is produced using the summary.pl script in the wac directory.  This will produce the summary root (~/happex3/ROOTfiles/parity09_000X_slug.root) file and the summary text file (http://www.jlab.org/~adaq/prompt_output/).
  
 
====Produce the slug plots====
 
====Produce the slug plots====
 +
 +
Once the slug summary has been

Revision as of 11:56, 13 September 2009

The Weekly Analysis Coordinator (WAC) is a rotating position of 1 week each. The wac is required to perform their functions every morning.


WAC schedule

Jobs of the WAC

Prompt the new runs

Run prompt on all the runs taken since the last wac summary. Do a reprompt if there is any doubt about the initial offline analysis. Look carefully through the output and try to spot problems. For example, Ahmed noticed large outliers in the bcm double differences and this helped us to learn that the dac glitch on the 18 bit ADCs was causing problems.

Update the run database

For every run the database of runs must be updated. The database structure is as follows.

+-------------------+------------+------+-----+-------------------+----------------+
| Field             | Type       | Null | Key | Default           | Extra          |
+-------------------+------------+------+-----+-------------------+----------------+
| WACentriesID      | int(11)    |      | PRI | NULL              | auto_increment | 
| RunInfo_RunNumber | int(11)    | YES  | MUL | NULL              |                | 
| WACname           | tinytext   | YES  |     | NULL              |                | 
| WACEntryTime      | timestamp  | YES  |     | CURRENT_TIMESTAMP |                | 
| WACcomment        | longtext   | YES  |     | NULL              |                | 
| LeftDETeventLo    | int(11)    | YES  |     | NULL              |                | 
| LeftDETeventHi    | int(11)    | YES  |     | NULL              |                | 
| RightDETeventLo   | int(11)    | YES  |     | NULL              |                | 
| RightDETeventHi   | int(11)    | YES  |     | NULL              |                | 
| Slug              | int(11)    | YES  |     | NULL              |                | 
| SlowSign          | tinyint(2) | YES  |     | NULL              |                | 
| Production        | tinyint(4) | YES  |     | NULL              |                | 
+-------------------+------------+------+-----+-------------------+----------------+

The database can be interacted with using the addWACentry.pl script in the wac directory.


Produce the slug summary

Once the database is up to date, the slug summary is produced using the summary.pl script in the wac directory. This will produce the summary root (~/happex3/ROOTfiles/parity09_000X_slug.root) file and the summary text file (http://www.jlab.org/~adaq/prompt_output/).

Produce the slug plots

Once the slug summary has been