Datasets

Introduction

This page is an attempt to record the datasets created and uploaded by "production". These are semi-permanent datasets that were created for the collaboration as a whole. It is nearly impossible to maintain dataset information perfectly when any datasets can become invalidated in various ways, or completely obsolete, at any time, for many reasons. Please do not use any datasets without consulting experts in these datasets - that's still the best way to be sure you are using the right dataset.

To print lists of datasets that are known to SAM - all or optionally with restrictions (see -h).

setup mu2efiletools
mu2eDatasetList

To see the files in a dataset with full file paths:

mu2eDatasetFileList dataset_name_here >& fcllist.txt

See also Workflows, FileTools and SAM.

Beam

TDR

See TDRDatasets

cd3

See background group.

051017

This sample of stage 1 beam simulation was generated in May 2017 to answer questions about CRV shielding. Default geometry. This sample is standard enough that it could be of use to other groups. Goals of this effort:

• Rates and dead-time with improved precision
• Sources of coincidences from neutrons and gammas
• Improved shielding and CRV geometry to mitigate rates and to increase CRV coverage (geometry changed in later stages)

The standard cd3 beam stage 1 fcl was modified to only write out the dsregion and mubeam datasets. Run in v6_2_1. See 8627 and 7040. Expert: Yuri Oksuzian.

• 500K jobs of 10K POT, total 5e9 POT
• cnf.mu2e.cd3-beam-g4s1.051017.fcl
• sim.mu2e.cd3-beam-g4s1cat-mubeam.051017.art (concatenated 20-to-1, uploaded)
• sim.mu2e.cd3-beam-g4s1cat-dsregion.051017.art (concatenated 20-to-1, uploaded)

geant4 v10 test samples

Run 11/2016 to 2/2017 to test geant4 v10. See doc-9336 doc-9624 doc-9402 doc-9139 doc-8357. For dataset details, see GeantV10Test. Expert: Ray Culbertson and Yuri Oksuzian.

MDC2018

A dataset to replace cd3 background frames and signal samples, largely driven by changes in tracker and target geometry.

Details

Cosmics

Calibration Cosmic Test Sample

Calibration cosmics are events taken with a simulated trigger intended to collect all cosmics that hit a detector, for use in calibration studies. The digis for trk and cal are written out, as well as the StepPointMC's for CRV (the CRV product is being updated, so we did not write here). The code used was built locally and not tagged, thought it was eventually committed. v6_5_2 should read it OK. Expert: Ray Culbertson

3/2018, three samples were generated, 1M events generated for each then some filtering.

• ext - detector extracted to +14m in z
  • Bfield is on but the default maps do not reach that far, so Bfield appears off
  • trigger on trk OR cal
  • Dataset: sim.mu2e.cosmic_calib_ext.180302.art
  • geometry: Mu2eG4/geom/geom_common_garage.txt (mods to Mu2eG4/geom/geom_common_current.txt)
  • Total cosmic rate = 1989.85 Hz for 1M events = 502s livetime
• ins - detect in normal inserted position
  • Bfield on
  • trigger on trk OR cal
  • Dataset: sim.mu2e.cosmic_calib_ins.180302.art
  • geometry: Mu2eG4/geom/geom_common.txt (->Mu2eG4/geom/geom_common_cd3_s4p2.txt)
  • Total cosmic rate = 1989.85 Hz for 1M events = 502s livetime
• crv - detect in normal inserted position
  • Bfield on
  • trigger on CRV hits
  • Dataset: sim.mu2e.cosmic_calib_crv.180302.art
  • geometry: Mu2eG4/geom/geom_common.txt (->Mu2eG4/geom/geom_common_cd3_s4p2.txt)
  • Total cosmic rate = 23010.7 Hz for 1M events = 43s livetime

target6/7 Study

Generated to study how cosmics enter the gap between the CRV top and sides, to help determine the CRV final design. Daya Bay generator. Summary talk 11147. Expert: Ralf Ehrlich.

• target6 - left (+x) top gap
• target7 - right (-x) top gap

Stages: same as cd3 processing.

6/2017 full listing

target5 Study

Generated to study cosmic rays that enter the TS hole and produce tracks, and how they can be degraded with new shielding blocks. This follows up on this category of events discovered in CD3 target1. Daya Bay generator. Talk summary 8322. Expert: Ray Culbertson.

The talk shows the various shielding configurations and concludes new shielding would help. Stages:

• s1 - v579, generate on a plane that is the TS opening, sim to a surface between TS3 and TS5
• s2 - various branches off of v579, complete sim, reco, require a track 50-200 MeV.

The job were run around 11/2016.

git tag	dataset name
v5-7_9	sim.mu2e.cd3-cosmic-g4s1-target5.0901a.art
v5-7_9-cosmic-target5-v2	sim.mu2e.cd3-cosmic-g4s2-target5.1026a_geom1.art
v5-7_9-cosmic-target5-v3	sim.mu2e.cd3-cosmic-g4s2-target5.1104a_geom2.art
v5-7_9-cosmic-target5-v4	sim.mu2e.cd3-cosmic-g4s2-target5.1206a_geom3.art
v5-7_9-cosmic-target5-v5	sim.mu2e.cd3-cosmic-g4s2-target5.1216a_geom4.art
v5-7_9-cosmic-target5-v6	sim.mu2e.cd3-cosmic-g4s2-target5.1208a_geom5.art

Stage1 fcl and archive:

bck.mu2e.cd3-cosmic-g4s1-target5.0901a.tbz
cnf.mu2e.cd3-cosmic-g4s1-target5.0901a.fcl

Stage 2 fcl and archive. The geometry was changed by running the same fcl but a different release, defined by the tag and loaded on cvmfs in OfflineSpecial

cnf.mu2e.cd3-cosmic-g4s2-target5.0901a_geom1.fcl
bck.mu2e.cd3-cosmic-g4s2-target5.1026a_geom1.tbz
bck.mu2e.cd3-cosmic-g4s2-target5.1104a_geom2.tbz
bck.mu2e.cd3-cosmic-g4s2-target5.1206a_geom3.tbz
bck.mu2e.cd3-cosmic-g4s2-target5.1216a_geom4.tbz
bck.mu2e.cd3-cosmic-g4s2-target5.1208a_geom5.tbz

cd3 background

Produced to determine the cosmic background for CD3 review. Daya Bay generator. Talk summary 7131, memo 3059. Expert: Ralf Ehrlich.

• general - all cosmics passing through a horizontal surface through detector.
• target1 - left side, around TS entrance
• target2 - upstream face
• target3 - downstream face
• target4 - cryo hole

Stages (s1-s4 uploaded)

• s1 - v542, simulate CRV, require 45 MeV of energy on detector volume surface, stop
• s2 - v566, simulate detectors, require 15 straw hits
• s3 - v574, reco, require a track 50-200 MeV
• s4 - v576, require tracks, 100-110 MeV, passing all cuts, PID, no upstream track
• s5 - v576, reconstruct CRV and make analysis ntuples (not uploaded)

For s1 and s2, there is also a truncated data stream, which is events that overflow the SimParticle list.

date	Offline	name
5/2016	v576	sim.mu2e.cd3-cosmic-g4s4-general.v542_v566_v574_v576.art
5/2016	v576	sim.mu2e.cd3-cosmic-g4s4-target1.v542_v566_v574_v576.art
5/2016	v576	sim.mu2e.cd3-cosmic-g4s4-target2.v542_v566_v574_v576.art
5/2016	v576	sim.mu2e.cd3-cosmic-g4s4-target3.v542_v566_v574_v576.art
5/2016	v576	sim.mu2e.cd3-cosmic-g4s4-target4.v542_v566_v574_v576.art

There is another page with a full list of these datasets.

CRY 1

A sample of 5(40)% of a mu2e true(effective) live-time with CRY cosmic generator produced around Dec 20, 2018. This was produced at the Argonne HPC center, "Bebop" farm. The computing year deadline was approaching so some shortcuts had to be made, and the procedure was not fully in the production scripting. branch =v7_2_0_CRYMT based of Offline tag=v7_2_0 fcl =JobConfig/cosmic/cosmic_defs_s1s2.fclinc. The generator time was set to 0, so the time of the hits needs to be offset to get into the reco window, see GenerateCosmicTimes_module.cc Experts: Yuri Oksuzian, Lisa Goodenough

The following configuration (EventGenerator/defaultConfigs/othersCRYconfig.txt) was used:

CRY::CRYSetup: Setting returnMuons to 1
CRY::CRYSetup: Setting returnNeutrons to 1 
CRY::CRYSetup: Setting returnProtons to 1 
CRY::CRYSetup: Setting returnGammas to 1 
CRY::CRYSetup: Setting returnElectrons to 1
CRY::CRYSetup: Setting returnPions to 1
CRY::CRYSetup: Setting returnKaons to 1
CRY::CRYSetup: Setting date to 6-21-2021 (month-day-year)
CRY::CRYSetup: Setting latitude to 41.8
CRY::CRYSetup: Setting altitude to 0
CRY::CRYSetup: Setting subboxLength to 30

The production plane of 30x30 meters was centered at the tracker. Generated primaries were projected back to the world volume. The simulation then was initiated from the world volume. The sample was produced using 0.75M (divided by 0.58) CPU hours on Bebop, processing on 32 cores with 8 threads.

Output datasets:

• sim.mu2e.cosmic-g4s1s2-crygeneral-cat.181220.art (6545 files, 1885124 events)
• sim.mu2e.cosmic-g4s1s2-truncated-crygeneral-cat.181220.art (1309 files, 61042 events)

With log file tarballs:

• bck.mu2e.cosmic-g4s1s2-crygeneral-cat.181220.tbz
• bck.mu2e.cosmic-g4s1s2-truncated-crygeneral-cat.181220.tbz

Adding digis with mixing:

• cnf.mu2e.CRY-cosmic-general-mix.MDC2018g.fcl
• dig.mu2e.CRY-cosmic-general-mix.MDC2018g.art
• bck.mu2e.CRY-cosmic-general-mix.MDC2018g.tbz

CRY 2

In March 2019, the sample was generated using 1.5M CPU hours on Theta and 1.0M (divided by 0.58) hours on Bebop. The sample size is 130% of effective Mu2e live-time. Live-time values are stored in log files. As with CRY 1 sample, all particle species were simulated. Used configuration: EventGenerator/defaultConfigs/defaultCRYconfig.txt Tag: v7_3_5 fcl: Offline/JobConfig/cosmic/cosmic_s1_general_cryMT_G4internalFilters.fcl The dataset needs to be moved to tape:

/pnfs/mu2e/persistent/users/mu2epro/workflow/mu2e_CRY_2

The production plane of 300x300 meters was centered at the tracker and positioned at top of the dirt volume. Generated primaries were projected from the dirt toward the CRV box. Tracks that intersect CRV box were simulated. The

Antiprotons

Bernstein Study

9/2017 generating antiprotons in the primary target, flat in energy and phase space. head of branch pbarAnalysis, from head after v6_2_3, on Aug 25 15:22, hash 2ce1246d3d7833bcdd8fcf38bcea3ab6f3255755. 100K jobs x 500K pbars, first NERSC production - docker image mu2e/prd:pbar-00. generate and sim to the upstream side of TS1 pbar window. Production: Ray Culbertson, Physics: Bob Bernstein.

• fcl dataset: cnf.rhbob.NERSCprod1.pbarAnalysis_0_1.fcl
• Concatenated dataset (485 files, 177637185 events): sim.mu2e.antiprotons_cs1VD91.170829.art
• logs and TFileService: bck.mu2e.NERSCprod1.170829.tbz

2019 Bernstein Study

Code has been rewritten to streamline the procedure, and the sample is regenerated.

Stage 0 generates protons on target, traces them through all target interactions, then stops the simulation, saving only particles that could have produces a pbar when interacting. sim.mu2e.masterPbarVertices.v0.000.art

The first interaction in the target is selected as a pbar production point and a pbar is generated random in direction angle, and with momentum flat from X to Y. The pbar is not propagated. The output is a file with the vertices and pbars now produces an art file which contains pbars in the production target.