next up previous contents
Next: Tagging, Freezing, and Production Up: Off-line Databases Previous: Off-line database

Combining Off-line and Mapmanager databases

Due to the nature of the ``cooking'' process, it is sometimes necessary for the off-line and Mapmanager databases to share information. Most of the time the Mapmanager database requires information from the off-line database. The framework for some of this exchange is written as UpdateCalibMaps.pl with the usage:


Usage:UpdateCalibMaps.pl -h-P0x# -d<dbdir> [-t#] [-f<string>]
		[-pdu<string>] 
 
		 -h 				Print this help message.
		-d<dbdir> Path to database directory.
		-f<string> Intermediate file name needed for put_map
						command (default  = alibaba).
		-pdu<string> PDU wire file including path to use for
						DC_STATUS. (must be used if -P0x4 is
						specified).
		-t# 				Run number to use as time stamp for DC_STATUS.
		-P0x# 				Choose maps to update.
				0x1 		Update Geometry map with x,y, and z beam positions.
				0x2 		Update Sync map with number of synchronization bits.
				0x4 		Update DC_STATUS map from pdu wire file. 

For the -P0x1 and -P0x2 options UpdateCalibMaps.pl retrieves values from the off-line database for each run. With the -P0x1 option, the vertex information, obtained by running trk_mon is placed into the GEOMETRY.map. The read out controller synchronization information, obtained by running sync, is stored in the SYNC.map when the -P0x2 option is specified. For both of these processing bits the -d option must also be specified to alert plot_strip_chart.pl to the location of the off-line database. The information for each run is then stored in the respective Map database.

The -P0x4 option, used for updating the DC_STATUS.map, is performed in a different manner than the other two processing options. In order to update this map the script does not access the off-line database but rather a text file. Using the -pdu<string> option, the user identifies the specific pdu wire file to use. The -t# should also be specified allowing the user to control where the information is placed in the map. Only one entry is needed for each set of run conditions since the health of the drift chambers should not change dramatically in the middle of a run.


next up previous contents
Next: Tagging, Freezing, and Production Up: Off-line Databases Previous: Off-line database
Elton Smith
10/8/1999