Upsilon for TPC misalignment

Here is a compressed package containing relevant files helping Yuri try to figure out the reason why the Upsilon has a large peak width. Let me explain what the files containing:

The attached 'runID_eventID_TPC_Vz_fromMiniTree.list' stores the runID, eventID, and TPC_Vz information obtained from the previous miniTree generation. 'runId_eventID_TPC_Vz_fromPico.list' stores the information obtained from pico Yuri generated, and 'TPCVz_diff' stores the events where TPC_Vz is different. 'runUpsilon4Yuri' contains the log information when we generated the miniTree from Yuri's picoDst file. One can check whether the information obtained from the chopped event is the same as what we obtained for Vertex and other information.

In a summary, when we identify events with Upsilon candidates, we require their TPC Vz to be between -100 cm and 100 cm. Additionally, we require the collision centrality to be between 0% and 80%. Therefore, the TPC Vz information and Centrality of the events should match. However, by reviewing the log file, we found inconsistencies between the information of the chopped events and the information from the previously generated miniTree.