sddm/src, branch master

update code to work with python3

2020-11-30T22:15:26+00:00

This commit updates the python code to work with python 3 and with a
newer version of matplotlib.

- zip_longest -> izip_longest
- fix tick marks for log plots
- scipy.misc -> scipy.special

update fit to fit events from the salt phase

2020-11-16T16:05:25+00:00

This commit updates both the PMT response and optics code to be able to
load constants from the salt phase.

add jdy, ut1, ut2, dte, and hmsc to hdf5 output file

2020-11-16T14:36:23+00:00

update qhl ratio

2020-11-02T00:17:14+00:00

update neck cut

2020-06-22T13:41:48+00:00

This commit updates the neck cut to increase the number of neck PMT hits even
if the neck PMT hit time isn't calibrated correctly. This is because I was
looking at all muon events which didn't have an NHIT trigger fire and I noticed
the following events:

Run    GTID
----   ----
10036  1462054
10040  2270713
10133  1096180

They all appear to be neck events, but the first one in particular has 4 neck
PMTs that got hit. When looking into it I realized that all 4 hits had ept
times of -9999.

several events:

delete an empty line in e_water_liquid.txt

2020-05-11T15:33:55+00:00

extend electron range tables up to 1 TeV

2020-04-14T17:01:43+00:00

fit for up to 5 peaks

2020-04-13T17:00:30+00:00

This commit updates fit.c to start with 5 peaks for the direction seeds. I
chose this number because I did some testing with the test-find-peaks program
on the atmospheric MC and it looks like 5 peaks were necessary to capture the
majority of the peaks.

update fit to fit each event twice with different quad quantiles

2020-04-13T16:57:15+00:00

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.

update find_peaks algorithm

2020-04-13T16:40:13+00:00

This commit updates the find peaks algorithm with several improvements which
together drastically improve its ability to find Cerenkov rings:

- when computing the Hough transform, instead of charge we weight each PMT hit
  by the probability that it is a multi-photon PMT hit
- we don't subtract off previously found rings (this makes the code simpler and
  I don't think it previously had a huge effect)
- ignore PMT hits who are within approximately 5 degrees of any previously
  found ring (previously we ignored all hits within the center of previously
  found rings)
- ignore PMT hits which have a time residual of more than 10 nanoseconds to
  hopefully ignore more reflected and/or scattered light
- switch from weighting the Hough transform by exp(-fabs(cos(theta)-1/n)/0.1)
  -> exp(-pow(cos(theta)-1/n,2)/0.01). I'm still not sure if this has a huge
  effect, but the reason I switched is that the PDF for Cerenkov light looks
  closer to the second form.
- switch to calling quad with f = 1.0 in test-find-peaks (I still need to add
  this update to fit.c but will do that in a later commit).