[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Analysis Instructions / Phone Call




Hi Peter,

I have attached the analysis instructions which I sent to Bernhard and
Claude a week or so ago, so that you can post them on the MuCap web page.
The "howto" file gives directions for setting up a CVS directory which
maintains the MIDAS-based "mu" analysis softare, as well as instructions
for performing analyses with that software.  The other 2 files are
auxiliary files; the "howto" will direct the user on what to do with them.

As I told Bernhard in an earlier e-mail today, I am working on developing
the histograms which Bernhard requested (muPC1,2 coincidences, etc).
Unfortunately, I don't quite know which data to look at.  I analyzed
run01606.mid, but many of the histograms came up empty.  I don't know if
this reflects some reconfiguration changes or problems with the
detectors, since the analysis software produces reasonable plots on the
older data (specifically, run00905.mid).  I will try to code
"anticipatory" versions of the requested histograms, but they will
probably not be any good until I can fully develop them on valid data.

BTW, I think Fred and I will try to give you a call on your cellphone
sometime Monday morning (Pacific time).  We want to discuss manpower
scheduling for the coming 3 months.  To give you some idea of our thoughts
on the matter, we agreed that it would probably be best for Fred to arrive
in mid-August and stay until early September.  I would arrive in early
September (overlapping for one week with Fred), and stay until the end of
the run October 15.  That way, Fred's heavy-duty computer skills will be
available when they are most needed, at the beginning of the run in
August.  I will then show up later for low-skill DAQ support and general
assistance with shifts, etc.

Tom
Here are the basic instructions for creating a MuCap MIDAS analysis directory
on either the Merlin cluster, or a machine running Red Hat 7.3:

1. Configure your .bash_profile to include the lines in the supplied
   bash_profile file.  If your existing .bash_profile has functioning
   instructions, you will need to merge the contents of the existing file
   and the new file.  Otherwise, you can just copy the new bash_profile
   into .bash_profile.

   This will configure your account to use the correct versions of 
   gcc (i.e. the C, C++, and Fortran compilers), ROOT, and MIDAS.

   Remember that you must log out, and then back in again, before any 
   changes to bash_profile will take effect.

2. Check out a copy of the analysis program from the CVS repository.  A
   subdirectory named "mu" will be created under the current directory,
   containing the analysis software.

     > cvs -d mucap@kaon.physics.berkeley.edu:/home/mucap/cvsroot co mu

   The password is the same as the one for the data account on pc620 and 
   pc3608, named after a type of electronics.

3. Now move into the newly-created analysis directory, and build the 
   program:

     > cd mu
     mu> make

4. In the mu directory, install the supplied file AnalyzerODB as .ODB.SHM:
     mu> mv AnalyzerODB .ODB.SHM

5. Run the analysis program with:

     mu> ./mu -i INPUT_FILE.mid -o OUTPUT_FILE.root -n NUMEVENTS

   (e.g. ./mu -i /data/run00905.mid -o 905.root -n 20)  

6. In order to view the resultant root file, you must run the root program 
   and load the analysis output file:

     mu> root
     root> f = new TFile("905.root")

   Now suppose, for example, you want to see the muon stop distribution:

     root> gStyle->SetPalette(1)
     root> MuonStopsBragg->Draw("COLZ")

   This should create a window with the histogram plotted on it.
   In order to view all of the available histograms, you can type

     root> f = new TBrowser

   and a window will appear.  Click on "ROOT Files", and a list of icons--
   one for each histogram--will appear.  This can help you save some typing 
   on the command line.  (Note: All of the histograms which are available 
   come from the module "raw_spectra.cpp".)


# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi

# User specific environment and startup programs

# Two cases; standard PSI Red Hat 7.3, and PSI Merlin cluster
if fgrep -q Valhalla /etc/redhat-release; then
  CLUSTER=psi-7.3
else
  CLUSTER=merlin
  GCC_DIR=/usr/local/gcc-2.95.3
fi

export ROOTSYS=/afs/psi.ch/project/mucap/$CLUSTER/root/pro
export MIDAS_ROOT=/afs/psi.ch/project/mucap/$CLUSTER/midas-cvs
export MIDAS_HOME=$MIDAS_ROOT
export MIDAS_DIR=$HOME/mu
export CVS_RSH=ssh

export PATH=$GCC_DIR/bin:$PATH:$ROOTSYS/bin:$MIDAS_ROOT/linux/bin:$HOME/bin
export LD_LIBRARY_PATH=$MIDAS_ROOT/linux/lib:$ROOTSYS/lib

export BASH_ENV=$HOME/.bashrc
export USERNAME=""

Attachment: Analyzer.ODB
Description: Binary data