##### PHENIX software Environment #####

							May 1, 2000
							N.Hayashi

***** Linux Plat form *****

PHENIX Linux software environment at CC-J is pretty much similar to 
that of RCF. Because you will find "/afs/rhic/phenix" and "/opt/phenix"
directories from your Linux environment.

-----> If you have experienced RCF/PHENIX user, this is enough to start.

In order to get a standard PHENIX environment, DO
source /opt/phenix/bin/phenix_setup.csh

However, there is one point to remember.
CC-J Linux nodes do not use AFS, neither Transarc's original AFS 
or free client arla. But these directories "/afs/rhic/...", "/opt/phenix/..."
and "/cern" are served via NFS. "sys name" (@sys) is symbolic linked to 
"i386_redhat61" at every switchyard. As long as you use "RH6.1" 
(at the moment), this difference wouldn't appear for normal use.

No kog necessary for "CVS checkout". But of course it non-sense 
to do "CVS checkin", because it will not reflect real AFS server at RCF.

----->  If you are PHENIX software beginner, follow a very basic tutorial,
        To BUILD and RUN PISA99 (PHENIX version of GEANT3) !!

1. Login to "ccjsun.riken.go.jp" by ssh

   ccjsun.riken.go.jp is a Sun E450 and used as gateway machine to enter CC-J.

2. Login to "ap01" by ssh.

   There are many Linux machines (ap01 - ap48). "ap01" is one of
   Linuxes assigned for interactive use.
   Do "source /opt/phenix/bin/phenix_setup.csh" to be ready 
   PHENIX standard environment.

3. Go to your working directory.

4. CVS check-out

   Do "cvs co pisa99" or "cvs checkout pisa99"!
   PHENIX Software use "CVS" as source code management.
   This action create "pisa99" directory at your current directory.
   "co" means abberiviation of "checkout".

#  This is a special case for CC-J. If you use real AFS client,
#  you have to do "klog -c rhic" in order to get kerberos ticket.

5. cd ./pisa99/lib

6. Build your PISA99

   "gmake -f pisag77.mk" does all necessary procedure,
   complies source code and link objects and libraries.
   It requires one Special Run-Time-Library "libPISARoot.so".

   If you fail at link stage, check "cat linux/pisalink.g77linux".
   At this stage linker uses CERN libraries and one pre compiled 
   Run-Time-Library "libPISARoot.so". At default setting, it uses
   AFS version of "libPISARoot.so", namely 

   "/afs/rhic/phenix/PHENIX_LIB/simulation/dev/@sys/lib/libPISARoot.so"

   If it failes, it could be version mismatch.
   To build your onw "libPISARoot.so", see official PISA page.

7. Setup

   You need the following files as PISA input.

       event.par		: kinematic filter
       flukaaf.dat		: Fluka data file
       gffgo.dat		: 
       glogon.kumac		:
       map_both_february_97.dat	: Field map
       phnx.par			: PHENIX geometry
       pisa.input		: input file
       pisa.kumac		: GEANT switch etc.
    and
       hijing.dat or
       pythia.dat		: event generator output
       (You can specifiy in "pisa.input".)

    If you don't have samples, you can get them from
    "/afs/rhic/phenix/software/pisa_input/" directory.

8. Run your PISA99

   This is an interactive GEANT program. You can do playing around
   with interactive mode. But I will not describe here.
   Usually one would run as background job.
   Simply you can do "pisa < pisa.input >& pisa.output&", for example.

   If it does not run. Check "ldd pisa99".
   If any libraries is missing, your LD_LIBRARY_PATH screwed up.
   Please set it up properly. If it can find "libPISARoot.so",
   go back "6. Building PISA99".

9. Last Remarks

    PISA99 is 1999 version of PISA. New release "PISA2000" is
    expected to appear sometime in 2000. There are two major differenes

    A. PISA output file will be root format.
    B. automake
    C. 3D magnetic field map

10. Reference:

    http://www.phenix.bnl.gov/phenix/WWW/simulation/Simulation.html
    Read also tagged pages PISA99 and FAQ.

### PHOOL response chain

    PHOOL is a set of ROOT libraries and macros for ROOT.
    Current PHENIX default version of ROOT is 2.23/12.

    See Luxor tutorial page,
    http://www.phenix.bnl.gov/WWW/software/luxor/tutorials.html

    Luxor is mainly central arm description.
    For muon arm,
    ...
    but not frequrently updated.

-----> Something detail. You may not need to know.

1. HPSS is not open for general use. Something like "rftp" is not available.

2. Typical LD_LIBRARY_PATH (RH6.1)

ap01.ccj> printenv LD_LIBRARY_PATH
/afs/rhic/phenix/software/simulation/pro/@sys/lib:/opt/phenix/lib:/usr/local/lib:/usr/lib:/afs/rhic/phenix/software/new/lib:/opt/phenix/root/lib:/afs/rhic/oodb/v_5.2.1/i386_redhat61/lib:/afs/rhic/phenix/oncs/R-pro/online_distribution/lib/Linux.i686.egcs-6.1:/afs/rhic/phenix/oncs/R-pro/online_distribution/DD/lib/Linux.i686.egcs-6.1

3. RH5.2 case

   RH5.2->RH6.1 transition happened March/April 2000.
   It has been obsoleted.Go to RH6.1.

4. Objy at CC-J

5. ONCS ($ONLINE_MAIN)

   With default setup, environment variable "$ONLINE_MAIN" points to
   "/afs/rhic/phenix/oncs/R-pro/online_distribution"

   "R-pro" currently linked to "R2.6.2a" (ONCS release version).

   Check also other variable "$OFFLINE_MAIN".
   "/afs/rhic/phenix/software/new" is default.

6. pgf77 compiler

   It's history. This compiler used before PISA99 which use GNU compiler.

7. AFS mirroring

8. Test Results

   PISA99 build/running/
   PHOOL build/response chain/reconstruction/...

9. ***** Solaris Plat form *****

   There are two Sun Enterprise 450 at CC-J now. (May 1, 2000)
   But none of them are production machines. One of them, ccjsun, 
   may be used as R&D, but no PHENIX software test is made for 
   this platform yet.