-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
undo TrackExtra size increase done in #17367 #17372
Comments
A new Issue was created by @slava77 Slava Krutelyov. @davidlange6, @Dr15Jones, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
@VinInn @ssekmen @mdhildreth Recall that the RECO data tier was increased by 10% due to issues in FastSim with PU (#17367) |
@slava77 , any update on this? |
adding TRK conveners |
assign reconstruction,simulation |
New categories assigned: reconstruction,simulation @mdhildreth,@slava77,@perrotta,@civanch you have been requested to review this Pull request/Issue and eventually sign? Thanks |
(to refresh the status) this is still active in a way; there was a recent discussion in connection with #30544 (which remained as an RFC and closed; a more generic variant of #31217, which was merged). @cms-sw/fastsim-l2 the point here is to make the following data members transient (again) TrajParams=vector<LocalTrajectoryParameters> m_trajParams;
Chi2sFive=vector<uchar> m_chi2sX5; // chi2 * 5 chopped at 255 To quote a few pieces from the email thread in August 2020 (after we narrowed down that the only use case is apparently in FastTrackDeDxProducer):
@VinInn :
|
assign fastsim |
New categories assigned: fastsim @mdhildreth,@sbein,@ssekmen,@lveldere,@civanch you have been requested to review this Pull request/Issue and eventually sign? Thanks |
@cms-sw/fastsim-l2 Please clarify. |
@cms-sw/fastsim-l2 any update here? |
@cms-sw/fastsim-l2 any update? |
this was done to get 900pre3 going and gives about 10% increase in RECO size.
Follow up will need to have some changes in fastsim first.
@VinInn @ssekmen
The text was updated successfully, but these errors were encountered: