Commit 90dd5936 authored by Morag Jean Williams's avatar Morag Jean Williams
Browse files

Changing use_cluster_centre default to 'false', and adding discussion to the...

Changing use_cluster_centre default to 'false', and adding discussion to the README file of DUTAssociation
parent 62a9b4ea
...@@ -8,7 +8,7 @@ DUTAssociation::DUTAssociation(Configuration config, std::shared_ptr<Detector> d ...@@ -8,7 +8,7 @@ DUTAssociation::DUTAssociation(Configuration config, std::shared_ptr<Detector> d
timingCut = m_config.get<double>("timing_cut", Units::get<double>(200, "ns")); timingCut = m_config.get<double>("timing_cut", Units::get<double>(200, "ns"));
spatialCut = m_config.get<XYVector>("spatial_cut", 2 * m_detector->pitch()); spatialCut = m_config.get<XYVector>("spatial_cut", 2 * m_detector->pitch());
useClusterCentre = m_config.get<bool>("use_cluster_centre", true); useClusterCentre = m_config.get<bool>("use_cluster_centre", false);
} }
void DUTAssociation::initialise() { void DUTAssociation::initialise() {
......
...@@ -15,7 +15,7 @@ This option can be chosen, e.g. for an efficiency analysis, when the cluster cen ...@@ -15,7 +15,7 @@ This option can be chosen, e.g. for an efficiency analysis, when the cluster cen
### Parameters ### Parameters
* `spatial_cut`: Maximum spatial distance in local coordinates in x- and y-direction allowed between cluster and track for association with the DUT. Expects two values for the two coordinates, defaults to twice the pixel pitch. * `spatial_cut`: Maximum spatial distance in local coordinates in x- and y-direction allowed between cluster and track for association with the DUT. Expects two values for the two coordinates, defaults to twice the pixel pitch.
* `timing_cut`: Maximum time difference allowed between cluster and track for association for the DUT. Default value is `200ns`. * `timing_cut`: Maximum time difference allowed between cluster and track for association for the DUT. Default value is `200ns`.
* `use_cluster_centre`: If set true, the cluster centre will be compared to the track position for the spatial cut. If false, the nearest pixel will be used. Defaults to `true`. * `use_cluster_centre`: If set true, the cluster centre will be compared to the track position for the spatial cut. If false, the nearest pixel in the cluster will be used. Defaults to `false`. When secondary particles are created in your detector, such as delta rays, the cluster centre position can be far away from the initial particle incidence point with the DUT. This impacts some measurements, for example measuring detector efficiencies as then DUT clusters from delta rays will not be associated to telescope tracks due to being outside the spatial cut, and the % efficiency measurement will decrease. A way to recover these delta rays and therefore the lost % efficiency is by comparing the closest pixel in the DUT cluster, rather than the cluster centre, to the track incidence position to determine association.
### Plots produced ### Plots produced
* distance in x of cluster centre to track minus closest pixel to track * distance in x of cluster centre to track minus closest pixel to track
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment