1. 1Malcolm Ellis - Software Meeting - 12th July 2006 Data Challenge Tasks  A set of web pages has been started to follow our progress and document the work: u http://www.mice.iit.edu/software/DataChallenge/DataChallenge.ht ml http://www.mice.iit.edu/software/DataChallenge/DataChallenge.ht ml  A “Progress-O-Meter” type page has been started, and an initial list of tasks and assignments made: u http://www.mice.iit.edu/software/DataChallenge/Progress/progres s.html http://www.mice.iit.edu/software/DataChallenge/Progress/progres s.html  If your name appears under an assignment and you think it should be someone else, let me know, but if you can’t find a new victim/volunteer, then you are stuck with it!!!!

2. 2Malcolm Ellis - Software Meeting - 12th July 2006 Monitoring Progress  Please suggest to me plausible dates by which each of your tasks can be completed.  If I do not hear back with dates by this weekend, I will start assigning dates for you...  A task will not go from red to green until ALL of the following are done: u Any code that is required to be added or changed is committed into CVS and I am informed of it so that it can be tagged. u Any data files that are required to be added or changed are committed into CVS and I am informed of it so that it can be tagged. u Documentation is written (either as doxygen comments in C++ source code, or as separate txt, doc or html files) so that I can update the documentation section of the website (currently empty!)

3. 3Malcolm Ellis - Software Meeting - 12th July 2006 Example:  Task: u Check Tracker geometry and materials - Malcolm Ellis  Required for completion: u For this task to be complete, I will need to check the source code for the SciFi tracker construction in DetModel, as well as the data files that set up the geometry and materials and ensure that they match the baseline in the TRD. u I will also need to ensure that the SciFi code in DetModel has doxygen documentation and write a separate file (or files) to document how the tracker is being modeled, where the parameters came from, and explaining what the SciFi specific properties mean (e.g. the PropertyDouble FibrePitch)  In the case of classes that are being made persistent, then I will also require a UnitTest to be committed that completely tests the reading and writing of that class!

4. 4Malcolm Ellis - Software Meeting - 12th July 2006 Persistency  In addition to the usual suspects from the MICEEvent (MCParticle, TOFHit, SciFiDigit, etc) we will be making two classes from the MICERun persistent: u dataCards u MiceModule  This will enable a Digitisation job (for example) to chose to either use the same model and data cards as were used for the Simulation, OR to over-write one or both of these as required for the particular analysis being performed.  It also means that the output file will “know” what configuration was used to produce it, irrespective of any changes that may be made in the future to the input configuration files.  E.g. Simulation is run with MICEStage6/Stage6.dat on 1 st October. In November, the Stage6.dat file is changed for some valid reason. In December, we can Digitise and reconstruct this simulated data using the exact configuration that was used to make it, or modify that configuration if we chose to.

5. 5Malcolm Ellis - Software Meeting - 12th July 2006 Persistency continued  Due to the importance of the Persistency scheme to the overall success of this project, we must have UnitTests for EVERY single class that is made persistent for this project.  In this way, we can guarantee that the data that we read back in from a file is not being corrupted in some manner due to a bug in the way it was written out or read in.  Responsibility for writing these tests will go with the relevant manager of the package or detector (e.g. TOF -> Aron, Tracker -> Malcolm, etc...)  Once the Testing structure has been upgraded (in the next day or two) some sample unit tests of the persistency will be committed that can be used as models for the others.

6. 6Malcolm Ellis - Software Meeting - 12th July 2006 Further Tasks  The task list on the web is not complete at the moment, but is a good starting point.  As we make progress in defining requirements, more tasks will become evident.  As usual we have a limited number of FTEs, so please let me know if you know someone who can help with any of these tasks.