1Malcolm Ellis - CM th October 2006 Status of Data Challenge  Don’t Shoot the Messenger!  Data Challenge – explanation  Software Tools u Design iteration u MICEEvent, MICERun, etc... u Configurations u Applications u Example Analyses u Testing u GRID  Documentation u Installation guide u G4MICE documentation u Task Assignments & Progress  Next Steps

2Malcolm Ellis - CM th October 2006 Don’t Shoot the Messenger!  I’ve decided to try to get some work done today and Chris kindly offered to present this summary for me.  I will cover most of the issues in this talk in more detail in the Software summary on Wednesday and will be present for questions/abuse/etc...

3Malcolm Ellis - CM th October 2006 Data Challenge – SW perspective  Purpose – to push the development of and test the use of the software tools needed for MICE by performing a complete cycle of simulation, digitisation, reconstruction and analysis of the MICE experiment.  Requires: u Working software tools u Documentation u Analysis techniques u Computing resources (e.g. GRID)  Should help produce: u Improved software tools (debugging defects discovered in the process of performing the challenge). u Improved documentation. u Increase the number of MICE who are able to use the MICE software (maybe?)  Originally stated goal was to be ready to begin by CM16 (i.e. now).  We are not quite there yet, but are hopefully only a week or two late.  Scope has been extended to include analysis of real data (KEK test beam).

4Malcolm Ellis - CM th October 2006 Software Tools  G4MICE is divided up into packages (domains) that provide: u Libraries dedicated to particular tasks (e.g. Interface, Detector modeling, Reconstruction, Visualisation, etc...) u “Applications”, that is, compiled executables that are linked with one or more of the libraries and which are dedicated to performing one or more “Use Cases” (e.g. Simulation of the beam passing through a stage of MICE).  Data flow inside G4MICE: u C++ classes represent physics (e.g. SciFiHit, MCParticle, TofSpacePoint, etc...) u Persistency scheme allows these classes to be written to and read from disk. u Real data converters read raw data files (e.g. KEK test beam) and produce C++ classes.

5Malcolm Ellis - CM th October 2006 Design Iteration  Initially proposed in April 2004 (Software Workshop and CM).  Plans made for detailed design, release, testing and acceptance procedures.  Process stalled due to external (to the software group) pressures not to make changes.  Following year and a half spent “patching up” code to meet analysis needs, unable to take it apart and build things up as required.  Process re-started in October last year.  First pass of the iteration will be complete with the release of mice-2-0 which will be the version used for the first attempt at the Data Challenge.

6Malcolm Ellis - CM th October 2006 MICEEvent, MICERun, etc...  Currently store C++ classes that contain physics information in two containers: u MICEEvent – classes that have a “life” corresponding to one event (particle trigger), e.g.: s MCParticle s SciFiHit s TofSpacePoint s SciFiKalTrack s ZustandVektor u MICERun – classes that have a “life” over a data taking run, e.g.: s MiceModule (modeling a configuration of MICE) s VlpcCalib (calibration information for the SciFi tracker) s TrajectoryManager (Kalman filter package manager class)  Will eventually add a third category: u MICESpill – collection of events that are read out in a single burst (1 ms). This will be implemented when it is required to simulate/study pile- up effects and make a more accurate model of the DAQ setup.

7Malcolm Ellis - CM th October 2006 Configurations  Between test beams, 6 stages of MICE, multiple running modes per setting (e.g. beam momentum, emittance, cooling channel parameters, etc) and systematic studies (e.g. misalignments, optimising component layout, etc) there is the need to define and control a vast number of configurations of the MICE hardware.  MiceModule solution was presented at CM15 and has been extended since then.  A configuration is implemented as a tree of instances of this class that hold all the information (geometry, material, detector, magnetic field, etc) required to define that configuration.  First use of this for a systematic study will be the tracker station spacing optimisation.

8Malcolm Ellis - CM th October 2006 Applications  For a given task (e.g. Simulation) an application is defined in G4MICE.  This is a separate directory in CVS in which an executable is created by linking one or more of the G4MICE libraries.  Special purpose code in the main() routine can be defined by anyone to use any of the G4MICE features.  Current list of applications includes: Analysis, Digitization, EventDisplay, FileSplitter, KekOct2005, Optics, PawHistograms, PawNtuples, PidStudies, Reconstruction, RootEvent, RootHistograms, RootTrees and Simulation  Anyone who discovers a new need that cannot be fulfilled by the existing applications can create a new one for the special purpose (e.g. KekOct2005 is specifically for the analysis of the KEK test beam in October 2005).  A LOT of analyses can be conducted using the existing applications (see next slide).

9Malcolm Ellis - CM th October 2006 Example Analyses  Determine the emittance of a beam: 1. Simulate the beam (Simulation Application), Monte Carlo hits are written to an output file. 2. Calculate the emittance of the beam (Analysis application), Monte Carlo hits are read back in from the file and the analysis routines are used to determine the emittance.  Determine the distribution of particles passing through TOF2: 1. Simulate the beam (Simulation Application), Monte Carlo hits are written to an output file. 2. Run an application to produce a histogram or ntuple (in PAW or ROOT format) reading in the ouput file and making histograms or an ntuple of the desired values.  Determine the momentum resolution of the tracker: 1. Simulate the beam (Simulation Application). 2. Digitise the hits (Digitization Application). 3. Reconstruct the digitised hits (Reconstruction Application). 4. Read in the results of the reconstruction and create histograms or ntuples of the reconstructed and Monte Carlo truth momenta and plot the difference...

10Malcolm Ellis - CM th October 2006 Testing  The software tools are of course under constant development (and, on average, improvement).  Even with the very small number of developers currently working on G4MICE it is easy to make changes that improve one area of performance and simultaneously degrade others.  In addition, crucial components (internal AND external) need to be tested to ensure that the physics has not changed (e.g. what if GEANT4 changes the multiple scattering model? Would we notice?!)  The answer to these (and more) problems is a comprehensive set of tests.  This was started by Yagmur some time ago, and has now been moved to a separate CVS area (MICETESTS) and is currently growing rapidly.  By mice-2-0 we will have reasonable coverage of the MICE code in Unit Tests as well as a few System and Integration tests to ensure some level of control over the physics performance of the software.

11Malcolm Ellis - CM th October 2006 e.g. MuScat vs GEANT4  Comparison of MuScat analysis with GEANT4 shows large difference with versions prior to  G4MICE has migrated to  System test will be developed to monitor the multiple scattering simulation so that we can keep track of any changes with future upgrades to newer versions.

12Malcolm Ellis - CM th October 2006 GRID  Serious analyses are going to require a lot of CPU and disk space (in particular anything that involves the simulation of RF background!).  We now have a MICE VO (Virtual Organisation)!  A GRID portal has been developed at Imperial College.  Unfortunately, I’ve not had any luck using it since getting a Fermilab GRID certificate and joining the MICE VO (successful use to date was with an Imperial GRID certificate and membership of the dteam VO).  Hoping someone at Imperial can help put me in touch with the experts there and sort out what is most likely a trivial mistake or omission on my part...

13Malcolm Ellis - CM th October 2006 Documentation  All of these tools are no use if you don’t know how to use them!  Even worse is documentation that is inaccurate!  As part of the current preparation for the data challenge I am in the process of updating the documentation on the MICE website.  It is still very limited, but can be found here:  The main areas that are covered are: u Installation guide u Documentation of the crucial G4MICE components u Task assignments & progress

14Malcolm Ellis - CM th October 2006 Installation Guide  G4MICE is now capable of operating under three operating systems: u Linux (always the default, serious productions will be run on Linux) u Macintosh OS X u Cygwin on Windows (using g++ not VC++)  The MAC and Windows versions are suitable for users to learn how to run small G4MICE jobs as well as for developers to work on code.  A page explaining how to install G4MICE from scratch is now on the web here: u  It is hoped that we will eventually be able to provide a single script that will perform all of these steps for the user.  The procedure has so far been tested successfully by a number of students and post-docs, we aim to eventually make it Professor-friendly...

15Malcolm Ellis - CM th October 2006 G4MICE Documentation  The existing documentation on G4MICE includes: u Doxygen documentation, generated automatically from the source code every day. u Access to the CVS repository for browsing the code. u The architectural diagram (for identifying dependencies) and list of package managers (so you know who to contact for help). u Bug database (bugzilla) for searching open or past bugs, or entering a new one. u Datacards – a page describing each of the datacards that the user can set to control the operation of G4MICE. u MiceModules – a page describing how the MICE configurations are specified. u Units – a page describing the use of physical units in G4MICE u Materials – a page describing the specification of materials in G4MICE u Applications – a page describing how to use each of the existing applications.

16Malcolm Ellis - CM th October 2006 Task Assignments & Progress  On the web from the Data Challenge website: u  Has not been updated by me for quite some time (sorry!).  I aim to update it before the end of CM16 and do so more regularly between now and the release of mice-2-0 for the start of production.

17Malcolm Ellis - CM th October 2006 Next Steps  We have made a lot of progress, with limited (and decreasing!) mouse-power, however there are still a number of crucial things to complete: u Finish work on SciFi decoding. u Debug SciFi seed and validate Kalman track fit. u Add reconstruction code to create ZustandVektor from reconstructed tracks and output DST output containing just ZustandVektors for analysis. u Update Analysis code to use ZustandVektor for emittance calculation. u Complete first version of HepRep visualisation. u Prepare data cards and configurations needed by Analysis group for production. u Run test productions on GRID to validate scripts. u Finish tests and documentation. u Release mice-2-0.