Items for next production

[riga]

Likely targeting v15 if new samples are not needed before ~May/June.

• L1 trigger objects, @artlbv (added in Adding L1 trigger objects  #15)
• Additional HLT trigger objects, @jolange
• Split ISR/FSR weights, @jolange
• Check trigger bits of additional triggers @artlbv
  • HLT_Mu12_IsoVVL_PFHT150_PNetBTag0p53 (and Mu14)
  • HLT_Ele14_eta2p5_IsoVVVL_Gsf_PFHT200_PNetBTag0p53
• Updated v15 configs, @riga
  • General adjustments for v15 in custom cmssw modules and injected customizations (added in e140775)
  • Check compatibility with cmssw-based stack (esp. gfal plugins for transports) (added in e140775)
  • Include UGloParT taggers (added in f6285a6)
  • Sync with HLepRare settings (fixing trigger bit bug) (added in f6285a6)
  • Add datasets for 2024 (data added in e8781d9, MC missing)

[artlbv]

Additional HLT trigger objects, @jolange

I am curious what you mean with this? :)

[riga]

As far as I know there were some trigger objects missing that represent jet legs needed for offline matching on analysis level.

[jolange]

Additional HLT trigger objects, @jolange

I am curious what you mean with this? :)

Right, there are no objects stored für SixJet + b-tagging triggers.

[riga]

@jolange I just figured we might already skip some collections that you might need. Could you check if these dropped collections look ok to you?

nanogen/config/nano_run3_v14.yaml

Lines 18 to 30 in 066af43

	column_filters:
	# drop some object collections alltogether
	- drop ^n?CaloMET.*$
	- drop ^n?CorrT1METJet.*$
	- drop ^n?TkMET.*$
	- drop ^n?FsrPhoton.*$
	- drop ^n?GenDressedLepton.*$
	- drop ^n?GenIsolatedPhoton.*$
	- drop ^n?GenProton.*$
	- drop ^n?IsoTrack.*$
	- drop ^n?LowPtElectron.*$
	- drop ^n?OtherPV.*$
	- drop ^n?SoftActivityJet.*$

[jolange]

Could you check if these dropped collections look ok to you?

Thanks, yes, for now we don't need any of that! (With the usual "but who knows..." 😉)

We will be working with run 2 data only for the foreseeable future, by the way, but the list is identical.

[riga]

@artlbv @mschrode @jolange

We are planning a production of nano v15 datasets (based on mini v6) for the 2024 campaign and I updated the list of TODOs in the description above.

I converted a test file with the current state and you can find the nano-self documentation in this file on dust: /data/dust/user/riegerma/nanogen/store/GenerateNanoDocs/config_24_v15/tt_sl_powheg/dev1/docs.html .

Can you

a) check if there are items missing in the TODO list, and
b) see if the content covers everything you'd need?

I can provide you the nano file privately for inspection.

[artlbv]

thanks for pinging! also adding @LukasEbeling here

As far as I know there were some trigger objects missing that represent jet legs needed for offline matching on analysis level.

fwiw we currently do not have the trigger bits for HLT_Mu12_IsoVVL_PFHT150_PNetBTag0p53 (and Mu14) and HLT_Ele14_eta2p5_IsoVVVL_Gsf_PFHT200_PNetBTag0p53

I wonder also whether all Tau objects are stored for e.g. the HT+1b+1tau path @portalesHEP in v15?