Hit occupancy with luminosity in Run 12 pp510

Mean number of TPC hits per padrow per event averaged over sectors vs. luminosity (depth in the histograms).


Hits available to tracking, all sectors Hits with flag=0, all sectors
Hits available to tracking, good sectors Hits with flag=0, good sectors

Hits available to tracking exclude those with flag & FCF_CHOPPED or flag & FCF_SANITY. I have not investigated which flags are set for the hits that fail the flag=0 cut.

Good sectors exclude 3,5,6,7,15,19,20,21,22,23 (meant to exclude portions of the TPC where there are dead channels or low gain regions).

Runs used (50 events of zerobias data from each): 13077066, 13077068, 13077073, 13077076, 13077081, 13078001, 13078006, 13078014, 13078028, 13078035, 13078039, 13078043, 13078048, 13078051, 13078058, 13078070, 13099025 (this last run is the lone high luminosity run in this sample).

______

Here are the fraction of hits available to tracking (in good sectors) which have their flags set:

FCF_ONEPAD (1) FCF_MERGED (2)
FCF_BIG_CHARGE (8) FCF_CHOPPED (256)

I found no other flags set except for a couple hits with FCF_SANITY. We see FCF_ONEPAD at the few percent level, increasing with luminosity (occupancy?). Similarly for FCF_MERGED, but at the 10s of percent level (nearly reaching 50%). FCF_BIG_CHARGE is at a very small level with no clear pattern in this data. FCF_CHOPPED is also at the sub-1% level, with the only obvious pattern being more of them in the outer sectors than inner.

-Gene