Merge branch 'b-1073' into 'v3.0-stable'

        - export PATH=~/.local/bin:$PATH

        - cd ../

        - pip install --trusted-host=pypi.org --user codespell

        - codespell --ignore-words .gitlab/ci/codespell_ignored_words.txt --quiet-level 2 --skip ".git,.gitlab,cmake,3rdparty"

        - codespell --ignore-words .gitlab/ci/codespell_ignored_words.txt --quiet-level 2 --skip ".git,.gitlab,cmake,3rdparty,AUTHORS.md"

fmt:proselint:

    extends: .format

possible to reset the ROOT-internal object ID of `TRef` references after the event has been processed. The subsequent event will 

reuse the same IDs again, preventing a continuous growth of the reference table and related memory re-allocation issues.

As a consequence, when reading objects back from file in a mutlithreaded environment, the `TRef` has to be converted back to a C

As a consequence, when reading objects back from file in a multithreaded environment, the `TRef` has to be converted back to a C

memory pointer in the reading thread, both to prevent mixing of re-used `TRef` object IDs from different events and to avoid 

locking access to the central reference table when looking up the memory location from there. This is performed similarly to the 

generation of history relations, and here only relations to valid TRefs are loaded, other relations will hold a `nullptr`:

Owing to its modular structure, the functionality of the Allpix Squared can easily be extended by adding additional modules

which can be placed in the simulation chain. Since the framework serves a wide community, modules should be as generic as

possible, i.e. not only serve the simulation of a single detector prototype but implement the necessary algorithms such that

they are re-usable for other applications. Furthermore, it may be beneficial to split up modules to support the modular

they are reusable for other applications. Furthermore, it may be beneficial to split up modules to support the modular

design of Allpix Squared.

Before starting the development of a new module, it is essential to carefully read the documentation of the framework module

         * @brief Get center of the chip in local coordinates

         * @return Center of the chip

         *

         * Center of the chip calculcated from chip excess and sensor offset

         * Center of the chip calculated from chip excess and sensor offset

         */

        virtual ROOT::Math::XYZPoint getChipCenter() const {

            ROOT::Math::XYZVector offset(assembly_->getChipOffset().x() / 2.0,

namespace allpix {

    /**

     * @ingroup Objects

     * @brief Flags to distinguish between eletron and hole charge carriers

     * @brief Flags to distinguish between electron and hole charge carriers

     */

    enum class CarrierType : int8_t { ELECTRON = -1, HOLE = 1 };