From d52982f538b2d44c4f9d9b5eb57ca6eeac4df977 Mon Sep 17 00:00:00 2001 From: Dener Lemos Date: Wed, 14 Aug 2024 11:04:26 -0500 Subject: [PATCH] Update 02-HLT_timing.md --- _episodes/02-HLT_timing.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/_episodes/02-HLT_timing.md b/_episodes/02-HLT_timing.md index f2fb5e7..840a980 100644 --- a/_episodes/02-HLT_timing.md +++ b/_episodes/02-HLT_timing.md @@ -66,16 +66,18 @@ A CERN account with access to lxplus - that's it! python3 submit.py /dev/CMSSW_14_0_0/GRun/V173 --cmssw CMSSW_14_0_11 --cpu-only --tag YOUR_CPU_JOB_TAG_HERE ``` -7. Once your jobs have finished, get the reports for one of the jobs using the `job_manager.py` script and the `--report` option. This will download a `tar.gz` file containing output and error files for : +7. Once your jobs have finished, get the reports for one of the jobs using the `job_manager.py` script and the `--report` option. + + ```bash + python3 job_manager.py --report JOB_ID + ``` + This will download a `tar.gz` file containing output and error files for : - the creation of the CMSSW environment on the timing machine (i.e. the `scram proj`/`cmsrel` step) - the building of the CMSSW environment including the merging of provided pull requests etc. (i.e. the `scram b` step) - the benchmarking script (found in the `run_benchmark.py` file) which initializes and controls the settings of the actual timing measurements on multiple CPUs/GPUs using the [`patatrack-scripts`` repo](https://github.com/cms-patatrack/patatrack-scripts) - the final `cmsRun` of the timing job - ```bash - python3 job_manager.py --report JOB_ID - ``` **NOTE:** All of these steps are taken care of by the server for you as a user and the reports are just helpful tools when occasionally some measurement is crashing.