diff options
| author | tlatorre <tlatorre@uchicago.edu> | 2019-07-29 12:18:40 -0500 |
|---|---|---|
| committer | tlatorre <tlatorre@uchicago.edu> | 2019-07-29 12:18:40 -0500 |
| commit | ebc0f100371942e99c433cf967b55524a9765c87 (patch) | |
| tree | 076b08ec2415bbdae435e1cb340cec2b50315e70 /src/event.h | |
| parent | bfa4b698787d780c3fe0ad8b1b9a54a60db64467 (diff) | |
| download | sddm-ebc0f100371942e99c433cf967b55524a9765c87.tar.gz sddm-ebc0f100371942e99c433cf967b55524a9765c87.tar.bz2 sddm-ebc0f100371942e99c433cf967b55524a9765c87.zip | |
switch to using the multiphoton PCA time
This commit updates the likelihood to use the multiphoton PCA time instead of
the usual pt time. When looking at the reconstruction of muons in run 10,000 I
noticed that the PMT hit times for the PMTs which had really high charge was
all over the place. There were PMTs that were very close to each other with hit
times differing by ~ 20 ns. I'm still not entirely sure what causes this (is
it some hardware issue with the discriminator or is it a problem with the
charge walk correction which always assumes a single PE?), but the multiphoton
PCA times looked a lot more reasonable.
Eventually I need to look into the ptms variable which is the multiphoton PCA
transit time RMS.
Diffstat (limited to 'src/event.h')
| -rw-r--r-- | src/event.h | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/src/event.h b/src/event.h index 4ebb14c..ddb8be3 100644 --- a/src/event.h +++ b/src/event.h @@ -61,6 +61,10 @@ typedef struct pmt_hit { int pf; /* Non-walk corrected PMT time. */ float pt1; + /* Time in nano-secs relative to event T0. */ + float pt; + /* Multiphoton PCA time. */ + float ptm; } pmt_hit; typedef struct event { |