Tunnell, Christopher, 23 August 2011 17:56
h1. MAUS User Documentation
MAUS usage is handled by several applications that enable basic usage of the framework. Each application runs several modules against a particular configuration. The particular modules that the application runs, and the configuration that is run against, can all be modified by the user.
h2. Offline data access
To get at the MICE data, look here:
There are several applications in the MAUS schema
h2. Getting Help
After reading the [[SupportFAQ|Support FAQ]] to see if your question has already been asked, then proceed to "here":http://micewww.pp.rl.ac.uk/projects/maus/issues/new to post your question on our website system. Please do read the FAQ since it may have a quick answer to your question.
Please *do not* email the code maintainers directly because we will send you to this webpage and frequently accidentally miss emails. This website is the way you are not forgotten.
h2. Configuration manipulation
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.
* 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.
* Documentation on global run controls is available in "html":http://www.mice.iit.edu/software/g4mice_doc/datacards-2-4-1.html format.
* [[Materials-2-4-1|List of valid materials]]
h2. Changing application modules
MAUS uses a modular structure in its applications. Uses can alter the modules which a particular application runs or define their own application. The different modules are listed in the [[Components]] section.
h2. File IO
Data is passed between different parts of the framework in tree-like structured data files. The tree structure is described in the [[DataStructure]] section.