Basic

The STAR code and libraries follows a structure and policy described in Library release structure and policy. Changes in each version is described in Library release history.

Installing the core STAR software is (should be) as simple as getting a full set of code for a given library, unpacking it into $STAR_PATH (default is $STAR_ROOT/packages as described in Setting up your computing environment) and issuing the following commands (in our example, we use STAR_LEVEL=SL07b)

% cd $STAR_PATH
% cvs co SL07b
% starver SL07b
% cd $STAR
% cons

And wait ... until all is done. This will actually build the non-optimized version of our libraries.

Modifiers

To build the optimized version, use

% setenv NODEBUG yes

before you execute the starver command. If you need both, you will hence have to build twice per libraries.

To build using icc compiler, you will need an appropriate version of $OPTSTAR and

% setup icc

 before using cons.

Tips

Excluding problematic directories

Sometimes, our libraries get packed with the "Pool" (user space) libraries and their support may vary. To be on the safe side, exclude several of them from compilation by setting the environment variable SKIP_DIRS before executing cons.

% setenv SKIP_DIRS "StEbyePool StHighptPool StAngleCorrMaker 
StSpinMaker StEbyeScaTagsMaker StEbye2ptMaker StDaqClfMaker 
StFtpcV0Maker StStrangePool"

Special levels

The levels pro, new and dev are special levels as described in Library release structure and policy. pro is especially relevant as if no level is specified, the STAR login will revert to whatever pro is set to be. You may then do something like the below (again, our example assumes the default library is SL07b - please adjust accordingly).

% cd $STAR_PATH
% test -e pro && rm -f pro
% ln -s SL07b ./pro

Your default STAR library is then set for your site.