APE notes uploading conditions

Change APE:

why? fit will be less efficent if you assigne wrong error on possition bigger ape's at startup is ok to help

First, check what global tag is used in production, one for HLT, one for express, one for prompt. These global tags are always in the alcadb meeting slides. (ppd alcaDB meeting). Click on introduction, see schedule and see first date, then see production global tags.

https://indico.cern.ch/category/3903/

100X_dataRun2_Prompt_v1 100X_dataRun2_Express_v1 100X_dataRun2_HLT_v1

Then we go to the conddb globgal tag browser:

click on global tag and we see all the tags in the global tag.

https://cms-conddb.cern.ch/cmsDbBrowser/index/Prod

As MA expert, we are responsible for CSC and DT position and APEs. THere are 5 tags.

The tags are defined by a record, the record is like a float which is what they contain. Here are the records:

Records you are responsible of: CSCAlignmentErrorExtendedRcd CSCAlignmentRcd DTAlignmentErrorExtendedRcd DTAlignmentRcd GlobalPositionRcd

We now want to check which tag is used. Go in search and search for a record ad you can see the Tag. You can see the last IOV

CSCAlignmentErrorExtended_6x6_hlt 300262

DTAlignmentErrorExtended_6x6_hlt 300262

In HLT promp and express you cannot change history.

Q: snapshot time to infinity, why? A: It is always that way for global tag. In tutorial sent to you. Otherwise CMSSW would ignore it.

https://indico.cern.ch/event/507993/

Ok so, now we need to append IOV. Can only append IOV in future or today. Cannot insert in past. This is the only thing that makes production GT differnet from rereco GTs.

the snapshot time allows you to use whatever IOV you are appending. So you can append IOV and they will be read in the time period you use. What you cannot do is change the tag, you would have to add a new version 2.

Now we know the tag in HLT, lets look at extras:

CSCAlignmentErrorExtended_6x6_express 300262 DTAlignmentErrorExtended_6x6_express 300262

You need to update all tags consistently!

Prompt:

We see tag used in prompt is the same as express. You don't need to change them seperatly. The reason express and HLT have different GTs is to protect HLT, but the tags are the same.

CSCAlignmentErrorExtended_6x6_express 300262 DTAlignmentErrorExtended_6x6_express 300262

So we need to change 4 tags.

Lets se how these are made. We look now at CSCAEE_6x6 and see 5 IOVs. We now need to create xml and upload that. We cannot do this ourselves, we produce the tag and give the tag to be tested.

Go to the terminal:

in CMSSW/src:

1. create xml file
2. convert xml to sqlite (sqlite file a TAG with a single IOV valid from RUN 1)
3. upload TAG in condDB prod
4. Ask Alca to validate TAG
5. Wait for greenlight, append IOV to HLT and Express Tag.

Q: IOV or payload? A: we upload the payload, the IOV is just the interval for that payload. referd to as the same thing kinda.

1. create xml:

go into algihtment/MAA/script

there is a file called OMPUTE_APE

Alignment/MuonAlignmentAlgorithms/scripts/COMPUTE_APE

ConvertXMLtoSQl script for step 2, but we need an xml first.

Look here:

All APEs and GEOM: /afs/cern.ch/cms/CAF/CMSALCA/ALCA_MUONALIGN/www/muonGeometries/

In that folder we have a folder called 2016 2017

look in

Example of APEs: /afs/cern.ch/cms/CAF/CMSALCA/ALCA_MUONALIGN/www/muonGeometries/2017-11_data_ALCARECO_AlignmentWithRun2017BF/APEs_COV_t2_DT_6DOF_2017part1.xml

Open file and see:

6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 http://cms-mual.web.cern.ch/cms-mual/tmp/)

We should see that the RMS is the same for each variable, (we are not seeing this now)

expect:

CSC: 2mm position 1mRad rotaiton

DT:

Create python script that writes down xml with our new values.

What script did you

Then you used upload follow insctrucitons:

https://twiki.cern.ch/twiki/bin/view/CMS/ConditionUploader

Example xml upload for test:

'''xml { "destinationDatabase": "oracle://cms_orcon_prod/CMS_CONDITIONS", "destinationTags": { "DTAlignmentErrorExtended_6x6_2018A_FORTEST": {} }, "inputTag": "DTAlignmentErrorExtendedRcd", "since": null, "userText": "FORTEST: APEs computed for DTs, 2018A 1st alignment: ~2.0 ^-fb" } '''

Change since to latest IOV when appending?

Something in compute_APE is display_ape which will visualize the results makeing sure everything is correct!

/afs/cern.ch/work/l/lpernie/MuonAlign/WD/CMSSW_9_4_0_pre3/src/Alignment/MuonAlignmentAlgorithms/scripts/COMPUTE_APE/DISPLAY_APE.py

Change the first APE and compaire.

Review:

1. make the xml
2. cpmapre with /afs/cern.ch/cms/CAF/CMSALCA/ALCA_MUONALIGN/www/muonGeometries/2017-11_data_ALCARECO_AlignmentWithRun2017BF/APEs_COV_t2_DT_6DOF_2017part1.xml
3. test with DISPLAY_APE.py

Hacking_xml writes a fake geometry.

(this is only for startup)