Available Alignment Constants for Run II

First of all, one needs to create new tags to the CondDB browser for global usage (ECAL and Muon people). More information about how to create new tags can be found in hands-on session here.

Then, we should announce these new tags to AlCaDB conveners (cms-PPD-conveners-AlCaDB@cernNOSPAMPLEASE.ch) so they can check and give the green-light to upload them to existing GTs of HLT, Express and Prompt workflows.

After conveners signed-off, what needs to be done is to update, appending a new IOV, the 3 payloads for TrackerAlignment, TrackerSurfaceDeformations and APE, to the existing tags that are already included in the production Global Tags. You can check what are the latest existing production Global Tag for each workflow here. For example, the current Global Tag of HLT is 80X_dataRun2_HLT_v12, Express is 80X_dataRun2_Express_v5 and Prompt is 80X_dataRun2_Prompt_v6.

And in order to check inside each of these Global Tags which are the relevant tags for Tracker Alignment you can use the conddb command within a CMSSW release.

 conddb list <name_of_the_GT> | grep <name_of_your_record> 

(The name_of_your_record relevant for Tracker Alignment are TrackerAlignmentRcd, TrackerSurfaceDeformationRcd and TrackerAlignmentErrorExtendedRcd)

This exercised on the 3 Global Tags above will yield you the table and therefore you can see there is a total of 7 tags to be updated.

• For Alignment : TrackerAlignment _PCL_byRun_v0_hlt (replaced TrackerAlignment _2009_v1_hlt), TrackerAlignment _PCL_byRun_v2_express (and copied version of TrackerAlignment _PCL_byRun_v0_express which replaced TrackerAlignment _2009_v1_express and TrackerAlignment _prompt)
• For SurfaceDeformations: TrackerSurafceDeformations _v1_hlt, TrackerSurafceDeformations _v1_express (please notice the typo in the name! it's not an error)
• For APE: TrackerAlignmentExtendedErr _2009_v2_hlt_IOVs and, TrackerAlignmentExtendedErr _2009_v2_express_IOVs

All these 6 tags need to be updated. Let's retrive the sqlite files again from the new tags you just created.

 
conddb_import -c sqlite_file:TrackerSurfaceDeformations_2015-EOY_v1_RunD.db -f frontier://FrontierProd/CMS_CONDITIONS -i TrackerSurfaceDeformations_2015-EOY_v1_RunD -t TrackerSurfaceDeformations_2015-EOY_v1_RunD

conddb_import -c sqlite_file:TrackerAlignmentExtendedErrors_CRUZET2016.db -f frontier://FrontierProd/CMS_CONDITIONS -i TrackerAlignmentExtendedErrors_CRUZET2016 -t TrackerAlignmentExtendedErrors_CRUZET2016 

conddb_import -c sqlite_file:TrackerAlignment_HP_CRUZET2016.db -f frontier://FrontierProd/CMS_CONDITIONS -i TrackerAlignment_HP_CRUZET2016 -t TrackerAlignment_HP_CRUZET2016

Then you should do 3 uploads (1 for each of your sqlite files) using the similar metadata files below for each record.

 uploadConditions.py <name_of_file.db> 

The txt files should be in the same folder as the sqlite files in which you upload and since these tags have already the correct synchronization, you don't need to specify the since (the service will automatically synchronize to the correct version).

The examples of metadata files for each record

• TrackerAlignmentExtendedErrors _CRUZET2016.txt

 
{
    "destinationDatabase": "oracle://cms_orcon_prod/CMS_CONDITIONS",
    "destinationTags": {
        "TrackerAlignmentExtendedErr_2009_v2_express_IOVs": {},
        "TrackerAlignmentExtendedErr_2009_v2_hlt_IOVs": {}
    },
    "inputTag": "TrackerAlignmentExtendedErrors_CRUZET2016",
    "since": null,
    "userText": "APE for 2016 startup: 100um for BPix and FPix, 20um for TIB and TOB, 40um for TID and TEC"
}

• TrackerAlignment _HP_CRUZET2016.txt

 
{
    "destinationDatabase": "oracle://cms_orcon_prod/CMS_CONDITIONS",
    "destinationTags": {
        "TrackerAlignment _PCL_byRun_v2_express": {},
        "TrackerAlignment_PCL_byRun_v0_hlt": {}
    },
    "inputTag": "TrackerAlignment_HP_CRUZET2016",
    "since": null,
    "userText": "Tracker alignment from CRUZET16 data, correcting positions and rotations of the barrel high level structures, starting from IOV 9 of EOY2015"
}

• TrackerSurfaceDeformations _2015-EOY_v1_RunD.txt

 
{
    "destinationDatabase": "oracle://cms_orcon_prod/CMS_CONDITIONS",
    "destinationTags": {
        "TrackerSurafceDeformations_v1_express": {},
        "TrackerSurafceDeformations_v1_hlt": {}
    },
    "inputTag": "TrackerSurfaceDeformations_2015-EOY_v1_RunD",
    "since": null,
    "userText": "Tracker Surface deformation from IOV9 of EOY 2015 alignment"
}

Example of how to import a payload from the DB into a local sqlite file, e.g. to prepare a tag with results of the pseudo-PCL workflow for central validation. The following will retrieve the payload of the IOV starting with 275375, put it into the local sqlite file SiPixelAli_PCL_v0_prompt_r275375.db and set the IOV range from 1 to infinity:

 
conddb_import -c sqlite_file:SiPixelAli_PCL_v0_prompt_r275375.db -f frontier://FrontierPrep/CMS_CONDITIONS -i SiPixelAli_PCL_v0_prompt -t SiPixelAli_PCL_v0_prompt_r275375 -b 275375

echo 'update IOV set SINCE=1 where SINCE=275375;' | sqlite3 SiPixelAli_PCL_v0_prompt_r275375.db

• Our SiPixelAli _PCL can be monitored here as well as the others PCL. You can see there is a plot for SiPixelAli _pcl.
• If you click on the legend at the top right of pclMon page, it will explain the meaning of each color. Basically when it's white, it means no payload was uploaded but when it's green, something has been uploaded (there is also some potential delay which sometimes you might see it's purple, don't panic, it will turn green sometime later but report to AlCa /DB if it's not the case)
• Once you know if the payload has been uploaded or not, you can check the parameters on the offline DQM GUI, for example here DQM link, there is a series of plots for each run (click on Run #). You can see numbers of run from current data taking corresponding to run numbers on pclMon page and you can check DQM for those runs which have new payload uploaded.
• You can also check PV performance for example this link or on-time monitoring from this link.
• You can even double-check new payload uploaded via conddb command line, for example,

 conddb list TrackerAlignment_PCL_byRun_v2_express | grep 2016-08-20

• or from condDB browser, link.

Note 1 see monitoring illustration from Chayanit's slides reported in TkAl meeting on 24 Aug 2016.

Note 2 small tip for circulating the DQM links: click on the small anchor sign on the top right part of the screen with the "link me" text, copying the URL won't work because each user session is accessible only under his/her own GRID certificate.

Tags for data-taking (superseded)

1. This was split from the express tag, see TrackerAlignment_prompt for details

TrackerAlignment_2009_v1_hlt (superseded)

Detailed information at CondDB.

Typically synchronized with TrackerAlignment_2009_v1_express.

since run	object	comment
246978	TrackerAlignment_v1_hltvalidation	CRUZET+CRAFT alignment AlCa/DB HN announcement
248618	TrackerAlignment_v2_hltvalidation	Wrong upload to production, no data taken, reverted back to TrackerAlignment_v1_hltvalidation till validation
248642	TrackerAlignment_v1_hltvalidation	CRUZET+CRAFT alignment AlCa/DB HN announcement
251100	TrackerAlignment_v2_hltvalidation	Module-level alignment of pixel detector only with 0T data of Run2015A AlCa/DB HN announcement
251607	TrackerAlignment_Run2015B_PseudoPCL_v2	pseudo-PCL alignment at 3.8T AlCa/DB HN announcement
256715	TrackerAlignment_for_Run2015D_v0	inconsistent conditions derived from Run2015C data, uploaded by mistake (affected data corrected in prompt reconstruction)
256746	TrackerAlignment_for_Run2015D_v1	conditions derived from Run2015B data
256766	TrackerAlignment_for_Run2015D_v0	inconsistent conditions derived from Run2015C data but centrally validated, therefore till further validation used in HLT. Express used the TrackerAlignment_for_Run2015D_v1 conditions. Difference to express
270856	TrackerAlignment_CRUZET2016	CRUZET alignment for 2016 the alignment constants starting from IOV 260335 of 2015-EOY_v1_RunD
272497	TrackerAlignment_Run2016A_PseudoPCL_v1	Tracker alignment derived from the Pseudo-PCL workflow on run 272011 and conditions in GT 80X_dataRun2_Express_v6 (CRUZET alignment)
276251		updated module level tracker alignment and APE from 2016B AlCa/DB HN announcement
276517	TrackerAlignment_Run2016B_PseudoPCL_276363	pseudo-PCL alignment at 3.8T after magnet cycle on 02.07.2016 AlCa/DB HN announcement
281466	TrackerAlignment_ReReco2016BtoG	Tracker alignment updated from September ReReco campaign Alca/DB HN announcement
271866	TrackerAlignment_EOY16_sm1959	Tracker alignment containing 35 IOVs from EOY16 campaign (after new IOVs redefinition) Alca/DB HN announcement

TrackerAlignment_2009_v1_express (superseded)

Detailed information at CondDB.

since run	object	comment
246978	TrackerAlignment_v1_hltvalidation	CRUZET+CRAFT alignment AlCa/DB HN announcement
248618	TrackerAlignment_v2_hltvalidation	Wrong upload to production, no data taken, reverted back to TrackerAlignment_v1_hltvalidation till validation
248642	TrackerAlignment_v1_hltvalidation	CRUZET+CRAFT alignment AlCa/DB HN announcement
251100	TrackerAlignment_v2_hltvalidation	Module-level alignment of pixel detector only with 0T data of Run2015A
251607	[SWGuideAlignmentConstantsRun2015[#TrackerAlignment_Run2015B_Pseudo][TrackerAlignment_Run2015B_PseudoPCL_v2]]	pseudo-PCL alignment at 3.8T AlCa/DB HN announcement
256715	TrackerAlignment_for_Run2015D_v0	inconsistent conditions derived from Run2015C data, uploaded by mistake (affected data corrected in prompt reconstruction)
256746	TrackerAlignment_for_Run2015D_v1	conditions derived from Run2015B data
257826	TrackerAlignment_Run2015D_PseudoPCL_v0	pseudo-PCL alignment at 3.8T with early Run2015D data AlCa/DB HN announcement
262922	TrackerAlignment_ppRef2015_hltvalidation	pseudo-PCL alignment at 3.8T with early Run2015E data AlCa/DB HN announcement
270856	TrackerAlignment_CRUZET2016	CRUZET 2016 alignment AlCa/DB HN announcement
272497	TrackerAlignment_Run2016A_PseudoPCL_v1	Tracker alignment derived from the Pseudo-PCL AlCa/DB HN announcement

TrackerAlignment_prompt (superseded)

Detailed information at CondDB.

This is a new tag that was created by merging the content of the old TrackerAlignment_2009_v1_prompt, which was in use (apparently) up to run 197571, and then inserting all the IOVs from TrackerAlignment_2009_v1_express that were included recently in all the express and prompt GTs.

It is included in the GT for Prompt as of 74X_dataRun2_Prompt_v2.

since run	object	comment
251607	TrackerAlignment_Run2015B_Pseudo	pseudo-PCL alignment at 3.8T AlCa/DB HN announcement
256709	TrackerAlignment_for_Run2015D_v1	conditions derived from Run2015B data (the payload with the younger time stamp)
257826	TrackerAlignment_Run2015D_PseudoPCL_v0	pseudo-PCL alignment at 3.8T with early Run2015D data AlCa/DB HN announcement
262922	TrackerAlignment_ppRef2015_hltvalidation	pseudo-PCL alignment at 3.8T with early Run2015E data AlCa/DB HN announcement
270385	TrackerAlignment_CRUZET2016	CRUZET 2016 alignment AlCa/DB HN announcement
272214	TrackerAlignment_Run2016A_PseudoPCL_v1	Tracker alignment derived from the Pseudo-PCL AlCa/DB HN announcement