Datasets: Difference between revisions

From Mu2eWiki
Jump to navigation Jump to search
Line 2: Line 2:
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.
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 see the files in a dataset:
To see the files in a dataset with full file paths:
setup dhtools
samweb count-files "dh.dataset=dataset_name_here"
samweb list-files "dh.dataset=dataset_name_here"
Or make a dataset file list with full file paths:
  mu2eDatasetFileList dataset_name_here >& fcllist.txt
  mu2eDatasetFileList dataset_name_here >& fcllist.txt
See also [[Workflows]] and [[SAM]].
See also [[Workflows]] and [[SAM]].

Revision as of 15:27, 9 October 2017

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 see the files in a dataset with full file paths:

mu2eDatasetFileList dataset_name_here >& fcllist.txt

See also Workflows and SAM.

Beam

Cosmics

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 top gap
  • target7 - right top gap

Stages: same as cd3 processing.

6/2017

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. 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.
date tag name
11/2016 v5-7_9 sim.mu2e.cd3-cosmic-g4s1-target5.0901a.art
11/2016 v5-7_9-cosmic-target5-v2 sim.mu2e.cd3-cosmic-g4s2-target5.1026a_geom1.art
11/2016 v5-7_9-cosmic-target5-v3 sim.mu2e.cd3-cosmic-g4s2-target5.1104a_geom2.art
11/2016 v5-7_9-cosmic-target5-v4 sim.mu2e.cd3-cosmic-g4s2-target5.1206a_geom3.art
11/2016 v5-7_9-cosmic-target5-v5 sim.mu2e.cd3-cosmic-g4s2-target5.1216a_geom4.art
11/2016 v5-7_9-cosmic-target5-v6 sim.mu2e.cd3-cosmic-g4s2-target5.1208a_geom5.art

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

Pions

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