Strange muon_veto_trigger nonsense about hax HOT 3 CLOSED

I checked the runs 12359 and 12360. The regrowing fixed the problem for them as well.

from hax.

On Oct 31, 2017, at 10:51 AM, Andrea Molinario @molinario wrote:

I send you a list of runs for which we can try to regrow the Proximity minitrees. You will see they are a good number. You can understand the reason by looking at the attached picture, which shows how the time difference between MV and high energy TPC events changes in time during SR1. These high energy TPC events are due to muons crossing the detector, so we would expect a tight time coincidence with MV. This is almost always the case, except for a few cases here and there and a specific period going from August 23rd to September 4th. The 3 runs you have already regrown belong to this period. Maybe it's even better to regrow Proximity for all runs in this period, and not only for those mentioned in my list.

I don't know why this is happening. I re-produced the Proximity minitree myself for few of these runs and I found that the MV-TPC time differences for high energy events change, getting to the expected value typical of physical coincidence among the two detectors.

list_run.txt

from hax.

@molinario ok i've regrown your list of runs. please check and let me know if i missed any.

from hax.