As you know we are cutting over to the new system this week. We hope
to get the TRK and DC packages up to date by Tuesday. At this point
recsis, recutl, bos, fpack, gsim, seb, ec, clasutil are up to date
with the old repository.
Unfortunately the CMS document Mark and I handed out has intimiated
several people....so here is a truncated instruction set...it really
is straight forward, here are the steps for JLab users:
A) place this snippet in your .cshrc file, this orginates from
/home/freyberg/.cshrc and will be executed everytime you do a
login or remote shell.
##########################################
# source /apps/clas/u1/etc/profile/.clascshrc
alias useold "source /apps/clas/u1/etc/profile/.clascshrc"
source /apps/clas/u1/builds/DEVELOPMENT/packages/cms/jlab.cshrc
# define TOP_DIR for working with CLAS Make system
setenv TOP_DIR /home/$LOGNAME/CLAS
# define the path....
set path = ( . $TOP_DIR/bin/$OSNAME $SCRATCH/$LOGNAME/bin/$OSNAME \
$HOME/bin/$OSNAME $CLAS_BIN $HOME/scripts $path )
#
##########################################
B) make a directory (in this example I called it CLAS)
mkdir CLAS
C) USERs should:
cd CLAS
D) get the USER subroutines:
mkdir user
cd user
cp $CLAS_PACK/user/* .
E) now build the executible
make
That is all there is to it!!!
Developers should to A) and B) and then
C) checkout the package you want to work on (trk is an example)
cvs checkout trk
D) cd into trk and edit the files you want:
cd trk
**** edit any file ******
make
FREQUENTLY ASKED QUESTIONS:
There were many questions at the Friday night session. I list
some of them here so people who didn't attend the session
have access to them.
A) Which shell(s) are supported?
The jlab.cshrc at JLab is written in C-shell, born shell users are
not presently supported. We strongly encourage all users to use
the C-shell or tc-shell.
B) When I link on cebafh the Make system fails, it says it cannot
find libtcl.a.
cebafh, cebafb, cebafe, clas02 are not on the JLAB CUE system. So
the tcl libraries are not where they should be (/usr/local/lib).
The plan is to bring these machines into the CUE system sometime
in the near future. Until then you need to define two enviroment
variables that point to libtcl.a and the tcl.h header file. These
enviroment variables are TCL_LIB and TCL_INC.
C) Where is the location of the cms document?
http://www.cebaf.gov/~manak/offline.html
D) which documents are available and which ones should I pay
the most attention to?
There are many documents available in $CLAS_DOC
ls>
BOS.ps GNUmake.ps datman2.ps gsim_userguide.ps
BOS_old.ps H1DDL.ps dbrouter.ps sda_guide.ps
CLASevent.ps H1UTIL.text dll.text tcltkguide.ps
CLASgeom.ps RCS.ps fpacknew.ps templates.ps
CodeMgmt.ps Sc2_2.ps fpacknew.text tkfor.ps
DatMTool.ps cnl217.ps gsim.hlp tkfor.text
FPACK.ps datman1.ps gsim.hlp.~1~ tkrefcard.ps
I would suggest that the typical user should be very familar
with BOS.ps and gsim_userguide.ps (if you want to run gsim).
You should also have as a reference, the CVS manual and gnumake
manual (found on the page: http://www.cebaf.gov/~manak/offline.html),
and fpacknew.ps.
E) How do we learn about the data structure?
Each BOS bank has an ascii descriptor file. These files are located
in $CLAS_PACK/bankdefs/.ddl. Browse through these files to see
how the data, and reconstructed information is laid out. Hopefully
individual package documentation found at http://www.cebaf.gov/~manak/offline.html wil be available soon.
F) Which platform should I run on?
This is your choice, at jlab you can run on,
Sun's: jlabs1 jlabs2 jlabs3
HP's : jlabh1
IBM : jlaba1 jlaba2
G) Do I need a separate build directory for each platform?
NO! You execute the "make" command in the same directory
on each of the three platforms. The steps are identical
regardless of system.
H) Which platforms other then SunOS, HP-UX, and AIX are
supported?
Linux, however some packages don't build yet. So you will
have to delete ced, Map, Bosio, utilities, c_bos_io until
they get ported to Linux. Ced needs motif libraries so if
you have motif libraries on your linux box you should be able
to build ced. However recsis, gsim, fdump do build and execute.
Dec-alpha, a port to dec-alpha is in progress at odu. So far they
have a working version of fdump...so things look promising.
------- =_aaaaaaaaaa--