Skip to content

Demo Jobs for LHCbPR2 Grid

Three new jobs to demonstrate LHCbPR2Grid Working:

Run 5 Simulation

The first two demonstrate simulation able to produce larger yields split over many sub jobs:

  • PRTESTGRID-FG-DETRun5Baseline-DD4HEP-PPnu54-SIM-P8-30000000-10Kevts-queue ; 10k gauss validation at nominal run 5 lumi, working from the current "Gaussino Run 5" nightly (PRTEST-FG-DETRun5-DD4HEP-PP2016-SIM-P8-30000000-1Kevts) which uses 2016 luminosity for speed.
  • PRTESTGRID-FG-DETRun5Middle-DD4HEP-PPnu54-SIM-P8-30000000-10Kevts-queue ; Similar but at the lower lumi wp (1e34)

Notes:

  • maybe 10k is too much at this lumi, could be reduced to 5k.
  • This makes use of the "Gauss splitter" to prevent the same events being generated multiple times, which needs Gauss().FirstEventNumber defining in the options file
  • Options files had to be customised to prevent overwriting of beam settings
  • The handler is quite old now, and definitely would be updated in future to test things like the new Multi-threading and timing of vertices, but that will be done centrally, so for now using the default gaussValidation handler

These two jobs won't be identical to the live server, but will demonstrate the ability to simulate higher throughput tests (with realistic settings).

PRTEST-DET2022-PP2024-SIM-P8-20000000-100evts on Grid

The other test attempts to produce the exact same results as an existing test, PRTEST-DET2022-PP2024-SIM-P8-20000000-100evts, a digitisation test with noticeably poor errors in some cases. With the grid enabled this can run over all of the available input files (upgrade_2024.Q1.2_BsToPhiPhi_md_sim) rather than 1000 evts.

Notes:

  • Job uses identical options file, internal to Boole
  • Makes use of the "Extract Input" tool: script prints out the urls to the input files, ganga should deal with this
  • Makes use of the "Remove Input" tool: script, as otherwise the ganga inputfiles will be ignored. This is general to boole, but a discussion might be needed about how to generalise these last two effects.

ToDo:

  • If fails, test locally before pushing fixes (the first commit is acting as a user test, which ideally will not need testing as the live PR jobs are already known to be working)
  • Decide if it is useful/worth it to implement a generalised "input file extractor/remover" using the IO helper. Do all LHCb coresoft jobs use this tool? Moore?

Test Status

PRTESTGRID-Run3-Integration-spillover-ALLFILES-queue

Timestamp Task Creation Jobs Handler Notes
2025-03-12 11:00 \textcolor{blue}{\text{completed}} (log) Step 0 (log)- \textcolor{green}{\text{running}}:
\textcolor{blue}{\text{completed}} (5) \textcolor{lightgray}{\text{submitted}} (1) \textcolor{green}{\text{running}} (1)
2025-03-10 11:00 \textcolor{blue}{\text{completed}} (log) Step 0 (log)- \textcolor{blue}{\text{completed}}:
\textcolor{blue}{\text{completed}} (7)
\textcolor{blue}{\text{completed}} (log)
2025-03-07 14:00 \textcolor{blue}{\text{completed}} (log) Step 0 (log)- \textcolor{blue}{\text{completed}}:
\textcolor{blue}{\text{completed}} (7)
\textcolor{blue}{\text{completed}} (log)
2025-03-07 12:00 completed (log) Step 0 (log)- completed:
completed (7)
running (log)

PRTESTGRID-FG-DETRun5Baseline-DD4HEP-PPnu54-SIM-P8-30000000-10Kevts-queue

Timestamp Task Creation Jobs Handler Notes
2025-03-12 11:00 \textcolor{blue}{\text{completed}} (log) Step 0 (log)- \textcolor{green}{\text{running}}:
\textcolor{lightgray}{\text{submitted}} (3) \textcolor{blue}{\text{completed}} (5) \textcolor{green}{\text{running}} (2)
2025-03-10 11:00 \textcolor{blue}{\text{completed}} (log) Step 0 (log)- \textcolor{blue}{\text{completed}}:
\textcolor{blue}{\text{completed}} (10)
\textcolor{blue}{\text{completed}} (log)
2025-03-07 14:00 \textcolor{blue}{\text{completed}} (log) Step 0 (log)- \textcolor{blue}{\text{completed}}:
\textcolor{blue}{\text{completed}} (10)
\textcolor{blue}{\text{completed}} (log)
2025-03-07 12:00 completed (log) Step 0 (log)- completed:
completed (10)
running (log)

PRTESTGRID-FG-DETRun5Middle-DD4HEP-PPnu36-SIM-P8-30000000-10Kevts-queue

Timestamp Task Creation Jobs Handler Notes
2025-03-12 11:00 \textcolor{blue}{\text{completed}} (log) Step 0 (log)- \textcolor{green}{\text{running}}:
\textcolor{lightgray}{\text{submitted}} (1) \textcolor{green}{\text{running}} (1)
2025-03-10 11:00 \textcolor{blue}{\text{completed}} (log) Step 0 (log)- \textcolor{blue}{\text{completed}}:
\textcolor{blue}{\text{completed}} (2)
\textcolor{blue}{\text{completed}} (log)
2025-03-07 14:00 \textcolor{blue}{\text{completed}} (log) Step 0 (log)- \textcolor{blue}{\text{completed}}:
\textcolor{blue}{\text{completed}} (2)
\textcolor{blue}{\text{completed}} (log)
2025-03-07 12:00 completed (log) Step 0 (log)- completed:
completed (2)
running (log)
Edited by Ghost User

Merge request reports

Loading