Creating and Using Framework/AC++ Modules

• If you do not do this in your login: source ~cdfsoft/cdf2.cshrc
• setup cdfsoft2
• This example will take up about 9000 blocks of disk space so if you do not have that much space in your home area, go to your scratch area: cd /spool/<your_name>
• newrel -t 1.8.0 testrel
• cd testrel
• newpkg MyExample
• cd MyExample
• cp $EXAMPLES_DIR/HistExample.cc MyModule.cc
• cp $EXAMPLES_DIR/HistExample.hh MyModule.hh
• cp $EXAMPLES_DIR/AppUserBuild_template.cc MyExample_test.cc
• chmod 775 * this will allow you to edit them.
• Edit the MyModule* files. Inside MyModule.cc, and MyExample_test.cc replace
  #include "Examples/HistExample.hh"
  with
  #include "MyExample/MyModule.hh"
  
• inside MyExample_test.cc change the line:
  aModule = new HistExample( "hist", "Histogramming example" );
  to
  aModule = new MyModule( "MyModule1", "My example module" );
  This file has the same purpose as the build_job output file in the old system. Changing the first line to the second says that in this test job create an instance of MyModule called MyModule1 not the HistModule. The first argument is the name to use on the AC++ command line and the second will be used as the discription field.
• inside MyModule.hh and MyModule.cc, change all occurrences of HistExample to MyModule
• Now make any functional changes to MyExample.cc that you wish. Suggestions from the class syllabus may be too ambitious but we can help if you are really interested:
  1. Add cuts to candidate muons and/or tracks
  2. Implement a "distance of closest approach" cut
  3. Extend to electron or meson candidates, other decays
  In order to do this you should:
  1. Identify banks needed, $BANKS_DIR/Banks/*.hh
  2. Create classes for them if needed (this is the hard part)
  An easier excersize would be to use the already existing classes in the example in different ways.
  1. Look at $BANKS_DIR/Banks/CMUO_Bank.hh to see what other named accessors could be used.
  2. Add histograms of other interesting quantaties.
  In any case even if you don't make any changes you should at least make it write something new to cout so that you know that your module is actually run and not the HistMoudle.
• cd .. Go back to the top level of the release, (testrel). This is where the make command should always run from.
• gmake
• run the executable from the top level of the release, invoke it with whatever name you choose for the BINS target in your GNUmakefile. It will be MyExample_test if you did not edit the make file. The binary can be run from the testrel directory without a path specification and it is also easier for the debuggers to find sources if you launch them from this directory.
• cp $EXAMPLES_DIR/run_ac++hist_ex.tcl run.tcl tcl files can be used the way uic files were used in the old system. If you are on cdfsga you can use the run.tcl file without changing the input file name because the data file it uses is in the standard validation area. However you should edit it and change hist to MyModule1 so that your module will be run in the SamplePath instead. For more available commands see the beginning chapters of this document. Although it is very old the commands have not changed. Much work on the user interface is needed and it will be improved this fall.