Difference between revisions of "WAC"
| Line 1: | Line 1: | ||
The Weekly Analysis Coordinator (WAC) is a rotating position of 1 week each. The wac is required to perform their functions every morning. | 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==== | ====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. | + | 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==== | ====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. | ||
Revision as of 12:47, 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.
Contents
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.
