/ZeroBias/Commissioning10-May19ReReco-v1/RECO, CMS collaboration
Cite as: CMS collaboration (2019). ZeroBias primary dataset in RECO format from the 0.9 TeV and 7 TeV Commissioning runs of 2010 (/ZeroBias/Commissioning10-May19ReReco-v1/RECO). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.QJ68.VK85
ZeroBias primary dataset in RECO format from the 0.9 and 7 TeV Commissioning runs of 2010. This dataset includes the data from the CASTOR calorimeter, which covers the very forward region in the CMS experiment (-6.6 < eta < -5.2).
The list of validated runs, which must be applied to all analyses, can be found in
Events stored in this primary dataset were selected because of A) the presence of a filled LHC beam bunch crossing in the IP (HLT_ZeroBias, HLT_L1_BPTX). This is the most basic requirement for a proton-proton collision to happen in CMS with as little selection bias as possible, hence a zero bias selection. B) the presence of a filled LHC beam bunch in only a single beam coming from the positive side (HLT_L1_BPTX_PlusOnly). This selection does not allow for any collision to happen as only one beam has a filled bunch crossing the IP, it is thus ideal to study electrical and beam-induced noise in the CMS detectors. C) the presence of a filled LHC beam bunch in only a single beam coming from the negative side (HLT_L1_BPTX_MinusOnly). This selection does not allow for any collision to happen as only one beam has a filled bunch crossing the IP, it is thus ideal to study electrical and beam-induced noise in the CMS detectors.
Data taking / HLT
The configuration files used to assign data to this dataset can be found in the list of HLT configurations (run between 135059 and 135575).
HLT trigger paths
The possible HLT trigger paths in this dataset are:
During data taking all the runs recorded by CMS are certified as good for physics analysis if all subdetectors, trigger, lumi and physics objects (tracking, electron, muon, photon, jet and MET) show the expected performance. Certification is based first on the offline shifters evaluation and later on the feedback provided by detector and Physics Object Group experts. Based on the above information, which is stored in a specific database called Run Registry, the Data Quality Monitoring group verifies the consistency of the certification and prepares a json file of certified runs to be used for physics analysis. For each reprocessing of the raw data, the above mentioned steps are repeated. For more information see:
You can access these data through the CMS Virtual Machine. See the instructions for setting up the Virtual Machine and getting started with CASTOR calorimeter data in
The open data are released under the Creative Commons CC0 waiver. Neither CMS nor CERN endorse any works, scientific or otherwise, produced using these data. All releases will have a unique DOI that you are requested to cite in any applications or publications.