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.

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).

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:

How to monitor PCL alignment workflows

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,

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.

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

Updates the pixel module-level alignment (positions and rotations), leading to an improved local resolution and using the collision data of the runs 295209+295210 as well as CRAFT (private rereco) AlCa/DB HN announcement

Updates the pixel module-level alignment (positions and rotations), leading to an improved local resolution and using the collision data of the runs 295209+295210 as well as CRAFT (private rereco) AlCa/DB HN announcement

TrackerAlignment _PCL_byRun_v2_prompt

Note we have currently (24.07.2017) different tags in prompt and express to allow faster reaction to changing conditions during the commissioning period. This is a simply copied version of tag TrackerAlignment_PCL_byRun_v2_express until Run 299228.

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

TrackerSurafceDeformations_v1_prompt

Note we have currently (24.07.2017) different tags in prompt and express to allow faster reaction to changing conditions during the commissioning period. This is a simply copied version of tag TrackerSurafceDeformations_v1_express until Run 298757.

enlarged APE for CRUZET17 data taking with only strips detector: 100mum for BPIX and FPIX, 20mum for TIB and TOB, 40mum for TID and TEC. Note that pixel is still the phase0 format. It will be updated to phase1 once interdependency tests are done with the first, strips-only CRUZET17 data. AlCa/DB HN announcement

enlarged APE for CRUZET17 data taking with only strips detector: 100mum for BPIX and FPIX, 20mum for TIB and TOB, 40mum for TID and TEC. Note that pixel is still the phase0 format. It will be updated to phase1 once interdependency tests are done with the first, strips-only CRUZET17 data. AlCa/DB HN announcement

TrackerAlignmentExtendedErr_2009_v2_prompt_IOVs

Note we have currently (24.07.2017) different tags in prompt and express to allow faster reaction to changing conditions during the commissioning period. This is a simply copied version of tag TrackerAlignmentExtendedErr_2009_v2_express_IOVs until Run 298759.