Strategy/task/milestone

From Hall A Wiki
Revision as of 00:34, 9 February 2011 by Zwzhao (Talk | contribs) (New page: == Strategy == by Zhiwen Zhao (edited by Seamus) 1. Name: SolidSim 2. 64bit only and everything (environment, G4, library, executable ...) 3. Standalone Input file for every possible in...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Strategy

by Zhiwen Zhao (edited by Seamus)

1. Name: SolidSim
2. 64bit only and everything (environment, G4, library, executable ...)
3. Standalone Input file for every possible input 
   changing configuration on fly w/o code editing and recompilation
   use custom geometry description language
4. Standalone event generator
   produce output file can be read by the main simulation code,
   multiple generators for different target, reaction, condition
   plug in correction  (energy loss, radiative correction etc) 
5. Use OpenGL viewer to have interactive 3D visualization

Monte Carlo Tasks

by Paul Souder

Main priority: have a working G4 Monte Carlo

Elements

Have a working Poisson code:

  • Be able to add iron to a coil to
    • balance forces
    • provide good trajectories
  • Be able to import Poisson field maps to G4
  • Learn to use the baffle generator
  • Export the output of the baffle generator to G4
  • Evaluate the acceptance and backgrounds for a given coil/baffle geometry; optimize the same.
  • Possible coils:
    • Babar
    • CDF
    • Cleo
    • Zeus??
    • Hall D/Lanl magnet
  • Tracking and calorimeter:
    • Start with generic devices specified just by resolution. (I assume that
    • these are trivial to add.)
    • Later the properties of proposed devices and be added.

Goals

Here are some goals in order in which they can be finished. We need a milestone table based on these goals.

1. Have a G4 code with baffles and the Babar magnet that duplicates Eugene's acceptance. Baffles should be absorbers: details including punch-through and slit scattering are later additions. (Is a stand-alone code best or should we start with G4?)

2. Determine resolution with generic detectors.

3. Generate realistic backgrounds in the detectors.

4. Add realistic details



Simulation Milestones

Outlined are several milestones, some of which can be done in parallel. The timescale can be discussed, but I think all are probably on the order of two months, with the exception of producing maps/configurations for additional magnets, tracking, and possibly the radiation studies.

1a. Produce general software as specified by the framework

  • Detector description language
  • Event generator (adapt EIC code for DIS)

1b. POISSON map of Babar magnet

2a. Reproduce Eugene's acceptance

2b. Produce additional magnets

  • Babar
  • CDF
  • Cleo
  • Zeus??
  • Hall D/Lanl magnet

3a. Baffles

  • Reproduce baffle process and software specified by Eugene [1]
  • (this includes running without and with energy loss considerations)
  • The existing software may be adaptable

3b. Track resolutions

3c. Simple detector responses

4. Realistic detector responses

  • Calorimeter response
  • Gas Cerenkov
  • GEM response (adapt Super BigBite work)
  • Straw tubes

5a. Background studies

5b. Tracking

5c. Radiation Studies

Learn from other project

CMS@LHC