Bachelor Thesis Open Access
Tim Leidel
<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
<leader>00000nam##2200000uu#4500</leader>
<datafield tag="980" ind1=" " ind2=" ">
<subfield code="a">thesis</subfield>
<subfield code="b">bachelor-thesis</subfield>
</datafield>
<datafield tag="520" ind1=" " ind2=" ">
<subfield code="a"><p>Precision tracking of charged particles is a key ingredient for the physics programme of the Belle~II experiment at the SuperKEKB.<br>
In particular, decays in flight of charged kaons and pions, such as&nbsp;$K^{+} \to \mu^{+} \nu_\mu$ and $\pi^{+} \to \mu^{+} \nu_\mu$ and their charge conjugates, pose a challenge for standard track-finding algorithms.<br>
These tracks, hereafter referred to as tricky tracks, exhibit a kink topology with a change of momentum and direction at a displaced decay vertex.<br>
They are relevant for a range of flavour-physics and new-physics analyses, since a successful reconstruction leads to an improvement in the particle identification and $\text{d}E/\text{d}x$ calibration.<br>
A successful reconstruction of tricky tracks would also make new processes measurable.</p>
<p>This thesis studies the reconstruction of tricky tracks using the CDC AI Track Finder, called CATFinder, a graph neural network-based track-finding algorithm for the central drift chamber, and a dedicated configuration for tricky tracks.<br>
The focus is on kink topologies from $K^{+} \to \mu^{+} \nu_\mu$ and $\pi^{+} \to \mu^{+} \nu_\mu$ decays, where both the mother and daughter tracks are reconstructable in the central drift chamber.<br>
To this end, simulated Monte Carlo samples are used that combine realistic physics events with specialised particle-gun configurations.</p>
<p>On the algorithmic side, the CATFinder is extended with two additional binary classifiers trained to identify mother and daughter particles in tricky tracks.<br>
Three training strategies are explored that differ in the relative weight assigned to the new classifier terms in the loss function and in whether a pretraining phase is used without these terms.<br>
The performance of the resulting models is evaluated on prompt pion samples and mixed $B$ events.<br>
The evaluation considers general tracking metrics, kink-specific metrics, momentum resolution, hit-based metrics, and classifier-quality measures such as receiver operating characteristic curves.<br>
Comparing the training strategies provides insight into the trade-offs between generic tracking performance and specialised sensitivity to tricky tracks.</p></subfield>
</datafield>
<datafield tag="700" ind1=" " ind2=" ">
<subfield code="a">Torben Ferber</subfield>
<subfield code="u">KIT/ETP</subfield>
<subfield code="4">ths</subfield>
</datafield>
<datafield tag="700" ind1=" " ind2=" ">
<subfield code="a">Giacomo De Pietro</subfield>
<subfield code="u">KIT/ETP</subfield>
<subfield code="4">ths</subfield>
</datafield>
<datafield tag="245" ind1=" " ind2=" ">
<subfield code="a">Tricky Tracks with the CATFinder at Belle II</subfield>
</datafield>
<controlfield tag="001">22381</controlfield>
<controlfield tag="005">20260201100232.0</controlfield>
<datafield tag="856" ind1="4" ind2=" ">
<subfield code="s">3871857</subfield>
<subfield code="u">https://publish.etp.kit.edu/record/22381/files/Tricky_Tracks_with_the_CATFinder_at_Belle_II.pdf</subfield>
<subfield code="z">md5:6e26b9cf3d0e63b871334c8063846dd3</subfield>
</datafield>
<datafield tag="909" ind1="C" ind2="O">
<subfield code="o">oai:publish.etp.kit.edu:22381</subfield>
<subfield code="p">user-belle2</subfield>
<subfield code="p">user-etp</subfield>
</datafield>
<datafield tag="260" ind1=" " ind2=" ">
<subfield code="c">2025-12-11</subfield>
</datafield>
<datafield tag="041" ind1=" " ind2=" ">
<subfield code="a">eng</subfield>
</datafield>
<datafield tag="100" ind1=" " ind2=" ">
<subfield code="a">Tim Leidel</subfield>
<subfield code="u">KIT/ETP</subfield>
</datafield>
<datafield tag="542" ind1=" " ind2=" ">
<subfield code="l">open</subfield>
</datafield>
<datafield tag="980" ind1=" " ind2=" ">
<subfield code="a">user-belle2</subfield>
</datafield>
<datafield tag="980" ind1=" " ind2=" ">
<subfield code="a">user-etp</subfield>
</datafield>
</record>