Figure 1: Crate configuration as of May 28th, with empty channels with "X" in them.

We've been running for a while, so I figured I would look at the cosmics.  I also changed the reader so that it knows about the QT32Ds and so that the mapping macro uses 5/1 as the starting date since we have not changed the mapping database after that.

The cosmics for each channel can be found at: drupal.star.bnl.gov/STAR/system/files/EpdCosmics05102023.pdf

An example is:

Figure 2: EQ 4 Board 14 (which is a QT32B) channel 26 cosmics for 2 different runs.  I chose this because you can see one, maybe 2 cosmic events.

The new reader files are: drupal.star.bnl.gov/STAR/system/files/StEpdHistMaker.h.05102023.txt  and drupal.star.bnl.gov/STAR/system/files/StEpdHistMaker.cxx_.05102023.txt

I realized looking through the code (along with how messy it is!) that I actually pick up the board type in the reader and not in the mapping macro.  So I have propagated the location of the 4 QTD boards into this code.  (Mike's scan macros will also need to look for QT32D)  Additionally, I changed things for some of the QA histograms - names the East vs West ones - which had been hard coded into the reader.  (The reader doesn't pick up the db.)  This will be useful when we have beam.

Then I changed the mapping macro: drupal.star.bnl.gov/STAR/system/files/map_EpdHistos.C.05102023.txt
This now picks up the QT32D, and it reads the database as of May 1st, so the mapping is the most recent.  This requires root4star. :-)
The reason the reading and the mapping are done separately is that querying the db takes a bit.  So if one is running over say, 15+ files as needs to be done for one data point for the various scans, it would take a while.  Instead, one can run over the files, hadd them together, and then using the mapping macro to figure out where they are.

The script that runs the reader is at: drupal.star.bnl.gov/STAR/system/files/runEpdTrgHist2023.sh_.05102023.txt
I didn't make any changes to this since the beginning of the year, since it doesn't really do too much.  The syntax is:
./runEpdTrgHist2023.sh day run # of files
So for run number 241300003, I ran:
./runEpdTrgHist2023.sh 130 3 30
Each file has 10k events in it - usually I use the runlog browser to figure out how much I need.

Trying to figure out the QTDs.

QTD channel from first run we took - mip peak but low counts.