aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-11-18add a new test for the quad fittertlatorre
This commit adds a new test to test the quad fitter when the t0 quantile argument is less than 1.
2019-11-18clear any flags except for PMT_FLAG_DQXX in get_event()tlatorre
This commit updates get_event() to clear any PMT flags except for PMT_FLAG_DQXX from all PMT hits before loading the event. Although I *was* previously clearing the other flags for hit PMTs, I was not clearing flags for PMTs which were *not* hit. This was causing non deterministic behaviour, i.e. I was getting different results depending on if I ran the fitter over a whole file or just a single event.
2019-11-18switch to using pt1 instead of the ptmtlatorre
This commit updates the likelihood function to use the PMT hit time without the time walk correction applied (when the charge is greater than 1.5 PE) instead of the multiphoton PCA time. The reason is that after talking with Chris Kyba I realized that the multiphoton PCA time was calibrated to give the mean PMT hit time when mulitiple photons hit at the same time instead of the time when the first photon hits which is what I assume in my likelihood function. Therefore I now use the regular PMT hit time without time walk correction applied which should be closer to the first order statistic.
2019-11-18switch to using twice the PSUP reflection time for the time PDFtlatorre
2019-11-18initialize mu_indirect to 0tlatorre
This commit updates the likelihood function to initialize mu_indirect to 0.0 since it's a static array. This can have an impact when the fit position is outside of the PSUP and we skip calculating the charges.
2019-11-18fix bug due to roundoff error in get_{delta_ray,shower}_weights()tlatorre
2019-11-18add nhit_cal to the HDF5 filetlatorre
2019-11-18size_t -> int in is_slot_early()tlatorre
This commit updates the crate, card, and channel variables in is_slot_early() to be ints instead of size_ts. The reason is I saw a warning when building with clang and realized that the abs(card - flasher_card) == 1 check wasn't working if flasher_card was 1 greater than card because I was using unsigned ints.
2019-11-18fix bug in quad causing it to always return 0 when f was less than 1tlatorre
2019-11-06add a couple of improvements to the quad fitter and fix a bug in ↵tlatorre
get_hough_transform() This commit adds two improvements to the quad fitter: 1. I updated quad to weight the random PMT hit selection by the probability that the PMT hit is a multiphoton hit. The idea here is that we really only want to sample direct light and for high energy events the reflected and scattered light is usually single photon. 2. I added an option to quad to only use points in the quad cloud which are below a given quantile of t0. The idea here is that for particles like muons which travel more than a few centimeters in the detector the quad cloud usually looks like the whole track. Since we want the QUAD fitter to find the position of the *start* of the track we select only those quad cloud points with an early time so the position is closer to the position of the start of the track. Also, I fixed a major bug in get_hough_transform() in which I was using the wrong index variable when checking if a PMT was not flagged, a normal PMT, and was hit. This was causing the algorithm to completely miss finding more than one ring while I was testing it.
2019-11-05update README to include python packages required for python scriptstlatorre
2019-11-05update guess_energy()tlatorre
This commit updates guess_energy() which is used to seed the energy for the likelihood fit. Previously we estimated the energy by summing up the charge in a 42 degree cone around the proposed direction and then dividing that by 6 (since electrons in SNO and SNO+ produce approximately 6 hits/MeV). Now, guess_energy() estimates the energy by calculating the expected number of photons produced from Cerenkov light, EM showers, and delta rays for a given particle at a given energy. The most likely energy is found by bisecting the difference between the expected number of photons and the observed charge to find when they are equal. This improves things dramatically for cosmic muons which have energies of ~200 GeV. Previously the initial guess was always very low (~1 GeV) and the fit could take > 1 hour to increase the energy.
2019-10-21add appendix about the combination of poisson and binomial random variablestlatorre
2019-10-12switch to book document classtlatorre
2019-10-12move sddm.tex to doc/tlatorre
2019-10-12add a section about the backgroundstlatorre
2019-10-12first draft of my thesistlatorre
2019-10-05fix typo in plot-energytlatorre
2019-09-30fix a SettingWithCopyWarning in plot-energytlatorre
2019-09-30update flasher cut to only check for normal PMTstlatorre
2019-09-30update flasher cuttlatorre
This commit updates the flasher cut to flag events in which the PMT with the highest pedestal subtracted QLX charge is 80 counts above the next highest QLX charge, has at least 4 hits in the same slot, and passes the final check in the flasher cut (70% of the normal PMT hits must be 50 ns after the high charge channel and 70% of the normal PMT hits must be at least 12 meters away from the high charge channel). This update was motivated by run 20062 GTID 818162. This was a flasher event but which had only 3 hits in the PC and so passed the previous version of the cut. This new update was inspired by the SNO QvT cut.
2019-09-30update plot-energy to sort events by GTIDtlatorre
2019-09-30write out run header info to the hdf5 filetlatorre
2019-09-27update the flasher cuttlatorre
This commit updates the flasher cut with the following changes: - no longer require nhit to be less than 1000 - update charge criteria to be that the flasher channel must have a QHS or QHL 1000 counts above the next highest QHS or QHL value in the PC or a QLX value 80 counts above the next highest QLX value - only check is_slot_early() for missing hits in the PC These updates were inspired by looking at how to tag flashers in runs 20062 - 20370 which didn't fail the original cut. In particular, the following flashers were previously not tagged: Run GTID Comments --- ---- -------- 20062 818162 flasher with only 3 hits in PC reconstructs at PSUP ESUMH triggered 20083 120836 high charge missing (in next couple of events) probably picked wrong flasher PMT ID 20089 454156 nhit > 1000 After this commit the last two are properly tagged.
2019-09-26update QVNHIT cuttlatorre
This commit updates the QvNHIT cut to not require PMT hits to have a good calibration to be included in the charge sum. The reason for this is that many electrical pickup events have lots of hits which are pickup and thus have small or negative charges. When the charge is low like this the PMT hits get flagged with the bad calibration bit (I'm not sure if it's because of the PMT charge walk calibration or what). Therefore, now we include all hit PMTs in the charge sum if there ECA calibrated QHL value is above -100.
2019-09-25update zdab-reprocess to be faster and run FTP and RSPtlatorre
This commit updates the zdab-reprocess script with the following changes: - don't run RAA - don't run a bunch of the other fitters like FTI, etc. - run the path and RSP fitters - add --lower-nhit and --upper-nhit command line arguments to control the primary nhit cut range
2019-09-25fix another small bug in zdab-reprocesstlatorre
2019-09-24fix bugs introduced into zdab-reprocess in commit 1e35deatlatorre
2019-09-24update zebra code to store location of MAST banktlatorre
This commit updates the zebra code to store a pointer to the first MAST bank in the zebraFile struct so that we can jump to it when iterating over the logical records. I had naively assumed based on the documenation in the SNOMAN companion that the first bank in a logical record was guaranteed to be a MAST bank, but that doesn't seem to be the case. This also explains why I was sometimes seeing RHDR and ZDAB banks as the first bank in a logical record.
2019-09-24update zdab-reprocess to be able to handle more filenamestlatorre
2019-09-24update breakdown cut to include a cut on the number of calibrated PMT hitstlatorre
This commit updates the breakdown cut to flag any event in which less than 70% of the PMT hits have a good TAC value.
2019-09-24update shower position distribution parameters for muonstlatorre
This commit updates the a and b parameters for the gamma distribution used to describe the position distribution of shower photons produced along the direction of the muon. Previously I had been assuming b was equal to the radiation length and using a formula from the PDG to calculate a from that. However, this formula doesn't seem to be valid for muons (the formula comes from a section describing the shower profile of electrons and gammas, so it's not surprising). Therefore, now we don't assume any relationship between a and b. Now, the value of a is approximated by a constant since I couldn't find any functional relationship as a function of energy to describe a very well (and it's approximately constant), and b is approximated by a single degree polynomial fit to the values I got from simulating muons in RAT-PAC as a function of energy. Note that looking at the simulation data it seems like the position distribution of shower photons from muons isn't even very well described by a gamma distribution, so in the future it might be a good idea to come up with a better parameterization. Even if I stick with the gamma distribution, it would be good to revisit this in the future and fit for a and b over a wider range of energies.
2019-09-23select prompt events before data cleaning cutstlatorre
This commit updates plot-energy to select prompt events before applying the data cleaning cuts. This fixes an issue where we might accidentally classify an event as a prompt event even if it came after an event that was flagged by data cleaning. For example, suppose there was a breakdown but for whatever reason the event immediately after the breakdown wasn't tagged (ignoring the fact that we apply a breakdown follower cut). If we apply the data cleaning first and then the prompt event selection, that event would be a part of the prompt events. There are several other small updates to plot-energy: - fix bug in 00-orphan cut - make michel event selection a separate function - make atmospheric tag into a separate function
2019-09-23add sub_run variable to the events array in the HDF5 filetlatorre
This commit adds the sub_run variable to the ev array in the HDF5 output file and updates plot-energy to order the events using the run and sub_run variables. This fixes a potential issue where I was sorting by GTID before, but the GTID can wrap around and so isn't guaranteed to put the events in the right order.
2019-09-23add the 00-orphan cut to plot-energytlatorre
2019-09-23update the ITC cut to use pt1 timetlatorre
This commit updates the ITC cut to use the pt1 time which is the ECA + PCA without charge walk calibration time. The reason is that an event which is mostly electronics noise may have all low charges which can't be calibrated with the PCA walk calibration.
2019-09-21update definition of nhittlatorre
This commit updates the ev.nhit variable to represent the total number of normal PMTs hit in the event, regardless of if the calibration failed. I added a new variable ev.nhit_cal which now stores the total number of normal PMTs hit without any flags.
2019-09-10add best_uncal_q to the pmt_hit struct and use it in the muon cuttlatorre
This commit adds a field to the pmt_hit struct called best_uncal_q which represents the best ECA calibrated charge (in units of QHS counts above pedestals). This is then used in the muon data cleaning cut.
2019-09-09add retrigger, flasher follower, and breakdown follower cuts to plot-energytlatorre
2019-09-09fix typo in is_slot_earlytlatorre
2019-09-09update muon cuttlatorre
This commit updates the muon cut to require at least 1 OWL hit which has a high charge and is early relative to nearby normal PMTs. This replaces the previous cut criteria which required 2 OWL hits to be early relative to the 10% percentile of all the normal PMT hits. This new cut should target external muons better although I still need to do some testing. In the future I'd like to optimize the distance at which PMTs are considered nearby. Currently I just use 3 meters which seemed like a good value based on some initial testing.
2019-09-09update READMEtlatorre
2019-09-09update fit to allow t0 to be negativetlatorre
2019-09-09fix a gcc warningtlatorre
2019-09-09update is_slot_early() to hopefully catch more flasherstlatorre
This commit updates is_slot_early() to do the following: - use median time when checking to see if the time of the PMT hits in the slot is early relative to nearby PMTs - return True if the number of nearby PMTs is less than or equal to the number of hit PMTs in the potential flasher slot - skip potential cross talk hits when finding the nearby hit PMTs by skipping hits in the adjacent slots with the same paddle card as the potential flasher
2019-09-09add a first draft of a data cleaning cut to detect breakdown eventstlatorre
2019-09-09add math header file to zdab_utils.c for fmin() and fmax()tlatorre
2019-09-09update get_event() to use the PMT types from the snoman.ratdb filetlatorre
This commit updates get_event() to assume the PMT type is correct in the pmt.txt file instead of assuming the SNOMAN bank is correct. The reason for this is that according to the email from Stan 3/15/9 should be a neck PMT (at least in the NCD phase) and that is what the pmt.txt file says it should be. In addition, the changes that Stan said were needed in ccc_type.for never got made.
2019-09-09use EHS instead of QHS in is_muon()tlatorre
This commit updates is_muon() to use the EHS charge for the OWL tubes since based on looking at the charges for the OWL tubes it looks like the QHS values are completely random.
2019-09-09lower QLX threshold from 4000 -> 1000 in is_flashertlatorre