next up previous contents
Next: Porting Code between different Up: Program development Previous: Naming conventions

Basic Structure of the PAW_FOPI analysis code

paw_fopi: Main program

E_ANAL: Analysis steering program, called via DST or RAW KUIP menu:

E_get_raw dispatcher routine for RAW input

E_get_dst exp. steering program for DST input

For each D/S in event:

E_put_dst exp. steering program for DST output

The locations of reference source and library files on the various systems are listed below.

VMS                           MVS                          UNIX 
 
           Sources/Libraries
 
ref_ulib:*.for               'kp09.ulib.fort(*)'           $CAVEB/ulib/*.f
inc_ulib:*.inc               'kp09.ulib.incl(*)'           $CAVEB/ulib/*.i
ref_ulib:*.c                 'kp09.ulib.c(*)'              $CAVEB/ulib/*.c
inc_ulib:*.h                 'kp09.ulib.h(*)'              $CAVEB/ulib/*.h
                             'kp09.ulib.asm(*)'            $CAVEB/ulib/*.s
                             'kp09.ulib.inc(*)'           
ref_flib:*.for               'kp09.flib.fort(*)'           $FOPI/flib/*.f
inc_flib:*.inc               'kp09.flib.incl(*)'           $FOPI/flib/*.i
ref_flib:*.com               'kp09.flib.exec(*)'
ref_flib:*.kumac             'kp09.flib.kumac(*)'
ref_flib:*.cdf               'kp09.flib.cdf(*)'
ref_flib:flib.mms            'kp09.flib.make'              $FOPI/flib/flib.make
ref_flib:flib.olb(*)         'kp09.flib.load(*)'           $FOPI/flib/libflib.a
cern_inc:*.inc               'kp09.cern.incl(*)'           $CAVEB/cern/*.i
 
           basic installation procedures
 
KP1$root:[fopi]cms_defs.com  'kp09.flib.exec(cmsdefs)' /u/fopi/flib/cmsdefs.sh  (AIX)
                                                       /disks/dsah_2/fopi/flib/cmsdefs.sh   (ULTRIX)
KP1$root:[caveb]cms_defs.com 'kp09.ulib.exec(cmsdefs)' /u/fopi/ulib/cmsdefs.sh  (AIX)
                                                       /disks/dsah_2/fopi/ulib/cmsdefs.sh   (ULTRIX) 
 
           Utilities
 
ref_flib:extfopi.dis
ref_flib:fopi.dis
ref_flib:pawlnk.com
ref_flib:pawlnk_x11.com
ref_flib:pawlnk_offl.com

For your private stuff you may use the following scheme (just a proposition). It should help to group together software dealing with a specific beamtime, e.g. February 1991:

VMS                                 MVS
---                                 ---
 
[user.paw]*.com              'xxxx.paw9102.exec(*)'        ~/xxxx/paw9102/*.sh
[user.paw]*.inc              'xxxx.paw9102.incl(*)'
[user.paw]*.kumac            'xxxx.paw9102.kumac(*)'
[user.paw]e_user.for         'xxxx.paw9102.fort(euser)'
                             'xxxx.paw9102.cntl(pawlnk)'
[user.paw]paw_fopi.exe       'xxxx.paw9102.load(pawfopi)'


next up previous contents
Next: Porting Code between different Up: Program development Previous: Naming conventions

Back to GSI Home Page Back to FOPI Home Page Index

fopi
Tue May 28 15:33:35 CST 1996