aboutsummaryrefslogtreecommitdiff
path: root/src/quad.c
diff options
context:
space:
mode:
authortlatorre <tlatorre@uchicago.edu>2020-04-13 11:57:15 -0500
committertlatorre <tlatorre@uchicago.edu>2020-04-13 11:57:15 -0500
commit441871fe030ef8ba7ea9ad02fda4a1e9caf03f93 (patch)
treedaff3ae7e1dba34a707ec80815dfb6927508a9af /src/quad.c
parentd1ce12ce69604c6979f4ffa45e4908eb71b19c60 (diff)
downloadsddm-441871fe030ef8ba7ea9ad02fda4a1e9caf03f93.tar.gz
sddm-441871fe030ef8ba7ea9ad02fda4a1e9caf03f93.tar.bz2
sddm-441871fe030ef8ba7ea9ad02fda4a1e9caf03f93.zip
update fit to fit each event twice with different quad quantiles
This commit updates the fit program to fit each event and particle hypothesis twice, once using the normal quad implementation and the other by cutting on the 10% quantile of times. The first way is much much better when the event is fully contained since quad will return a really good starting point, and the second is much better for muons where we want to seed the fit near the entry point of the muon. Ideally we would only need a single call and I have an idea of how to update QUAD to maybe return reasonable guesses in both cases. The idea is to take the cloud of quad points and find the position and time that has the smallest time such that it is only a certain Mahalabonis distance from the distribution. This (I think) corresponds roughly to what I would do by eye where you look at the distribution of quad points in the cloud and see that it forms a track, and pick a point at the start of the track. I started working on this second idea but haven't successfully tested it out yet.
Diffstat (limited to 'src/quad.c')
0 files changed, 0 insertions, 0 deletions