GitLab

ParallelTTracker. Particle-Matter interaction doesn't work either at the moment.

I hope that I didn't create too much of a mess when merging!

allow 0 in dump frequency (frequ is maxint) and supress h5 writes of number of partcles are 1 and 2 in OPAL_cycl

- DataSink::writeSurfaceInteraction(): cast H5_ERR if compared to variable of type h5_file_t

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

    - 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;

std::regex does not seem to work properly on merlin; switching to boost::regex; don't write to H5 file if there are no particles in the bunch

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

in sdds file: make sure that the data fits to the type given in the header; here the parameter 'processors' is declared long, but string was given

Brought back saving in local frame for cyclotron tracker. Reverted the way mean E is calculated in PartBunch. Hopefully, restarts in local as well as in global frame now work in the cyclotron tracker.

- moving the following classes over from OPAL to CLASSIC
  o OpalField       -> ClassicField
  o OpalRing        -> Ring
  o OpalRingSection -> RingSection
  o LossDataSink
- clean up
- splitting Options into classic and opal options

This allows to specify collimator losses as an objective. CHK wrote the original part, I did 
minor modifications. I tested with BeamLine-1 from the regressiontests so far only with one core.
 

- putting own header file first
  o for reason see http://www.cplusplus.com/forum/articles/10627/#msg49679 and
                   http://www.cplusplus.com/forum/articles/10627/#msg49680