PWGHF: Add the QA plots for the mixed-event and Change the strategy of mixed event#8028
Conversation
|
Hi @zhangbiao-phy, thanks a lot! |
Co-authored-by: Vít Kučera <vit.kucera@cern.ch>
Co-authored-by: Vít Kučera <vit.kucera@cern.ch>
Co-authored-by: Vít Kučera <vit.kucera@cern.ch>
Co-authored-by: Vít Kučera <vit.kucera@cern.ch>
Please consider the following formatting changes to AliceO2Group#8028
Hi @fgrosa, yes, this is the previous strategy in the producer, but we don't save the derived table at this stage. So, from what I tested locally, I did not find it would increase the disk space a lot. Then I would say It's not merged in the task process, then the event pool is arround ~10-25, so it's hard to mix 10 events in that pool. Another method is to save the collision index, vz, and mul in the final derived table, then mix it locally. These are the two methods also used in HFC currently.
ah, yes, I only produce the final table, for this, let me try again now. Thanks |
It's not the case, the point is still the number of collisions that include Lc-p pair (satisfy the Lc selection) are very few. |
|
Hi @zhangbiao-phy thanks for the explanation, good for me! |
vkucera
left a comment
There was a problem hiding this comment.
Thanks @zhangbiao-phy for implementing my suggestions.
I let @deepathoms @apalasciano have the final look and merge.
alibuild
left a comment
There was a problem hiding this comment.
Auto-approving on behalf of @zhangbiao-phy.
Hi @1994ra and @fgrosa, The commit I implemented last week is still not satisfactory, since the number of events that contain lc (with selection) in one DF are few. The mixed event flow can only process in one DF for the current O2. so I made further modifications. Now, the producer no longer stores only the Lc-proton pair for collisions. Instead, I’ve set a mask to tag the collisions that contain at least one Lc or at least one selected track. Let me know if you have any questions or comments. Thanks!