Launching productions with DIRAC/iLCDirac

Core commands

Pantelis Kontaxakis (University of Geneva), Juraj Smieško (CERN)

Training of the MC Production contacts

CERN, 13/3-005

21 October 2026

Environment and proxy

  • Use only the existing iLCDirac client installation from CVMFS 
    
source /cvmfs/clicdp.cern.ch/DIRAC/bashrc

dirac-proxy-init -g fcc_prod
dirac-proxy-info
  • Keep the DIRAC shell separate from a shell with the Key4hep stack
  • Production submission needs the fcc_prod group and the nickname set up

Production configuration


[delphesapp]
ExecutableName = DelphesPythia8_EDM4HEP
DetectorCard = card_IDEA.tcl
OutputCard = edm4hep_IDEA.tcl
Version = key4hep_260408

[Production Parameters]
machine = ee
prodGroup = mccontacts_training
softwareVersion = key4hep_260408
generatorApplication = delphesapp
generatorSteeringFile = p8_ee_ZH_ecm240.cmd
configVersion = key4hep-devel-6
configPackage = fccConfig
eventsPerJobs = 100
numberOfTasks = 1
campaign = summer2026
energies = 240
processes = ZH
detectorModel = IDEA
additionalName = training_<username>_attempt1
outputSE = CERN-DST-EOS
ProdTypes = Gen
move = False
  • Application sections + [Production Parameters]
  • campaign, energies, processes, detectorModel determine the output path
  • Full sim: ProdTypes = Gen, Sim, Rec with separate applications
  • Reference: FCC Production Manager Guide

Dry run and submission

  • Create the production from the configuration file 
    
# Dry run: prepares the workflow, nothing is created
dirac-fcc-make-productions -f training.conf

# Creates the transformations
dirac-fcc-make-productions -f training.conf -x
  • The dry run uses 12345 as a placeholder ID — it is not a real production
  • With -x the transformations are created and active right away
  • Start with a small pilot, check it, and only then scale up

Monitoring

  • iLCDirac web portal — certificate imported in the browser
    • Transformation and job monitors
    • Right-click on the transformation → details → LFN
  • Command line 
    
dirac-ilc-production-summary -P <transID>
dirac-ilc-get-prod-log -P <transID>

dirac-wms-job-status <jobID>
dirac-wms-job-get-output <jobID>

Managing transformations

  • Stopping and cleaning is done primarily from the command line 
    
dirac-transformation-information <transID>
dirac-transformation-get-files <transID>
dirac-transformation-verify-outputdata <transID>

dirac-transformation-cli
  stop <transID>
  start <transID>
  setStatus Stopped <transID>

# Removes the output and the jobs of the transformation
dirac-transformation-clean <transID>
  • Not all of these commands might work in the current setup

Cancelling a DRS request does not stop its transformations

Back to the DRS and DaMI

  • Record the transformation IDs in the DRS request — one per process and step
    • Fast sim (Delphes): one step → one transformation ID per process
    • Full sim (CLD, Gen, Sim, Rec): e.g. 3 processes → 9 transformation IDs
  • EOS path of the output: /eos/experiment/fcc/prod + transformation LFN
  • Validate the datasets and insert them into DaMI
  • Tutorial: iLCDirac/