Skip to content

README.md

Latest commit

 

History

History
216 lines (164 loc) · 7.51 KB

README.md

File metadata and controls

216 lines (164 loc) · 7.51 KB
Raw

DeepMuonReco sample

Ntuplizer/  shared plugin and notebook
Phase2/     Phase-2 configs and Condor submission
Run3/       Run 3 configs and Condor submission

The sample inspection notebook is Ntuplizer/notebooks/check-ntuple.ipynb.

Phase-2

Use CMSSW_14_0_9.

source /cvmfs/cms.cern.ch/cmsset_default.sh
cd /path/to/CMSSW_14_0_9/src
cmsenv
scram b -j 8

cmsRun "$CMSSW_BASE/src/DeepMuonRecoSample/Phase2/test/runReReco_cfg.py" \
  inputFiles=file:/path/to/input.root outputFile=rereco.root maxEvents=-1

cmsRun "$CMSSW_BASE/src/DeepMuonRecoSample/Phase2/test/runDeepMuonRecoNtuplizer_cfg.py" \
  inputFiles=file:rereco.root outputFile=ntuple.root maxEvents=-1

The Phase-2 physics configuration and ntuple schema are unchanged; only the paths moved under Phase2/.

Phase-2 Condor

The same submit file is used for ReReco and ntuple jobs. Each line of the input list is one absolute ROOT file path.

cd "$CMSSW_BASE/src/DeepMuonRecoSample/Phase2/condor"
mkdir -p logs /hdfs/path/to/rereco
find /hdfs/path/to/official-input -type f -name '*.root' -size +1000c \
  | sort > inputs-rereco.txt

condor_submit -batch-name phase2-rereco \
  cfg=runReReco_cfg.py label=rereco max_events=-1 \
  input_list="$PWD/inputs-rereco.txt" output_dir=/hdfs/path/to/rereco \
  submit.sub

Submit and worker nodes must see the same CMSSW project path.

After ReReco finishes, make a new input list and change only the cfg and output directory:

mkdir -p /hdfs/path/to/ntuples
find /hdfs/path/to/rereco -type f -name '*.root' | sort > inputs-ntuple.txt

condor_submit -batch-name phase2-ntuple \
  cfg=runDeepMuonRecoNtuplizer_cfg.py label=ntuple max_events=-1 \
  input_list="$PWD/inputs-ntuple.txt" output_dir=/hdfs/path/to/ntuples \
  submit.sub

Run 3

Use CMSSW_14_0_21_patch1 with the package linked into its src directory.

source /cvmfs/cms.cern.ch/cmsset_default.sh
scram project CMSSW CMSSW_14_0_21_patch1
cd CMSSW_14_0_21_patch1/src
ln -s /absolute/path/to/DeepMuonRecoSample DeepMuonRecoSample
cmsenv
scram b -j 8

Change to an empty working directory, then run the five configs:

mkdir -p /path/to/run3-work
cd /path/to/run3-work

cmsRun "$CMSSW_BASE/src/DeepMuonRecoSample/Run3/test/runGENSIM_cfg.py"
cmsRun "$CMSSW_BASE/src/DeepMuonRecoSample/Run3/test/runMinBiasGENSIM_cfg.py"
cmsRun "$CMSSW_BASE/src/DeepMuonRecoSample/Run3/test/runDIGIRAW_cfg.py"
cmsRun "$CMSSW_BASE/src/DeepMuonRecoSample/Run3/test/runRECO_cfg.py"
cmsRun "$CMSSW_BASE/src/DeepMuonRecoSample/Run3/test/runDeepMuonRecoNtuplizer_cfg.py"

The default files are gensim.root, minbias.root, digiraw.root, reco.root, and ntuple.root. The Run 3 setup uses the official SingleMuFlatPt2To100 gun and generates TuneCP5 13.6 TeV MinBias events with the local fragment. DIGI then reads those MinBias files for direct Summer24 pileup mixing.

Run 3 deliberately uses the same ntuple schema as Phase-2. Consequently, track_is_matched_muon does not distinguish a signal muon from a pileup muon.

Run 3 Condor

Run 3 is split into separate jobs and keeps every stage output:

signal GENSIM ─┐
               ├─> DIGIRAW ─> RECO ─> Ntuple
MinBias pool ──┘

The production below creates 250 signal files with 1000 events per file. A shared MinBias pool contains 4,000 files with 1,000 events per file. With the Summer24 pileup profile, each MinBias event is reused about 45 times across all bunch crossings, or about 2.8 times for in-time pileup alone. Keeping every stage output requires roughly 15 TB.

Submit each stage only after checking that the previous stage finished and its ROOT files were transferred successfully. Start from a built CMSSW_14_0_21_patch1 environment:

cd "$CMSSW_BASE/src/DeepMuonRecoSample/Run3/condor"
campaign_tag=production_v01
campaign_dir="/hdfs/user/$USER/DeepMuonReco/Run3/$campaign_tag"
log_root="$PWD/logs/$campaign_tag"
mkdir -p "$log_root"/{gensim,minbias,digiraw,reco,ntuple} \
  "$campaign_dir"/{gensim,minbias,digiraw,reco,ntuple}

First check the exact submissions without queueing jobs:

condor_submit -dry-run /tmp/run3-gensim.ad -batch-name run3-gensim \
  stage=gensim first_job=0 last_job=249 events=1000 \
  log_root="$log_root" output_dir="$campaign_dir/gensim" generation.sub

condor_submit -dry-run /tmp/run3-minbias.ad -batch-name run3-minbias \
  stage=minbias first_job=0 last_job=3999 events=1000 \
  log_root="$log_root" output_dir="$campaign_dir/minbias" generation.sub

If both dry runs succeed, submit the signal and MinBias productions:

condor_submit -batch-name run3-gensim \
  stage=gensim first_job=0 last_job=249 events=1000 \
  log_root="$log_root" output_dir="$campaign_dir/gensim" generation.sub

condor_submit -batch-name run3-minbias \
  stage=minbias first_job=0 last_job=3999 events=1000 \
  log_root="$log_root" output_dir="$campaign_dir/minbias" generation.sub

After both productions finish, create the shared pileup list and the indexed signal input list. The pileup list contains CMSSW file names; the indexed list contains JOB_INDEX ABSOLUTE_PATH on each line. Their line counts must be 4,000 and 250 respectively.

find "$campaign_dir/minbias" -type f -name 'minbias_*.root' -size +1000c \
  | sort | sed 's#^#file:#' > inputs-minbias.txt

find "$campaign_dir/gensim" -type f -name 'gensim_*.root' -size +1000c \
  | sed -E 's#.*/gensim_([0-9]+)\.root#\1 &#' \
  | sort -n > inputs-gensim.txt

wc -l inputs-minbias.txt inputs-gensim.txt

condor_submit -dry-run /tmp/run3-digiraw.ad -batch-name run3-digiraw \
  stage=digiraw events=-1 input_list="$PWD/inputs-gensim.txt" \
  pileup_list="$PWD/inputs-minbias.txt" \
  log_root="$log_root" output_dir="$campaign_dir/digiraw" processing.sub

condor_submit -batch-name run3-digiraw \
  stage=digiraw events=-1 input_list="$PWD/inputs-gensim.txt" \
  pileup_list="$PWD/inputs-minbias.txt" \
  log_root="$log_root" output_dir="$campaign_dir/digiraw" processing.sub

Build the next indexed list after each stage succeeds:

find "$campaign_dir/digiraw" -type f -name 'digiraw_*.root' -size +1000c \
  | sed -E 's#.*/digiraw_([0-9]+)\.root#\1 &#' \
  | sort -n > inputs-digiraw.txt

wc -l inputs-digiraw.txt

condor_submit -dry-run /tmp/run3-reco.ad -batch-name run3-reco \
  stage=reco events=-1 input_list="$PWD/inputs-digiraw.txt" \
  log_root="$log_root" output_dir="$campaign_dir/reco" processing.sub

condor_submit -batch-name run3-reco \
  stage=reco events=-1 input_list="$PWD/inputs-digiraw.txt" \
  log_root="$log_root" output_dir="$campaign_dir/reco" processing.sub

find "$campaign_dir/reco" -type f -name 'reco_*.root' -size +1000c \
  | sed -E 's#.*/reco_([0-9]+)\.root#\1 &#' \
  | sort -n > inputs-reco.txt

wc -l inputs-reco.txt

condor_submit -dry-run /tmp/run3-ntuple.ad -batch-name run3-ntuple \
  stage=ntuple events=-1 input_list="$PWD/inputs-reco.txt" \
  log_root="$log_root" output_dir="$campaign_dir/ntuple" processing.sub

condor_submit -batch-name run3-ntuple \
  stage=ntuple events=-1 input_list="$PWD/inputs-reco.txt" \
  log_root="$log_root" output_dir="$campaign_dir/ntuple" processing.sub

The expected result is 250 files in each signal stage and 4,000 MinBias files: gensim/gensim_INDEX.root, minbias/minbias_INDEX.root, digiraw/digiraw_INDEX.root, reco/reco_INDEX.root, and ntuple/ntuple_INDEX.root. The dry runs validate Condor expansion only; they do not run CMSSW. Do not assign one signal job index to two different event chunks; retrying the same failed job should reuse its index. Submit and worker nodes must see the same CMSSW project and mounted HDFS paths.