New p ds #5065
New p ds #5065
Conversation
Co-authored-by: Marino Missiroli <[email protected]>
| @@ -795,7 +820,7 @@ | |||
| physics_skims=["ZMu", "LogError", "LogErrorMonitor"], | |||
| scenario=ppScenario) | |||
|
|
|||
| DATASETS = ["EGamma", "EGamma0", "EGamma1"] | |||
| DATASETS = ["EGamma", "EGamma0", "EGamma1", "EGamma2", "Egamma3"] | |||
There was a problem hiding this comment.
| DATASETS = ["EGamma", "EGamma0", "EGamma1", "EGamma2", "Egamma3"] | |
| DATASETS = ["EGamma", "EGamma0", "EGamma1", "EGamma2", "EGamma3"] |
| @@ -674,14 +694,15 @@ | |||
| disk_node="T2_CH_CERN", | |||
| scenario=ppScenario) | |||
|
|
|||
| DATASETS = ["ParkingLLP"] | |||
| DATASETS = ["ParkingLLP0", "ParkingLLP1"] | |||
There was a problem hiding this comment.
FTR, removing ParkingLLP and ParkingHH (in favour of ParkingHH{0,1} and ParkingLLP{0,1}) is okay with HLT, in the sense that today no 2025 menus contain the ParkingLLP and ParkingHH PDs.
I do not necessarily know whether or not it is okay to remove them in general from this config, that's to be determined by T0 and the other relevant experts.
PS. The same argument for removal applies to EGamma, JetMET, DisplacedJet, etc, etc.
| DATASETS = ["EmittanceScan0", "EmittanceScan1", "EmittanceScan2", | ||
| "EmittanceScan3", "EmittanceScan4", "EmittanceScan5"] | ||
|
|
||
| for dataset in DATASETS: | ||
| addDataset(tier0Config, dataset, | ||
| do_reco=True, | ||
| aod_to_disk=False, | ||
| scenario=ppScenario) |
There was a problem hiding this comment.
In the CMSTalk post, I mentioned that these are "prompt" PDs (because I do not know any better, they are not for "Parking" per se). It's a new set of PDs, for a pretty narrow use case of BRIL, and they are supposed to be small in the grand scheme of things.
I wonder if they should be configured similarly to PDs like JetMET* or SpecialZeroBias*, which seem to have a 2nd copy of RAW on T1 tape. As for AlCaRecos that BRIL may need on these EmittanceScan PDs, I do not actually know. Maybe this is something that AlCa experts could easily clarify with BRIL.
The treatment of these PDs offline is a bit beyond my expertise, but if you think TSG (and not PPD or T0) should follow this up with BRIL, please let me know.
| @@ -587,13 +587,26 @@ | |||
| do_reco=True, | |||
| scenario=ppScenario) | |||
|
|
|||
| DATASETS = ["ParkingSingleMuon","ParkingSingleMuon0","ParkingSingleMuon1","ParkingSingleMuon2"] | |||
| DATASETS = ["ParkingSingleMuon1","ParkingSingleMuon2","ParkingSingleMuon3", | |||
There was a problem hiding this comment.
This does not seem to have ParkingSingleMuon0 (while the HLT menu does have it).
Following the request in cms-talk, the following datasets are being added to the configuration:
Also, a few requested changes in the Physics skims of ParkingLLP and JetMET PDs.