MAUSUser » History » Version 3
Rogers, Chris, 16 March 2011 09:08
1 | 1 | Rogers, Chris | h1. MAUS User Documentation |
---|---|---|---|
2 | |||
3 | h2. Applications |
||
4 | |||
5 | 2 | Rogers, Chris | There are several applications in the MAUS schema: |
6 | |||
7 | 3 | Rogers, Chris | * _Simulation_ tracks particles through a given geometry. |
8 | 2 | Rogers, Chris | |
9 | 1 | Rogers, Chris | h2. Configuration manipulation |
10 | |||
11 | MAUS uses a set of user-modifiable files to control the application configuration. Variables such as input geometry, field arrangement and detector parameters can all be modified by the user. |
||
12 | |||
13 | * Documentation on geometry file generation is available in "pdf":http://www.mice.iit.edu/software/g4mice_doc/Mice_Module-2-4-1.pdf or "html":http://www.mice.iit.edu/software/g4mice_doc/Mice_Module-2-4-1.html format. |
||
14 | * Documentation on global run controls is available in "html":http://www.mice.iit.edu/software/g4mice_doc/datacards-2-4-1.html format. |
||
15 | * [[Materials-2-4-1|List of valid materials]] |
||
16 | |||
17 | h2. Changing application modules |
||
18 | |||
19 | 2 | Rogers, Chris | MAUS uses a modular structure in its applications. Uses can alter the modules which a particular application runs or define their own application. Modules are of several types. |
20 | 1 | Rogers, Chris | |
21 | * _Maps_ are executed once per spill and manipulate the spill data in some way (for example, try to do pattern recognition on tracker digits). |
||
22 | * _Reduces_ are executed once per run and manipulate all the spills in some way (for example, make a histogram of the tracker light yield). |
||
23 | * _Runners_ control how Maps and Reduces are executed, for example controlling multithreading or doing some optimisation. |