Sherpa Tar Creation of Sliced Samples

This topic describes how to create tar balls, which contain full integration and logs, to add to the input for generation and hence shorten the generation-process.

For steps of generation involving Sherpa Tarballs, see:

Find Sherpa-2.2.8 documentation here:


Sherpa Tar Creation

The current version of the Sherpa Tar Creator we've used at Tufts' supercomputer Cluster

..can be found here:

..implements Sherpa-2.2.8 at /cvmfs/

..uses 32 cores for the "integration" step and 12 cores for the other four steps. When Openloops is necessary (with job options including loops), there is an additional 0th step, namely "getOpenLoops".

Step No. Step Name No. of Cores Run-time (d-hh:mm:ss)
0 getOpenLoops 12 00:11:57
1 createLibs 12 00:08:28
2 makelibs 12 00:08:22
3 integrate 32 1-11:02:35
4 makeTarball 12 00:00:39
5 evgen 12 06:47:41
For submitting jobs:
  • Login and start an interactive node
  • Set up Athena-Generation with (recommended for Sherpa_2.2.8) > asetup 21.6.2,AthGeneration
  • Pick a new singularity module > module load singularity/3.1.0
  • Submit tar creation > python ../sherpaTarCreator/ MC.File.Of.Your.Choosing --noPrecompile
  • Watch progress > watch --interval 30 sacct --job={[step0-jobid]..[step5-jobid]} --format=jobid,jobname,elapsed,ncpus,state
Once a tarball is created, it

..appears in your runDir, e.g.: mc_13TeV.Sh_228_Zee_EnhLogPtV_BbarMode5.GRID.tar.gz

..can be unzipped by > gunzip -c *.tar.gz | tar xopf -

..will have: 3.integrate.log Process/ Results.db

For an example of these files and the complete logs that are produced during a tar ball creation, see:


Job options

Here we'll describe the specific Job Options (e.g., sliced) we've looked at and how we created them.

Original jobId/jobOption is 421304/

Link to the original jobOption (JO):

Implemented changes:

Starting with the Original, we've changed the following:

  • Reduced the number of events to 100 to increase testing speed
  • Reduced NJET to 3 and edited processes so that there are at least 1 jet by redefining "Process 93 93 -> 11 -11 93 93{NJET}" and adding "Cut_Core 1" (so the integration starts with events of type 2_3__j__j__e-__e+__j__QCD, you can check this by looking into runDir/ecm13TeV/3.integrate.log once the integration starts),
  • Edited EnhancedVariable for the slice to be only enhancing HT "Enhance_Observable VAR{log10(sqrt(H_T2)-PPerp(p[2])-PPerp(p[3]))}|1|3.7 {3,4,5,6,7}" (instead of the max among HT and pT)
  • Defined pT boundaries "PT2NLO 11 -11 500 E_CMS"
Sliced jobID/JO is 421364/

Link to the Sliced JO:


Optimization of Cluster jobs

We've tested enhancement boundaries on the HT and boundaries of pT on the tarballs we've generated. Statistics on these tests:



-- Colette F I Kaya at FikriyeIdilKaya - 2020-04-18

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng optStats.png r1 manage 111.1 K 2020-04-18 - 17:21 ColetteKaya  
Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r6 - 2020-06-10 - ColetteKaya
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback