{{tag> pile-up dead_time IRF differential_countrate}}
====== Differential Count Rate ======
Ideally, a... y (probability of encountering a photon) during a time interval when a detected signal is really present... the detector bunched, as flashes. These are short time intervals with huge photon density (rate), separa... rate" is a result of **sparse sampling with dead time**. The sampled signal features much higher photon
{{tag> TCSPC pile-up dead_time}}
~~TOC~~
====== Pile-Up Effect ======
The Pile-Up effect describes the ... s lost at high photon count rates due to the dead time of the TCSPC devices.
Most single photon counti... detectors and [[TCSPC]] electronics have a [[dead time]]. After registering one photon the device needs some time to be ready for the next photon to detect. The de
====== Dead Time ======
In TCSPC the term dead time refers to the time the TCSPC system needs armed again after detecting an event. During the dead time the TCSPC system is blind.
If for example two p
====== TTTR ======
TTTR stands for Time-Tagged Time-Resolved. The basic concept of this measurement mode is to record every individual photon of a [[TCSPC]] experiment. Both the arrival time as well as the TCSPC timing information (i.e. the time from the preceding excitation pulse or to the fol
thods afterwards. Usually a burst is defined as a time interval for which the intensity of a time trace or [[MCS]] measurement is above a chosen threshold. Ev
=== T3-mode ======
(derived from [[tttr]]-mode or Time-Tagged-Time-Resolved mode)
A special measurement mode of the [[products:PicoHarp 300]], [[products:HydraHarp 400]] and [[products:TimeHarp 260]].
In T3 Mode input channel 0 is dedicat... reduces the sync rate so that the channel [[dead time]] is no longer a problem.
* The remaining prob
300]], [[Products:HydraHarp 400]] and [[Products:TimeHarp 260]]
In T2 Mode both signal inputs of the... on about the channel it came from and the arrival time of the event with respect to the overall measurem... 4 bits for the channel number and 28 bits for the time-tag. Routing is not supported. If the time tag overflows, a special overflow marker record is inserted