Warning, /analysis/LuminosityCounterGoodRuns/README.md is written in an unsupported language. File is not indexed.
0001 To set up, cd to the run directory and do
0002 bash setup.sh [user's build directory] [user's install directory]
0003
0004 This will set everything up, build, and install the module. Note that the scripts are currently set up to use the ana.458 build, which is old. The user should probably update this, but it should be kept consistent across scripts.
0005
0006 The User can skip steps marked optional if the user wants to - the default setup reaches into jocl's tg directory to find the ttrees. If the user doesn't want to skip them (i.e., the user wants to generate their own ttrees for whatever reason), the user should edit the file addcommand.sh by removing all instances of the text jocl in the file (there should only be one) and replace with $UN
0007
0008 To get luminosities:
0009
0010 1. create a list of run numbers the user wishes to use. This can be accomplished in various ways, but probably the best one is to use the repo at https://github.com/sPHENIX-Collaboration/analysis/blob/master/runListGeneration/Run2024pp/ to get a list. This step is non-optional.
0011
0012 Then do
0013
0014 2. (optional) CreateDstList.pl --build [build to use] --cdb [cdb tag] --list [user's run list]
0015
0016 To get lists of DSTs.
0017
0018 3. (optional) do
0019
0020 bash run_runs.sh
0021
0022 To get a bunch of ttrees to a tg directory that setup.sh created. The user won't need to look at these.
0023
0024 4. do
0025
0026 bash run_alladd.sh
0027
0028 To get more condensed ttrees for analysis.
0029
0030 At this point, the user can either run
0031
0032 root "check.C([run number])" to dump out the info for a given run
0033
0034 or
0035
0036 root get_all_lumi.sh [user's runlist]
0037
0038 to get the total luminosity for all triggers for all the runs in the user's list. Note that this reports luminosity ONLY for good/analyzable segments. Segments which are corrupt or otherwise unable to be analyzed are not used.
