src issueshttps://gitlab.psi.ch/OPAL/src/-/issues2021-06-10T17:47:02+02:00https://gitlab.psi.ch/OPAL/src/-/issues/562General elements for electrostatitic and magnetostatic fields2021-06-10T17:47:02+02:00krausGeneral elements for electrostatitic and magnetostatic fields### Summary
Currently not every element can be modeled with a specific element in Opal. Instead one has to use 3D field maps and either a solenoid (only for magneto static fields) or an rf cavity. This isn't very intuitive. Instead we c...### Summary
Currently not every element can be modeled with a specific element in Opal. Instead one has to use 3D field maps and either a solenoid (only for magneto static fields) or an rf cavity. This isn't very intuitive. Instead we could provide "blank" elements for the general case, e.g. GENERALELECTROSTATIC and GENERALMAGNETOSTATIC.https://gitlab.psi.ch/OPAL/src/-/issues/606Container support2021-06-10T17:42:42+02:00bellotti_rContainer supportI suggest to provide container images for OPAL. It is quite complicated to build it, and requires running specific scripts in a specific order. On the other hand, pulling (or building) an image is just one command. The system agnostic ap...I suggest to provide container images for OPAL. It is quite complicated to build it, and requires running specific scripts in a specific order. On the other hand, pulling (or building) an image is just one command. The system agnostic approach circumvents problems when clusters provide different versions of the dependencies, or change them.https://gitlab.psi.ch/OPAL/src/-/issues/613Remove unused attributes and add TRANSPARENT to opal.el2021-06-10T17:40:29+02:00krausRemove unused attributes and add TRANSPARENT to opal.elIn OpalCavity and OpalTravelingwave there are a few attributes that aren't used anymore:
- BETRF
- CAVITYTYPE
- HARMON
- PG
- SHUNT
- TFILL
They should be removed. Additionally TRANSPARENT is missing in opal.elIn OpalCavity and OpalTravelingwave there are a few attributes that aren't used anymore:
- BETRF
- CAVITYTYPE
- HARMON
- PG
- SHUNT
- TFILL
They should be removed. Additionally TRANSPARENT is missing in opal.elOPAL 2021.1krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/653Octupole magnet strengths are set using the formula for Decapoles2021-06-10T10:07:15+02:00adelmannOctupole magnet strengths are set using the formula for Decapoles### Summary
In the course of trying to get Opal to agree with another code, Finn O'Shea discovered that the normal component of the octupole strength
is set using the formula for decapoles. Line 114 of Multipole.cpp shows that the OCT...### Summary
In the course of trying to get Opal to agree with another code, Finn O'Shea discovered that the normal component of the octupole strength
is set using the formula for decapoles. Line 114 of Multipole.cpp shows that the OCTUPOLE case is combined with the DECAPOLE case:
### Steps to reproduce
will ask for input file(s)
### What is the current *bug* behavior?
OCTUPOLE behaves like a DECAPOLE, see also the attached file with the trace win "reference" solution, provided by Finn O'Shea.
### What is the expected *correct* behavior?
see below
### Relevant logs and/or screenshots
```
case OCTUPOLE:
case DECAPOLE:
NormalComponents[n - 1] = (v + vError) / 24;
NormalComponentErrors[n - 1] = vError / 24;
break;
```
### Possible fixes
```
case OCTUPOLE:
NormalComponents[n - 1] = (v + vError) / 6;
NormalComponentErrors[n - 1] = vError / 6;
break;
case DECAPOLE:
NormalComponents[n - 1] = (v + vError) / 24;
NormalComponentErrors[n - 1] = vError / 24;
break;
```
[octupoles.tar.gz](/uploads/6cb3061fbe6619e5563a275bf3eb1fca/octupoles.tar.gz)OPAL 2021.1snuverink_jjochem.snuverink@psi.chsnuverink_jjochem.snuverink@psi.chhttps://gitlab.psi.ch/OPAL/src/-/issues/574P3M solver declaration is missing2021-05-26T12:54:27+02:00ext-calvo_ppedro.calvo@ciemat.esP3M solver declaration is missingP3M solver is missing as FieldSolver type (`FSTYPE`) in FieldSolver.cpp. In addition, it is not documented in the manual (OPAL/documentation/manual#41)P3M solver is missing as FieldSolver type (`FSTYPE`) in FieldSolver.cpp. In addition, it is not documented in the manual (OPAL/documentation/manual#41)OPAL-3.0https://gitlab.psi.ch/OPAL/src/-/issues/651Printing info of DumpFields and DumpEMFields2021-05-11T10:45:39+02:00ext-calvo_ppedro.calvo@ciemat.esPrinting info of DumpFields and DumpEMFieldsDumpFields and DumpEMFields statements must print information about their attributes to stdout.DumpFields and DumpEMFields statements must print information about their attributes to stdout.OPAL 2021.1ext-calvo_ppedro.calvo@ciemat.esext-calvo_ppedro.calvo@ciemat.eshttps://gitlab.psi.ch/OPAL/src/-/issues/475Formula momentum conversion2021-04-23T17:10:39+02:00albajacas_aarnau.albajacas@psi.chFormula momentum conversion* [x] Add two functions to Utilities/Util
* [x] Update documentation
### Summary
I'm not sure if this is a bug, but I don't understand the formula used to convert P [eV/c] to $`\beta\gamma`$ [dimensionless] in the function [`Distribut...* [x] Add two functions to Utilities/Util
* [x] Update documentation
### Summary
I'm not sure if this is a bug, but I don't understand the formula used to convert P [eV/c] to $`\beta\gamma`$ [dimensionless] in the function [`Distribution::converteVToBetaGamma`](https://gitlab.psi.ch/OPAL/src/blob/master/src/Distribution/Distribution.cpp#L904):
```math
(\beta_x\gamma)=\sqrt{(\frac{P_x[{eV/c}]}{m_0c}+1)^2-1}.
```
If the user gives momentum in eV/c, I would imagine that the conversion should be
```math
\gamma\beta_x = \frac{P_xc}{mc^2}.
```
If it's not a bug then I think it should be better explained in the manual.OPAL 2.4.0albajacas_aarnau.albajacas@psi.chalbajacas_aarnau.albajacas@psi.ch2020-07-24https://gitlab.psi.ch/OPAL/src/-/issues/647Add option to write VTK file2021-04-23T11:25:53+02:00ext-calvo_ppedro.calvo@ciemat.esAdd option to write VTK fileWriting the VTK file of the voxel mesh increases the time consumption. To speed up boundary geometry initialization I propose to add an option to disable VTK files. In addition, as @gsell suggested, VTK files should only be written if th...Writing the VTK file of the voxel mesh increases the time consumption. To speed up boundary geometry initialization I propose to add an option to disable VTK files. In addition, as @gsell suggested, VTK files should only be written if they do not exist or are older than the geometry file.OPAL 2021.1ext-calvo_ppedro.calvo@ciemat.esext-calvo_ppedro.calvo@ciemat.eshttps://gitlab.psi.ch/OPAL/src/-/issues/634Reviewing physics behind particle matter interaction models2021-04-23T11:25:39+02:00ext-calvo_ppedro.calvo@ciemat.esReviewing physics behind particle matter interaction models- Extend the energy loss calculation and beam scattering for other incoming heavy ions. It is currently only valid for protons
- Add energy loss at very low energy region (1-10 keV) (see ICRU Report 49)
- Document stopping power at Ander...- Extend the energy loss calculation and beam scattering for other incoming heavy ions. It is currently only valid for protons
- Add energy loss at very low energy region (1-10 keV) (see ICRU Report 49)
- Document stopping power at Anderson-Ziegler region
- Update atomic weight of materials according to [database 2019](https://www.qmul.ac.uk/sbcs/iupac/AtWt/) and other [material properties](https://pdg.lbl.gov/2020/AtomicNuclearProperties/)
- Add alpha particle beams
- Review energy threshold for stripper gas interactionsOPAL 2021.1ext-calvo_ppedro.calvo@ciemat.esext-calvo_ppedro.calvo@ciemat.eshttps://gitlab.psi.ch/OPAL/src/-/issues/648File header for BasicActions classes2021-04-22T15:31:14+02:00ext-calvo_ppedro.calvo@ciemat.esFile header for BasicActions classesThis issue fixes the coding style and adds the file header for BasicActions classesThis issue fixes the coding style and adds the file header for BasicActions classesOPAL 2021.1ext-calvo_ppedro.calvo@ciemat.esext-calvo_ppedro.calvo@ciemat.eshttps://gitlab.psi.ch/OPAL/src/-/issues/646Extend the list of symbolic constant2021-04-16T09:57:33+02:00ext-calvo_ppedro.calvo@ciemat.esExtend the list of symbolic constantThe physical constants recognized by OPAL must include all the particle masses defined in the `Beam` command. This prevents the user from defining a value for the mass that differs from the value considered internally by OPAL.
- [x] Def...The physical constants recognized by OPAL must include all the particle masses defined in the `Beam` command. This prevents the user from defining a value for the mass that differs from the value considered internally by OPAL.
- [x] Define masses as standard constants (see !487)
- [x] Update documentation (see OPAL/documentation/manual!124)OPAL 2021.1ext-calvo_ppedro.calvo@ciemat.esext-calvo_ppedro.calvo@ciemat.eshttps://gitlab.psi.ch/OPAL/src/-/issues/645Fix turnNumber in loss output file2021-04-06T09:21:34+02:00ext-calvo_ppedro.calvo@ciemat.esFix turnNumber in loss output fileAfter implementing OPAL/src#503, loss files in ASCII format is not considering `turnNumber` info when simulations are performed in parallel environment unless all nodes has particles.
`hasTurnInformations()` could be modified to fix itAfter implementing OPAL/src#503, loss files in ASCII format is not considering `turnNumber` info when simulations are performed in parallel environment unless all nodes has particles.
`hasTurnInformations()` could be modified to fix itext-calvo_ppedro.calvo@ciemat.esext-calvo_ppedro.calvo@ciemat.eshttps://gitlab.psi.ch/OPAL/src/-/issues/503Add more information to the HDF5 file written by monitors2021-04-05T20:16:16+02:00krausAdd more information to the HDF5 file written by monitors### Summary
Currently the HDF5 file that is written by the monitors provides very limited information (x, y, t, px, py, pz). More information should be added such as the charge and the mass of the particles. Ideally the same information ...### Summary
Currently the HDF5 file that is written by the monitors provides very limited information (x, y, t, px, py, pz). More information should be added such as the charge and the mass of the particles. Ideally the same information as in the phase space file should be added.OPAL 2021.1krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/632Delete particles that move in the opposite direction than the bunch.2021-04-05T20:09:26+02:00krausDelete particles that move in the opposite direction than the bunch.### Summary
When running some simulations a drastic increase in overall compute time is noticed. This seems to originate from the evaluation of external fields.
### Steps to reproduce
Run the same simulation with Opal 2.2 and 2.4 and...### Summary
When running some simulations a drastic increase in overall compute time is noticed. This seems to originate from the evaluation of external fields.
### Steps to reproduce
Run the same simulation with Opal 2.2 and 2.4 and compare the timings.
### What is the current *bug* behavior?
The time to evaluate the external fields has regressed from Opal 2.2.
### What is the expected *correct* behavior?
The evaluation of the external fields shouldn't take longer as in Opal 2.2
### Relevant logs and/or screenshots
Timing for Opal 2.4
```
Timings{0}> -----------------------------------------------------------------
Timings{0}> Timing results for 16 nodes:
Timings{0}> -----------------------------------------------------------------
Timings{0}> mainTimer........... Wall tot = 1333.67, CPU tot = 1304.62
Timings{0}>
Timings{0}> Binaryrepart........ Wall max = 0.0760612, CPU max = 0.12
Timings{0}> Wall avg = 0.0748878, CPU avg = 0.076875
Timings{0}> Wall min = 0.0710163, CPU min = 0.04
Timings{0}>
Timings{0}> Boundingbox......... Wall max = 21.1333, CPU max = 21.51
Timings{0}> Wall avg = 20.492, CPU avg = 20.3581
Timings{0}> Wall min = 19.5912, CPU min = 18.98
Timings{0}>
Timings{0}> Boundingbox-bounds.. Wall max = 3.31469, CPU max = 3.25
Timings{0}> Wall avg = 2.33188, CPU avg = 2.32125
Timings{0}> Wall min = 1.45284, CPU min = 1.43
Timings{0}>
Timings{0}> Boundingbox-update.. Wall max = 12.3236, CPU max = 12.66
Timings{0}> Wall avg = 12.2843, CPU avg = 12.1619
Timings{0}> Wall min = 12.2186, CPU min = 11.72
Timings{0}>
Timings{0}> Compute Statistics.. Wall max = 24.9249, CPU max = 25.18
Timings{0}> Wall avg = 23.5228, CPU avg = 23.6244
Timings{0}> Wall min = 21.6156, CPU min = 21.35
Timings{0}>
Timings{0}> ComputePotential.... Wall max = 212.61, CPU max = 213.74
Timings{0}> Wall avg = 211.029, CPU avg = 210.689
Timings{0}> Wall min = 207.543, CPU min = 207.01
Timings{0}>
Timings{0}> Create Distr........ Wall max = 0.0197351, CPU max = 0.03
Timings{0}> Wall avg = 0.0186866, CPU avg = 0.020625
Timings{0}> Wall min = 0.0185006, CPU min = 0.01
Timings{0}>
Timings{0}> External field eval. Wall max = 711.153, CPU max = 711.74
Timings{0}> Wall avg = 361.201, CPU avg = 361.191
Timings{0}> Wall min = 2.25931, CPU min = 2.35
Timings{0}>
Timings{0}> Fast inside test.... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Histogram........... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Initialize geometry. Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Inside test......... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Load Distr.......... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Particle Inside..... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Ray tracing......... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> SelfField total..... Wall max = 380.273, CPU max = 380.01
Timings{0}> Wall avg = 344.384, CPU avg = 344.401
Timings{0}> Wall min = 317.067, CPU min = 318.26
Timings{0}>
Timings{0}> SF: GreensFTotal.... Wall max = 134.448, CPU max = 134.95
Timings{0}> Wall avg = 133.307, CPU avg = 132.716
Timings{0}> Wall min = 131.767, CPU min = 130.46
Timings{0}>
Timings{0}> TIntegration1....... Wall max = 20.5137, CPU max = 20.53
Timings{0}> Wall avg = 19.1446, CPU avg = 19.1488
Timings{0}> Wall min = 17.3008, CPU min = 17.47
Timings{0}>
Timings{0}> TIntegration2....... Wall max = 38.3021, CPU max = 38.52
Timings{0}> Wall avg = 36.8959, CPU avg = 36.8775
Timings{0}> Wall min = 35.997, CPU min = 35.53
Timings{0}>
Timings{0}> WakeField........... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Write H5-File....... Wall max = 49.9556, CPU max = 21.73
Timings{0}> Wall avg = 49.9353, CPU avg = 20.2519
Timings{0}> Wall min = 49.8026, CPU min = 17.74
Timings{0}>
Timings{0}> Write Stat.......... Wall max = 9.01406, CPU max = 2.07
Timings{0}> Wall avg = 0.833675, CPU avg = 0.405
Timings{0}> Wall min = 0.281822, CPU min = 0.22
Timings{0}>
Timings{0}> -----------------------------------------------------------------
```
Timing for Opal 2.2 and the same input file
```
Timings{0}> -----------------------------------------------------------------
Timings{0}> Timing results for 16 nodes:
Timings{0}> -----------------------------------------------------------------
Timings{0}> mainTimer........... Wall tot = 698.587, CPU tot = 672.33
Timings{0}>
Timings{0}> Binaryrepart........ Wall max = 0.0804251, CPU max = 0.13
Timings{0}> Wall avg = 0.0792938, CPU avg = 0.078125
Timings{0}> Wall min = 0.0762691, CPU min = 0.04
Timings{0}>
Timings{0}> Boundingbox......... Wall max = 21.9074, CPU max = 22.05
Timings{0}> Wall avg = 21.2645, CPU avg = 21.2381
Timings{0}> Wall min = 20.2972, CPU min = 19.86
Timings{0}>
Timings{0}> Boundingbox-bounds.. Wall max = 3.23519, CPU max = 3.3
Timings{0}> Wall avg = 2.29564, CPU avg = 2.33812
Timings{0}> Wall min = 1.43132, CPU min = 1.19
Timings{0}>
Timings{0}> Boundingbox-update.. Wall max = 13.0062, CPU max = 13.74
Timings{0}> Wall avg = 12.9693, CPU avg = 12.9756
Timings{0}> Wall min = 12.8177, CPU min = 12.44
Timings{0}>
Timings{0}> Compute Statistics.. Wall max = 26.1269, CPU max = 26.62
Timings{0}> Wall avg = 24.6571, CPU avg = 24.815
Timings{0}> Wall min = 22.6815, CPU min = 22.65
Timings{0}>
Timings{0}> ComputePotential.... Wall max = 221.744, CPU max = 222.57
Timings{0}> Wall avg = 219.925, CPU avg = 219.121
Timings{0}> Wall min = 215.744, CPU min = 214.95
Timings{0}>
Timings{0}> Create Distr........ Wall max = 0.0196037, CPU max = 0.03
Timings{0}> Wall avg = 0.01854, CPU avg = 0.019375
Timings{0}> Wall min = 0.0183704, CPU min = 0.01
Timings{0}>
Timings{0}> External field eval. Wall max = 83.0337, CPU max = 83.09
Timings{0}> Wall avg = 37.3202, CPU avg = 37.67
Timings{0}> Wall min = 2.13352, CPU min = 2.24
Timings{0}>
Timings{0}> Fast inside test.... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Histogram........... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Initialize geometry. Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Inside test......... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Load Distr.......... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Particle Inside..... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Ray tracing......... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Secondary emission.. Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> SelfField total..... Wall max = 398.178, CPU max = 399.5
Timings{0}> Wall avg = 359.377, CPU avg = 358.998
Timings{0}> Wall min = 330.56, CPU min = 330.17
Timings{0}>
Timings{0}> SF: GreensFTotal.... Wall max = 140.186, CPU max = 141.31
Timings{0}> Wall avg = 139.146, CPU avg = 138.486
Timings{0}> Wall min = 137.841, CPU min = 135.62
Timings{0}>
Timings{0}> TIntegration1....... Wall max = 21.4125, CPU max = 21.77
Timings{0}> Wall avg = 20.1085, CPU avg = 19.935
Timings{0}> Wall min = 18.3236, CPU min = 18.12
Timings{0}>
Timings{0}> TIntegration2....... Wall max = 40.1375, CPU max = 40.82
Timings{0}> Wall avg = 38.7925, CPU avg = 38.8013
Timings{0}> Wall min = 37.9342, CPU min = 37.21
Timings{0}>
Timings{0}> WakeField........... Wall max = 0, CPU max = 0
Timings{0}> Wall avg = 0, CPU avg = 0
Timings{0}> Wall min = 0, CPU min = 0
Timings{0}>
Timings{0}> Write H5-File....... Wall max = 47.1853, CPU max = 21.09
Timings{0}> Wall avg = 47.1643, CPU avg = 18.93
Timings{0}> Wall min = 47.0338, CPU min = 15.95
Timings{0}>
Timings{0}> Write Stat.......... Wall max = 9.99641, CPU max = 3.93
Timings{0}> Wall avg = 2.74196, CPU avg = 2.36437
Timings{0}> Wall min = 2.17362, CPU min = 2.09
Timings{0}>
Timings{0}> -----------------------------------------------------------------
```OPAL 2021.1krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/643Remove unnecessary condition in CCollimators2021-03-26T11:52:31+01:00ext-calvo_ppedro.calvo@ciemat.esRemove unnecessary condition in CCollimatorsCCollimator is currently restricted only for `REGULAR` particles, but all the `ParticleOrigin` must be consideredCCollimator is currently restricted only for `REGULAR` particles, but all the `ParticleOrigin` must be consideredOPAL 2021.1ext-calvo_ppedro.calvo@ciemat.esext-calvo_ppedro.calvo@ciemat.eshttps://gitlab.psi.ch/OPAL/src/-/issues/642Stop particles in probe2021-03-26T08:27:43+01:00ext-calvo_ppedro.calvo@ciemat.esStop particles in probeAdds a user option to stop particle tracking in the probe elementAdds a user option to stop particle tracking in the probe elementext-calvo_ppedro.calvo@ciemat.esext-calvo_ppedro.calvo@ciemat.eshttps://gitlab.psi.ch/OPAL/src/-/issues/640Update time unit in loss output file of some elements2021-03-24T09:09:01+01:00ext-calvo_ppedro.calvo@ciemat.esUpdate time unit in loss output file of some elementsFrom a [discussion](https://gitlab.psi.ch/OPAL/src/-/merge_requests/477#note_30392) on MR !477, and in agreement with #357, the unit of time should be unified to `s` in some elements to avoid inconsistencies in the `LossDataSink` output ...From a [discussion](https://gitlab.psi.ch/OPAL/src/-/merge_requests/477#note_30392) on MR !477, and in agreement with #357, the unit of time should be unified to `s` in some elements to avoid inconsistencies in the `LossDataSink` output file.OPAL 2021.1ext-calvo_ppedro.calvo@ciemat.esext-calvo_ppedro.calvo@ciemat.eshttps://gitlab.psi.ch/OPAL/src/-/issues/639unused variable in ippl/test/particle/p3m3dMicrobunching.cpp2021-03-23T09:39:02+01:00gsellunused variable in ippl/test/particle/p3m3dMicrobunching.cppCompilation fails with an `unused variable` warning in `ippl/test/particle/p3m3dMicrobunching.cpp` if compile type is set to `Release`.Compilation fails with an `unused variable` warning in `ippl/test/particle/p3m3dMicrobunching.cpp` if compile type is set to `Release`.OPAL 2021.1gsellgsellhttps://gitlab.psi.ch/OPAL/src/-/issues/637Segmantation fault with BoundaryGeometry2021-02-17T11:21:51+01:00ext-calvo_ppedro.calvo@ciemat.esSegmantation fault with BoundaryGeometrySince MR OPAL/src!464, I got a segmentation fault running opal-cycl with geometry
```
*** Process received signal ***
Signal: Aborted (6)
Signal code: (-6)
[ 0] /lib64/libpthread.so.0[0x30b520f130]
[ 1] /lib64/libc.so.6(gsignal+0x39)[0...Since MR OPAL/src!464, I got a segmentation fault running opal-cycl with geometry
```
*** Process received signal ***
Signal: Aborted (6)
Signal code: (-6)
[ 0] /lib64/libpthread.so.0[0x30b520f130]
[ 1] /lib64/libc.so.6(gsignal+0x39)[0x30b4a359d9]
[ 2] /lib64/libc.so.6(abort+0x148)[0x30b4a370e8]
[ 3] opal(_ZNSt6vectorIN7Message7MsgItemESaIS1_EE7reserveEm+0x0)[0x64af30]
[ 4] opal[0x80121b]
[ 5] opal(_ZN16BoundaryGeometry10initializeEv+0x2e62)[0x8044e2]
[ 6] opal(_ZN16BoundaryGeometryC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPS_+0x348)[0x805468]
[ 7] opal(_ZN16BoundaryGeometry5cloneERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x25)[0x8055e5]
[ 8] opal(_ZN8TrackRun21setupCyclotronTrackerEv+0xeb0)[0x81ea60]
[ 9] opal(_ZN8TrackRun7executeEv+0xc8)[0x8211d8]
[10] opal(_ZNK10OpalParser7executeEP6ObjectRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x3a)[0x6f197a]
[11] opal(_ZNK10OpalParser11parseActionER9Statement+0xfd)[0x6f5ced]
[12] opal(_ZNK10OpalParser5parseER9Statement+0x173)[0x6f4933]
[13] opal(_ZNK10OpalParser3runEv+0x4e)[0x6f214e]
[14] opal(_ZN8TrackCmd7executeEv+0x97c)[0x81b50c]
[15] opal(_ZNK10OpalParser7executeEP6ObjectRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x3a)[0x6f197a]
[16] opal(_ZNK10OpalParser11parseActionER9Statement+0xfd)[0x6f5ced]
[17] opal(_ZNK10OpalParser5parseER9Statement+0x173)[0x6f4933]
[18] opal(_ZNK10OpalParser3runEv+0x4e)[0x6f214e]
[19] opal(_ZNK10OpalParser3runEP11TokenStream+0x70)[0x6f6260]
[20] opal(main+0x1f5d)[0x6443cd]
[21] /lib64/libc.so.6(__libc_start_main+0xf5)[0x30b4a21b45]
[22] opal[0x6356a9]
```
cc: @kraus, @gsellOPAL 2021.1https://gitlab.psi.ch/OPAL/src/-/issues/116CollimatorPhysics::EnergyLoss2021-02-16T08:39:33+01:00adelmannCollimatorPhysics::EnergyLossis hard coded for protons. Need also make clear in the manual (exception in code) that electrons are not supported.is hard coded for protons. Need also make clear in the manual (exception in code) that electrons are not supported.OPAL 2021.1ext-calvo_ppedro.calvo@ciemat.esext-calvo_ppedro.calvo@ciemat.es