Update PhysicsRun2021_pass0_recon.lcsim #1067
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am adding validated kalman filter tracking algorithm parameter optimizations to the steering file for the first pass. The optimization method you are familiar with (likely from the last collaboration meeting) was used w/ 1000 iterations to obtain settings which improved MC efficiency 4% and increased data track number 10% in run 14185. I believe the reason MC only increased marginally compared to data track number is because MC already is quite clean and easy to construct well. The info pertaining to MC optimization (and its validation) was already included in previous talks. I had to manually include new optimization constraints for data, because I realized that some parameters relevant to data could not have been optimized for MC. The reward function was updated to optimized efficiency in MC and track no in a single data file in run 14185; the MC efficiency is not increasing as high as it did before after 1000 iterations but I suspect as much is expected because now it has to simultaneously work in a clean and messy environment. I am doing some further validation, but I would be comfortable using this steering file in the run. Here is a plot showing the track number increase between the two iterations:
Red is old, blue is new; it is shifted into higher track no per event. In total we find 10% more tracks while retaining the same MC efficiency and negligible change in fake rate or duplicates (atleast when training on 14185). I can characterize its behavior on other runs, and more extensively if requested.