Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manual O2O of uGT menu #177

Open
tmatsush opened this issue Mar 3, 2016 · 12 comments
Open

Manual O2O of uGT menu #177

tmatsush opened this issue Mar 3, 2016 · 12 comments

Comments

@tmatsush
Copy link

tmatsush commented Mar 3, 2016

Ingredients:

  • L1Menu_Collisions2015_25nsStage1_v7_uGT_v3.xml
  • dumpMenu.py from Khristian
  • menuWriter.tgz from Khristian
  • L1Menu_Collisions2015_25nsStage1_v7_uGT.txt from Khristian

Steps:

  1. cmsrel CMSSW_8_0_0_patch2
  2. cd CMSSW_8_0_0_patch2/src
  3. cmsenv
  4. tar xvfz /afs/cern.ch/user/t/tmatsush/public/khristian/menuWriter.tgz
  5. scram b -j4
  6. cp /afs/cern.ch/user/t/tmatsush/public/khristian/dumpMenu.py .
  7. edit dumpMenu.py - change line23 and line40
  8. cmsRun dumpMenu.py
  9. cp /afs/cern.ch/user/t/tmatsush/public/khristian/L1Menu_Collisions2015_25nsStage1_v7_uGT.txt .
  10. rename the L1Menu_Collisions2015_25nsStage1_v7_uGT.txt file to menu_name.txt
  11. edit menu name.txt - change line4 and line11
  12. uploadConditions.py menu name.db [0]

[0] https://twiki.cern.ch/twiki/bin/viewauth/CMS/DropBox

@tmatsush
Copy link
Author

tmatsush commented Mar 3, 2016

L1Menu_Collisions2015_25nsStage1_v7_uGT_v3 has been uploaded to the conddb as
https://cms-conddb.cern.ch/cmsDbBrowser/list/Prod/tags/L1Menu_Collisions2015_25nsStage1_v7_uGT_v3_xml

@tmatsush
Copy link
Author

tmatsush commented Mar 3, 2016

If a menu is not included in the release, the following additional steps are needed;

  1. git cms-addpkg L1Trigger/L1TGlobal
  2. copy menu.xml to L1Trigger/L1TGlobal/data/Luminosity/startup

@tmatsush
Copy link
Author

tmatsush commented Mar 3, 2016

L1Menu_Collisions2015_25nsStage1_v7_uGT_v4 has been uploaded to the conddb as
https://cms-conddb.cern.ch/cmsDbBrowser/list/Prod/tags/L1Menu_Collisions2015_25nsStage1_v7_uGT_v4_xml

@tmatsush
Copy link
Author

tmatsush commented Mar 4, 2016

@tmatsush
Copy link
Author

tmatsush commented Mar 4, 2016

@kkotov
Tried to upload L1Menu_CollisionsHeavyIons2015_v5_uGT but failed with the following message;

[2016-03-04 12:50:54,081] INFO: cms-conddb-prod.cern.ch:
L1Menu_CollisionsHeavyIons2015_v5_uGT: Uploading file
(b63da6c3d142a977677d1465fee1c27c34a3d3d4, size 110814) to the online
backend...
[2016-03-04 12:50:56,725] ERROR: found tag
L1Menu_CollisionsHeavyIons2015_v5_uGT_xml failed to upload. reason:
... Exception: ORA-00001: unique constraint (CMS_CONDITIONS.IOV_PK) violated
[2016-03-04 12:50:56,725] ERROR: tags FAILed to upload :
[u'L1Menu_CollisionsHeavyIons2015_v5_uGT_xml']
[2016-03-04 12:50:56,725] INFO: file log at:
https://cms-conddb-prod.cern.ch/logs/dropBox/getFileLog?fileHash=b63da6c3d142a977677d1465fee1c27c34a3d3d4
[2016-03-04 12:50:56,725] INFO: cms-conddb-prod.cern.ch: Signing out...
uploadAllFiles returned:
L1Menu_CollisionsHeavyIons2015_v5_uGT.db : False

.db and .txt files are in /afs/cern.ch/user/t/tmatsush/public/khristian/test
.xml file is in /afs/cern.ch/user/t/tmatsush/public/L1MenuDev
Any suggestions ?

@tmatsush
Copy link
Author

tmatsush commented Mar 4, 2016

@kkotov
Uploading trial of L1Menu_Collisions2015_5TeV_pp_reference_v5_uGT_v2_mc failed with the same error;

... Exception: ORA-00001: unique constraint (CMS_CONDITIONS.IOV_PK) violated

@kkotov
Copy link

kkotov commented Mar 4, 2016

You have two payloads and two IOVs in your sqlite file. You can either explicitly indicate in the meta file which of the two you are uploading or produce a new sqlite with just one payload and one IOV. I assume you want the later.

@kkotov
Copy link

kkotov commented Mar 4, 2016

btw, there is a simple recipe to create a meta file from scratch with the new uploadConditions.py script: just remove the initial .txt file and run the script. it'll guide you through the process and generate the .txt in the end.

@kkotov
Copy link

kkotov commented Mar 4, 2016

On the other subject, before the L1T O2O is in place we will have to resort to a manual menu upload for the HLT to run. We choose the new tag name: "L1Menu_Commissioning2016v0_hlt" that replaces the old "L1GtTriggerMenu_CRAFT09_hlt" tag. The upload process is no different from uploading the MC tag except that one has to update the "since" field in the meta file to the current run. I made a first upload using L1Menu_Collisions2015_25nsStage1_v7_uGT tag: https://cms-conddb.cern.ch/cmsDbBrowser/list/Prod/tags/L1Menu_Commissioning2016v0_hlt

@tmatsush
Copy link
Author

tmatsush commented Mar 4, 2016

Uploaded L1Menu_CollisionsHeavyIons2015_v5_uGT.xml and L1Menu_Collisions2015_5TeV_pp_reference_v5_uGT_v2_mc.xml as
https://cms-conddb.cern.ch/cmsDbBrowser/list/Prod/tags/L1Menu_CollisionsHeavyIons2015_v5_uGT_xml
and
https://cms-conddb.cern.ch/cmsDbBrowser/list/Prod/tags/L1Menu_Collisions2015_5TeV_pp_reference_v5_uGT_v2_mc_xml , respectively

@tmatsush
Copy link
Author

tmatsush commented Mar 4, 2016

@kkotov
please get L1Menu_Collisions2015_25nsStage1_v7_uGT_v1.xml file from Mike and upload them too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants