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

CMS: CMSSW versions & GT for pPb and pp ref data & MC #144

Closed
katilp opened this issue Sep 6, 2022 · 2 comments
Closed

CMS: CMSSW versions & GT for pPb and pp ref data & MC #144

katilp opened this issue Sep 6, 2022 · 2 comments

Comments

@katilp
Copy link
Member

katilp commented Sep 6, 2022

From #129

Finding the information

CMSSW version:

Identifying the version to be used in the analysis:

Question: would it make sense to provide a container with the CmsHI fork on top of a CMSSW version?

GT:

Look at the HIForest production configs (pPb, pp, PbPb, MC or DATA) in the respective branches under

2013 pPb 5.02 TeV data

(datasets see #136)

CMSSW for RECO production:

  • Prompt: cmsdas gives 5 versions (?):
    CMSSW_5_3_8
    CMSSW_5_3_8_HI
    CMSSW_5_3_8_HI_patch2
    CMSSW_5_3_8_patch1
    CMSSW_5_3_8_patch2
    
  • Rereco: cmsdas: CMSSW_5_3_8_HI_patch2

CMSSW for HIForest:

GT

2013 pp 2.76 TeV ref

(datasets see #140)

CMSSW for RECO production:

  • Prompt: cmsdas: CMSSW_5_3_8_patch3
  • Skims: cmsdas: CMSSW_5_3_8_patch3

CMSSW for HIForest

GT

2015 pp 5.02 TeV ref

(datasets see #139)

CMSSW for RECO production:

  • Prompt: cmsdas: shows two CMSSW_7_5_5_patch3, CMSSW_7_5_5_patch4

CMSSW for HIForest

GT

HI MC

(datasets in #138 including 2.76TeV PbPb and 5.02TeV pPb)

CMSSW for GEN-SIM-RECO production

  • ranging from CMSSW_5_3_8_patch3 to CMSSW_5_3_27

CMSSW for HIForest

GT

@katilp katilp changed the title CMS: CMSSW versions for pPb and pp ref data CMS: CMSSW versions & GT for pPb and pp ref data & MC Sep 8, 2022
@katilp
Copy link
Member Author

katilp commented May 18, 2023

Check the difference between STARTHI_V27 and STARTHI_V28

  • On lxplus, go to slc6 singularity with cmssw-el6
  • Create or use existing CMSSW area, e.g. CMSSW_5_3_32/src, exact version does not matter
  • Get the condition db listings with:
    cmscond_tagtree_list -c frontier://FrontierProd/CMS_COND_31X_GLOBALTAG -T STARTHI53_V27 > STARTHI53_V27.list
    cmscond_tagtree_list -c frontier://FrontierProd/CMS_COND_31X_GLOBALTAG -T STARTHI53_V28 > STARTHI53_V28.list
    
  • The dbs are in a different order, so sort them and compare with:
    $ diff <(sort STARTHI53_V27.list) <(sort STARTHI53_V28.list)
    5c5
    <    leafnode:BeamSpotObjects   parent:Calibration   tag:RealisticHICollisions2013_START53_V9_v1_mc record:BeamSpotObjectsRcd object:BeamSpotObjects label:None pfn:frontier://FrontierProd/CMS_COND_31X_BEAMSPOT
    ---
    >    leafnode:BeamSpotObjects   parent:Calibration   tag:Realistic2p76TeVCollisions2013_START53_V9_v1_mc record:BeamSpotObjectsRcd object:BeamSpotObjects label:None pfn:frontier://FrontierProd/CMS_COND_31X_BEAMSPOT
    

So the difference is in the beamspot.

Checking the actual values from the text dump:

sqlite3 RealisticHICollisions2013_START53_V9_v1_mc.db .dump > RealisticHICollisions2013_START53_V9_v1_mc.txt
sqlite3 Realistic2p76TeVCollisions2013_START53_V9_v1_mc.db .dump > Realistic2p76TeVCollisions2013_START53_V9_v1_mc.txt
$ diff RealisticHICollisions2013_START53_V9_v1_mc.txt Realistic2p76TeVCollisions2013_START53_V9_v1_mc.txt
[...]
83c83
< INSERT INTO "ORA_C_BEAMSPOTOBJECTS" VALUES(0,0.0050005,0.0,0.00499228,0.0,0.0,-2.8373e-06,9.11533e-06,0.0,0.0,0.243801,0.392822,0.462779,8.90928,2);
---
> INSERT INTO "ORA_C_BEAMSPOTOBJECTS" VALUES(0,0.00959171,0.0,0.00955925,0.0,0.0,-9.59487e-06,-9.86836e-06,0.0,0.0,0.244065,0.392906,0.42742,7.91168,2);
85,91c85,91
< INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,0,3.4736e-09,1.47792e-11,0.0,0.0,0.0,0.0,0.0);
< INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,1,1.47792e-11,3.48422e-09,0.0,0.0,0.0,0.0,0.0);
< INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,2,0.0,0.0,0.0119739,0.0,0.0,0.0,0.0);
< INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,3,0.0,0.0,0.0,0.00598691,0.0,0.0,0.0);
< INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,4,0.0,0.0,0.0,0.0,4.40224e-11,3.4355e-13,0.0);
< INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,5,0.0,0.0,0.0,0.0,3.4355e-13,4.35842e-11,0.0);
< INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,6,0.0,0.0,0.0,0.0,0.0,0.0,3.1986e-09);
---
> INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,0,3.80569e-09,6.77499e-12,0.0,0.0,0.0,0.0,0.0);
> INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,1,6.77499e-12,3.78769e-09,0.0,0.0,0.0,0.0,0.0);
> INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,2,0.0,0.0,0.00242419,0.0,0.0,0.0,0.0);
> INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,3,0.0,0.0,0.0,0.00121209,0.0,0.0,0.0);
> INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,4,0.0,0.0,0.0,0.0,6.45014e-11,-7.03752e-14,0.0);
> INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,5,0.0,0.0,0.0,0.0,-7.03752e-14,6.44679e-11,0.0);
> INSERT INTO "ORA_C_BEAMSPOTOBJE_A0" VALUES(0,6,0.0,0.0,0.0,0.0,0.0,0.0,3.8004e-09);

@katilp
Copy link
Member Author

katilp commented Jun 6, 2023

From the discussion on June 6, 2023:

  • V27 and V28 correspond to 2.76 and 5.02 TeV, take both
  • in general, always keep to the GT of the production unless otherwise stated

For differences btw V25/V27 and V26/V28 see https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideFrontierConditions?rev=609#HI_Simulation_AN4
image

Check the actual difference (instructions)

Singularity> diff <(sort STARTHI53_V27.list) <(sort STARTHI53_V25.list)
209c209
<    leafnode:L1MuCSCTFConfiguration   parent:Calibration   tag:L1MuCSCTFConfiguration_10412_mc record:L1MuCSCTFConfigurationRcd object:L1MuCSCTFConfiguration label:None pfn:frontier://FrontierProd/CMS_COND_31X_L1T
---
>    leafnode:L1MuCSCTFConfiguration   parent:Calibration   tag:L1MuCSCTFConfiguration_90511_mc record:L1MuCSCTFConfigurationRcd object:L1MuCSCTFConfiguration label:None pfn:frontier://FrontierProd/CMS_COND_31X_L1T
218c218
<    leafnode:L1MuGMTParameters   parent:Calibration   tag:L1MuGMTParameters_gmt2012_0_EarlyRPC_mc record:L1MuGMTParametersRcd object:L1MuGMTParameters label:None pfn:frontier://FrontierProd/CMS_COND_31X_L1T
---
>    leafnode:L1MuGMTParameters   parent:Calibration   tag:L1MuGMTParameters_synctf_11_EarlyRPC_mc record:L1MuGMTParametersRcd object:L1MuGMTParameters label:None pfn:frontier://FrontierProd/CMS_COND_31X_L1T
Singularity> diff <(sort STARTHI53_V28.list) <(sort STARTHI53_V26.list)
209c209
<    leafnode:L1MuCSCTFConfiguration   parent:Calibration   tag:L1MuCSCTFConfiguration_10412_mc record:L1MuCSCTFConfigurationRcd object:L1MuCSCTFConfiguration label:None pfn:frontier://FrontierProd/CMS_COND_31X_L1T
---
>    leafnode:L1MuCSCTFConfiguration   parent:Calibration   tag:L1MuCSCTFConfiguration_90511_mc record:L1MuCSCTFConfigurationRcd object:L1MuCSCTFConfiguration label:None pfn:frontier://FrontierProd/CMS_COND_31X_L1T
218c218
<    leafnode:L1MuGMTParameters   parent:Calibration   tag:L1MuGMTParameters_gmt2012_0_EarlyRPC_mc record:L1MuGMTParametersRcd object:L1MuGMTParameters label:None pfn:frontier://FrontierProd/CMS_COND_31X_L1T
---
>    leafnode:L1MuGMTParameters   parent:Calibration   tag:L1MuGMTParameters_synctf_11_EarlyRPC_mc record:L1MuGMTParametersRcd object:L1MuGMTParameters label:None pfn:frontier://FrontierProd/CMS_COND_31X_L1T

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

1 participant