Previously in the comparison of charged hadron triggers in the Run 9 dijet embedding to the pi0 triggers in Run 9 data, the embedding showed a systematic depletion of tracks in the trigger pT range (9 - 20 GeV/c) relative to the data.  See the track pT comparison in this post:

https://drupal.star.bnl.gov/STAR/blog/dmawxc/update-01152018-run-9-embedding-charged-hadron-triggers

It was suggested that it might be due to a region in trigger eta-phi which wasn't being populated in data, but was in embedding.  The comparison of trigger phi can be seen in this post:

https://drupal.star.bnl.gov/STAR/blog/dmawxc/update-02082018-run-9-embedding-trigger-phi

The trigger eta-phi distributions for data and embedding are presented below.  As you can see, there's a distinct swath where there are no pi0 triggers in data (even when using a smaller hot tower list).

So I masked out the region phi = (1.25, 1.58), and recalculated the track pT distributions.  Even after masking out this region, the depletion persists...

I've attached the two different hot tower lists used in the first two plots; 'pp200r12.hotTowers.d24m10y2017.txt' is the list with 302 towers, and 'HotTowerList.StGJetTreeAnalysis.txt' is the list with 41 towers.  The distributions with the bad phi region masked out were made with the latter (41 tower) list.  Below I've tabulated the number of triggers found in each partonic pT bin when the bad phi region was masked out and the 41 tower list was used.  The precise definitions of the charged hadron and pi0 triggers can be found in the first link.