GitLab

    - simplify checkNumPart
    - clean up function initDistInGlobalFrame
          - correct indentation
          - move AUTO mode stuff down where meanR is calculated already
    - referenceR is not used in Tracker_MTS body, so remove it

    - Needed to add member variables turnnumber_m, eta_m

cleanup: merge the duplicate code of LF2 and RK4into a function initDistInGlobleFrame(), not used in MTS tracker since units are different

    - Different splitting allows any positive integer for MTSSUBSTEPS option
    - Requires still one space charge solve per step, but one additional
      solve before main loop. Therefore, extract code to function
      evaluateSpaceCharge
    - TODO: correct location of bunch injection code?

    - Only for Tracker_LF and Tracker_MTS so far, Tracker_RK4 seems
      to contain different/additional logic. This should be clarified
      such that all trackers can use the same single particle dump
      code.
    - Initialization of trackOrbit-file done in initTrackOrbitFile
    - outf stream renamend to outfTrackOrbit_m, is now member variable
    - method singleParticleDump does the actual dump

- remove virtual functions from Component class which are specific for the Cyclotron class, then, in ParallelCyclotronTracker, cast pointers to instances of Component appropriately
- remove unrecognised escape character

    - Additional method ParallelCyclotronTracker::Tracker_MTS
    - If successfully tested, it should replace Tracker_LF
    - Detailed description and sample input file will follow
    - Brief usage guide:
        - Use 'TIMEINTEGRATOR="MTS"' instead of 'TIMEINTEGRATOR="LF-2"'
        - The outer, large step is for integration of space charge, the substeps
          for everything else.
        - Define number of substeps per step with 'Option, MTSSUBSTEPS=10;'.
          This must be an even number >= 2.
        - The input file has to be rewritten in units of the large step, so
          divide STEPSPERTURN, PSDUMPFREQ (and others) by MTSSUBSTEPS to
          maintain similar behaviour.
        - MTSSUBSTEPS and SCSOLVEFREQ both describe the frequency of space
          charge solves compared to the basic step. However, MTSSUBSTEPS
          can be chosen larger while maintaining accuracy. Try it :-)