STAR Software Basics Introduction to the working environment Lee Barnby - Kent State University

Contents Machines - gateway, analysis farm Disks - home, data, afs Library - cvs, star levels, compilation Communications - hypernews, mailing lists Makers & macros - bfc, doEvents

Machines (hardware) Gateway machines to log into rcf facility –rsshgw.rcf.bnl.gov, rssh2gw.rcf.bnl.gov (these 2 preferred, no jobs allowed) –rcf.rhic.bnl.gov ( , web, etc. NO analysis related jobs) Machines for working –Solaris rmine02.rcf.bnl.gov, rmine03.rcf.bnl.gov –Linux (RedHat 6.1) analysis nodes rcas6001.rcf.bnl.gov to rcas6015.rcf.bnl.gov interactive nodes rcas6016.rcf.bnl.gov to rcas6025.rcf.bnl.gov for LSF (cannot login) Login from gateway using e.g. ‘ssh rcas6012’ LINK

Disks For Writing Home directory is for things you create, e.g. modified source code. It is backed up nightly by rcf. It is NOT for data… Physics working group data disks –/star/rcf/pwg/{nameofpwg} Reading stuff DSTs are located in /star/rcf/reco/P00hd_1/2000/07 Archiving rftp utility –no password, use put and get to archive and retrieve files to your personal piece of HPSS (mass storage tape system) Should use for files >1Mb in size to be efficient. For directories first use the ‘tar’ Unix command Should use for files >1Mb in size to be efficient. For directories first use the ‘tar’ Unix command Make yourself a directory in here LINK

Communications Hypernews fora –follow “hypernews” link from STAR home page –can browse the different topics and sign up to receive mail for those that interest –need to sign up to make postings too Mailing lists –follow “ archives” link –there is information on how to sign up –starsoft is the software announcements list LINK

Software library Repository under cvs control 3 libraries or “levels” –dev (updated daily) for development –new (~few weeks) relatively stable, perform studies here –pro (when necessary) for official production switch levels by typing e.g. ‘starnew’ –can check current level with ‘STAR_LEVELS’ This means updates to repository are NOT visible until library is rebuilt in the evening

Software library II Basic organization StRoot directory with subdirectories for Makers contains C++ code to work with root4star also macros subdirectory pams directory with subdirectories for groups contains (mostly) older Fortran reconstruction code Example I am working in “new” level and would like the latest version of a particular maker, StFtpcTrackMaker Also applies if you want to modify a package LINK

Library - cvs Obtain token – klog (then type afs password at prompt) In a fresh directory “check out” –cvs co StRoot/StFtpcTrackMaker Compile and build using “cons” (replacement for “make”) –cons +StFtpcTrackMaker Similar thing works for pams –N.B. You can check out specific subdirectory, e.g. pams/global/evr BUT smallest unit to compile is e.g. pams/global Directory tree will appear in your directory StRoot/StFtpcTrackMaker.share directory and either.sun4x_56_CC5 or.i386_redhat61 directories appear for compiled code LINK

Makers & macros Makers Compiled code to put in a “chain”, 2 main chains are bfc.C and doEvents.C bfc.C is the chain for running reconstruction. Works on raw data. It has a scheme to add your maker before or after an existing maker. doEvents.C is for analysing the reconstructed dsts Macros Interpreted code - many examples can be found in $STAR/StRoot/macros –examples start off very simple e.g. bfcread.C opens a dst file LINK