GitLab

Correctly handle multiple degraders and multiple degraders that follow each other, min particles per core set back to 0

Workaround to run the degrader and not break the regressiontests. This is TEMPORARLY until we have understood the problem and At THE SAME TIME satisfy our users

- emitSecondaryFurmanPivi(): interface changed

- adapted to changed interface of BoundaryGeometry::emitSecondaryVaughan()
- whitespace changes

This reverts commit 90dc2956.

- Expressions: adding error function
- LossDataSink: we are using git
- OpalBeamline: let Autophase tracker smoothly (i.e. don't throw a segmentation fault) even if there are no cavities
- ParallelTTracker: don't save phase space after last step if saved at end of last step

- fix bug in collection of all sections with surface physics - slightly improve performance of CollimatorPhysics::deleteParticleFromLocalVector()

- OpalParallelPlate: initialize boundary geometry to NULL
- BoundaryGeometry: initialize timers before we use them

- new laser profile class with automatic detection of center of mass of profile and possiblity to flip and rotate

CMakeLists fix for Intel compiler + DKS, ParaleTTracker DKS update for numparticlesinsimulation after material

better update for variable numParticlesInSimulation_m which works for gun simulations as well as Monte Carlo simulations in degraders on GPUs

    - fixing number of particles when the numbers don't add up to the total due to rounding errors;
    - clean up: rename files to comply with coding guide lines;
    - improve message when field of bend overlapps;
    - warning is emitted if too few fourier coefficients are used to filter the field map;

fixing restart: can now (again) restart from any step in any H5Part file that was written for/with OPAL; SDDS file and load balance file are rewound to an s-position less or equal as in the H5file