Time-Resolved Fluorescence Wiki

antibunching_measurements

Anonymous (anonymous@undisclosed.example.com) — 2025-04-09T14:01:09+00:00

2025/04/09 16:00		current
Line 5:		Line 5:
	====== How to Perform Antibunching Measurements ======		====== How to Perform Antibunching Measurements ======

-	Antibunching Measurements are (normally) measured in T2 mode. In T2 mode, all input channels of the TCSPC electronics are treated the same, also the "Sync" channel. Therefore the sync has to be disabled either by disconneting the cable, or by changing the CFD level or trigger level to such a value that the sync is not recognized any more. i.e. Sync rate = 0 . Directly in the Sepia software, the sync out can also be disabled.	+	Antibunching Measurements are (normally) measured in T2 mode. In T2 mode, all input channels of the TCSPC electronics are treated the same, also the "Sync" channel. Therefore the sync has to be disabled either by disconneting the cable, or by changing the CFD level or trigger level to such a value that the sync is not recognized any more. i.e. Sync rate = 0 . Directly in the Sepia software, the sync out can also be disabled.

	The descriptions below only mention physically disconnecting the sync. This is strictly necessary only for the PicoHarp 300 because it only has two channels.		The descriptions below only mention physically disconnecting the sync. This is strictly necessary only for the PicoHarp 300 because it only has two channels.

Anonymous (anonymous@undisclosed.example.com) — 2015-02-10T16:27:57+00:00

2015/02/10 17:27		current
Line 12:		Line 12:
	- the arrival time of the event pair on the overall experiment time scale (the time tag).		- the arrival time of the event pair on the overall experiment time scale (the time tag).

-	The latter was originally obtained from an independent asynchronous clock. This made it difficult to combine the start-stop timing with the time tag or to know the sync period the event belonged to. For the PicoHarp's T3 Mode a smarter approach was chosen:\\	+	The latter was originally obtained from an independent asynchronous clock. This made it difficult to combine the start-stop timing with the time tag or to know the sync period the event belonged to. For the *Harp's T3 Mode a smarter approach was chosen:\\
	The time tag is now obtained by simply counting sync pulses. From the T3 Mode event records it is therefore possible to precisely determine which sync period a photon event belongs to. Since the sync period is also known precisely, this furthermore allows to reconstruct the arrival time of the photon with respect to the overall experiment time.		The time tag is now obtained by simply counting sync pulses. From the T3 Mode event records it is therefore possible to precisely determine which sync period a photon event belongs to. Since the sync period is also known precisely, this furthermore allows to reconstruct the arrival time of the photon with respect to the overall experiment time.

Anonymous (anonymous@undisclosed.example.com) — 2020-09-14T16:01:28+00:00

2020/09/14 18:01		current
Line 31:		Line 31:
	* PI Controller: E725		* PI Controller: E725
	* PI Controller: E710 \\		* PI Controller: E710 \\
-	* Controller: E727 \\	+	* PI Controller: E727 \\
	* Controller: C867.2U2 (PI wide range scanner)		* Controller: C867.2U2 (PI wide range scanner)
	* Controller: C867.262 (PI wide range scanner)		* Controller: C867.262 (PI wide range scanner)

Anonymous (anonymous@undisclosed.example.com) — 2023-02-17T12:44:38+00:00

2023/02/17 13:44		current
Line 1:		Line 1:
-	{{tag>SymPhoTime MicroTime200 MicroTime100 Scanner PI Physik_Instrumente E725 E710 MadCityLabs Mad_City_Labs PC}}	+	{{tag>SymPhoTime MicroTime200 Scanner PI Physik_Instrumente E725 E710 MadCityLabs Mad_City_Labs PC}}
	~~TOC~~		~~TOC~~