triggerDefinition and triggerTheshold Offline Database Upload Information, Years 2013-2016
Originally I was going to make a separate blog entry for each year, but for the sake of convenience and compactness, I will put the relevant information for all years in this entry. Details regarding the migration from the online database to the offline data base can be found in my previous blog entry.
The offline database for both triggerDefinition and triggerThreshold was uploaded on a run by run basis. The runs used were ones with a production level trigger setup name, which also satisfied get_file_list.pl with tpx=1,emc=1,eemc=1,sanity=1.
Attached to this blog post are the list of runs along with their associated beginTime, which is used to read from the offline database.
The trigger setup names used, along with the number of runs, for each run year is as follows: (note: removed production level TrgSetupNames with no runs passing conditions used in get_file_list.pl)
Run Year | TrgSetupName | # of Runs |
2013 | pp500_production_2013 pp500_production_2013a |
1911 |
2014 |
AuAu_200_production_2014
AuAu_200_production_low_2014 AuAu_200_production_mid_2014 AuAu_200_production_high_2014 AuHe3_production_2014 |
4212 |
2015 | production_pAl200_2015 production_pAl200_2015_lowlumi production_pp200long2_2015 production_pp200long3_2015 production_pp200long_2015 production_pp200trans_2015 |
2665 |
2016 | AuAu200_production2_2016 AuAu200_production2_2016MXQds9 AuAu200_production2_2016_MXQds7 AuAu_200_production_2016 dAu200_production_2016 dAu20_production_2016 dAu39_production_2016 dAu62_production_2016 |
2780 |
- dbnemes's blog
- Login or register to post comments