Last Updated on Tuesday, May 23, 2000 at 13:00:32. by Author: Nigel George

Data Tracking Proposal

Table PHOFFLINE.LOG_ENTRIES

ACTION LOG_ID LOG DATE
DV_START 1 12:35-1/1/00
DV_START 2 12:55-1/1/00

George suggested ACTION=OFFLINE_JOB, and then have table with types?

Table PHOFFLINE.LOG_ACTIONS

ACTION DESCRIPTION
DV_START Data validation started

Table PHOFFLINE.RUN_NUMBERS (??, need to point to seq)

This table probably does not make any sense.

LOG_ID RUN_NUMBER SEQ_NUMBER
1 2900 10
2 2900 11

George suggested

FILE_ID RUN_NUMBER SEQ_NUMBER
10 2900 10
15 2900 11

 

Table PHOFFLINE.JOBS

JOBS
1 <LOG_ID>
2

George suggested having extra column here JOB_TYPE?

Table PHOFFLINE.INPUTS

LOG_ID FILE_ID
1 10
2 15

Table PHOFFLINE.FILES

LOG_ID(creation) FILE_ID FILE_TYPE SYSTEM DIRECTORY FILENAME
1 10 RAW_DATA HPSS phobsink/cr00/data PhoRaw002900s010.root
1 11 HIT_DATA RCF_NFS_DISK /phobos/data02/dv_out PhoHit002900s010.root
1 12 OM RCF_NFS_DISK /phobos/data02/dv_out PhoOM002900s010.root
1 13 STD_LOG RCF_NFS_DISK /phobos/data02/dv_out Date20000101_Time154543_Set1.log
1 14 STD_ERR RCF_NFS_DISK /phobos/data02/dv_out Date20000101_Time154543_Set1.err
2 15 RAW_DATA HPSS phobsink/cr00/data PhoRaw002900s011.root

Andrzej mentioned File type could be in a table of types?

Table PHOFFLINE.MODULES

(do we need locations of modules relative to PHATHOME?)

LOG_ID CVS_VERSION_NUM MODULE_CLASS MODULE_NAME PARAM_NAME PARAM_TYPE PARAM_VALUE
1 1.3 TPhInitGeoMod geoinitmod fGeometryName CHAR 42.600
1 1.1 TPhInitFECMod fecinitmod fGetFromDB INT 1
1 1.1 TPhInitFECMod fecinitmod fSensorMapName CHAR
1 1.7 TPhHitProcInitMod hitproc fGetFromDB INT 1
1 1.7 TPhHitProcInitMod hitproc fCalibrationRunNumber INT 2889
1 1.7 TPhHitProcInitMod hitproc fCalibrationFileName CHAR PhoGain_2889s000.root
1 1.7 TPhHitProcInitMod hitproc fPedRunNumber INT 2898
1 1.7 TPhHitProcInitMod hitproc fPedName CHAR ped
1 1.7 TPhHitProcInitMod hitproc fGainName CHAR gain
2 1.1 TPhInitGeoMod geoinitmod fGeometryName CHAR 42.600

Table PHOFFLINE.PHATJOBS

LOG_ID PHAT_VERSION MACRO_NAME (rel PHATHOME)
1 ONLV_1_0_0 sigproc/macros/data_validation.C
2 ONLV_1_0_0 sigproc/macros/data_validation.C

Table PHOFFLINE.DATABASE_KEYS

LOG_ID TYPE INPUT_LOG_ID
1 PED ??
1 GAIN ??
2 PED ??

Table PHOFFLINE.JOB_STATISTICS

LOG_ID SYSTEM_RUN_ON EVENTS_PROCESSED STOP_TIME First Event Number Last Event Number
1 CRS 4000 13:35-1/1/00    
2 CRS 2000 13:55-1/1/00    
           

Maybe combine with run numbers?

Table PHOFFLINE.JOB_QUALITY

This needs lot more thought

(don't know how to tie this to run/seq file as one log_id may have many run/seq input??)

If just one run/seq input

LOG_ID QUALITY AUTO_QUALITY HUMAN_QUALITY Comments
1 GOOD GOOD GOOD
2 UNKNOWN GOOD UNKNOWN
3 UNSURE GOOD UNSURE
4 BAD BAD UNKNOWN

Still little unclear how to handle more thatn one run/seq per job as input?

Better Suggestion by George

LOG_ID CHECKNAME QUALITY
1 DV_AUTO GOOD
1 DV_MANUAL UNSURE
2 DV_AUTO BAD
3 DV_AUTO GOOD
3 DV_MANUAL GOOD
4 DV_AUTO UNSURE

How to handle refinements in quality...