src issueshttps://gitlab.psi.ch/OPAL/src/-/issues2017-12-21T09:52:44+01:00https://gitlab.psi.ch/OPAL/src/-/issues/188C version of FFTPACK segfaults2017-12-21T09:52:44+01:00snuverink_jjochem.snuverink@psi.chC version of FFTPACK segfaultsOpalRingTest and RingCyclotron-Tests segfault as [found by Christoph]
(https://gitlab.psi.ch/OPAL/src/commit/ee8a32ba55683d5dea34e7522e3c2cba2384d4d8#note_3812) with:
```
[pc12290:01336] Signal: Segmentation fault (11)
[pc12290:01336] S...OpalRingTest and RingCyclotron-Tests segfault as [found by Christoph]
(https://gitlab.psi.ch/OPAL/src/commit/ee8a32ba55683d5dea34e7522e3c2cba2384d4d8#note_3812) with:
```
[pc12290:01336] Signal: Segmentation fault (11)
[pc12290:01336] Signal code: (128)
[pc12290:01336] Failing at address: (nil)
[pc12290:01336] [ 0] /lib64/libpthread.so.0[0x3ab660f7e0]
[pc12290:01336] [ 1] opal(rffti1_+0x1c)[0x25b43ac]
[pc12290:01336] [ 2] opal(rffti_+0x24)[0x25b4374]
[pc12290:01336] [ 3] opal(_ZN3FFTI11RCTransformLj3EdEC1ERK7NDIndexILj3EES5_RKbi+0x2c7)[0x13109d7]
[pc12290:01336] [ 4] opal(_ZN16FFTPoissonSolverC1EP16UniformCartesianILj3EdEP19CenteredFieldLayoutILj3ES1_4CellENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESC_+0xf5c)[0x130428c]
[pc12290:01336] [ 5] opal(_ZN11FieldSolver10initSolverEP13PartBunchBaseIdLj3EE+0x7c5)[0x1038d35]
[pc12290:01336] [ 6] opal(_ZN8TrackRun16setupFieldsolverEv+0x1ef)[0x13efb6f]
[pc12290:01336] [ 7] opal(_ZN8TrackRun21setupCyclotronTrackerEv+0xbb)[0x13f3c2b]
[pc12290:01336] [ 8] opal(_ZN8TrackRun7executeEv+0x632)[0x13f5d02]
[pc12290:01336] [ 9] opal(_ZNK10OpalParser7executeEP6ObjectRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x35)[0xff7f35]
```gsellgsellhttps://gitlab.psi.ch/OPAL/src/-/issues/187Unit tests Gauss and Binomial fail2017-12-02T15:04:35+01:00snuverink_jjochem.snuverink@psi.chUnit tests Gauss and Binomial failThe unit tests `GaussTest` and `BinomialTest` fail with NaNs.
I investigated a bit and this is because in Distribution::adjustPhaseSpace() totalNumberParticles_m is 0 (division by zero).
Right now the test do the following:
```c++
Dis...The unit tests `GaussTest` and `BinomialTest` fail with NaNs.
I investigated a bit and this is because in Distribution::adjustPhaseSpace() totalNumberParticles_m is 0 (division by zero).
Right now the test do the following:
```c++
Distribution dist;
... // set attributes
dist.setDistType();
dist.checkIfEmitted();
size_t numParticles = 1e7;
dist.create(numParticles, Physics::m_p);
```
Possibly these shouldn't call the private create() directly?krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/186error compiling with clang2017-12-05T09:46:01+01:00gsellerror compiling with clangClang (Apple LLVM version 9.0.0 (clang-900.0.38)) complains about several expressions in the OPAL code. One I do not know how to fix is:
```C
[ 11%] Building CXX object src/CMakeFiles/OPALib.dir/Editor/EditParser.cpp.o
In file included ...Clang (Apple LLVM version 9.0.0 (clang-900.0.38)) complains about several expressions in the OPAL code. One I do not know how to fix is:
```C
[ 11%] Building CXX object src/CMakeFiles/OPALib.dir/Editor/EditParser.cpp.o
In file included from /Users/gsell/src/OPAL/src/src/Classic/Parser/ClassicParser.cpp:39:
In file included from /Users/gsell/src/OPAL/src/src/Classic/BeamlineCore/Octupole.h:23:
/Users/gsell/src/OPAL/src/src/Classic/BeamlineCore/SingleMultipole.h:209:30: error: instantiation of variable
'SingleMultipole<4>::entries' required here, but no definition is available [-Werror,-Wundefined-var-template]
for(const Entry *entry = entries; entry->name != 0; ++entry) {
^
/Users/gsell/src/OPAL/src/src/Classic/BeamlineCore/SingleMultipole.h:60:14: note: in instantiation of member function
'SingleMultipole<4>::getChannel' requested here
explicit SingleMultipole(const std::string &name);
^
/Users/gsell/src/OPAL/src/src/Classic/Parser/ClassicParser.cpp:111:24: note: in instantiation of member function
'SingleMultipole<4>::SingleMultipole' requested here
factory.define(new Octupole("OCTUPOLE"));
^
/Users/gsell/src/OPAL/src/src/Classic/BeamlineCore/SingleMultipole.h:130:24: note: forward declaration of template entity is here
static const Entry entries[];
^
/Users/gsell/src/OPAL/src/src/Classic/BeamlineCore/SingleMultipole.h:209:30: note: add an explicit instantiation declaration to suppress
this warning if 'SingleMultipole<4>::entries' is explicitly instantiated in another translation unit
for(const Entry *entry = entries; entry->name != 0; ++entry) {
^
1 error generated.
```
What is the right "explicit instantiation declaration" here???krausgsellsnuverink_jjochem.snuverink@psi.chkraushttps://gitlab.psi.ch/OPAL/src/-/issues/185OPAL-Cyc / RINGDEFINITION: Subline definition does not work2017-12-07T15:48:51+01:00Valeria RizzoglioOPAL-Cyc / RINGDEFINITION: Subline definition does not workI am running a small test with CCollimators in OPAL-Cyc - RINGDEFINITION.
Those are the elements of the beamline:
```
OffQuad1: LOCAL_CARTESIAN_OFFSET, end_position_x=off_quad1x....
Quad1: SBEND3D, FMAPFN="3D_B_map_1st_Q.table", LENG...I am running a small test with CCollimators in OPAL-Cyc - RINGDEFINITION.
Those are the elements of the beamline:
```
OffQuad1: LOCAL_CARTESIAN_OFFSET, end_position_x=off_quad1x....
Quad1: SBEND3D, FMAPFN="3D_B_map_1st_Q.table", LENGTH_UNITS=1000.0, FIELD_UNITS=10.0;
Quad1_BP_1: CCollimator, XSTART=-950, XEND=-950, YSTART=1800, YEND=1950, ZSTART=70, ZEND=170, WIDTH=4.0;
Quad1_BP_2: CCollimator, XSTART=-1000, XEND=-1000, YSTART=1800, YEND=1950, ZSTART=168, ZEND=172, WIDTH=100.0;
Quad1_BP_3: CCollimator, XSTART=-1050, XEND=-1050, YSTART=1800, YEND=1950, ZSTART=70, ZEND=170, WIDTH=4.0;
Quad1_BP_4: CCollimator, XSTART=-1000, XEND=-1000, YSTART=1800, YEND=1950, ZSTART=68, ZEND=72, WIDTH=100.0;
```
I tried to define a subline with only collimators:
`Quad1_BP: LINE = (Quad1_BP_1, Quad1_BP_2, Quad1_BP_3, Quad1_BP_4);`
Then the beamline that I want to track is:
`BEAMLINE: LINE = (OffQuad1, Quad1, Quad1_BP);`
With this configuration, I get segmentation fault.
If I replace `Quad1_BP` with the elements that form this subline, OPAL runs without problems.
`BEAMLINE: LINE = (OffQuad1, Quad1, Quad1_BP_1, Quad1_BP_2, Quad1_BP_3, Quad1_BP_4);`
**It seems that the OPAL-Cyc - RINGDEFINITION does not support definition of sublines.**
Here my configuration
```
Currently Loaded Modulefiles:
1) gcc/5.4.0 3) OPAL/1.6.1 5) openssl/1.0.2j 7) Tk/8.6.4 9) boost/1.62.0 11) gsl/2.2.1
2) openmpi/1.10.4 4) OPAL/1.6 6) Tcl/8.6.4 8) Python/2.7.12 10) root/6.08.02 12) H5root/1.3.4
```OPAL 1.6.1adelmannext-rogers_cadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/184Unused BEAM Attributes2017-12-13T14:53:25+01:00snuverink_jjochem.snuverink@psi.chUnused BEAM AttributesWhile working on issue #183, I noticed that in [Beam.cpp](https://gitlab.psi.ch/OPAL/src/blob/master/src/Structure/Beam.cpp) there are several attributes defined that are not used nor documented:
* RADIATE
* DAMP
* QUANTUM
* EXN
* EYN
*...While working on issue #183, I noticed that in [Beam.cpp](https://gitlab.psi.ch/OPAL/src/blob/master/src/Structure/Beam.cpp) there are several attributes defined that are not used nor documented:
* RADIATE
* DAMP
* QUANTUM
* EXN
* EYN
* SPACECHARGE
* FIELDSOLVER
* BUNCHED
* KBUNCH
I propose to remove those from the code.
The following are not documented and only used in the twiss calculation (AFAICS):
* EX, EY, ETsnuverink_jjochem.snuverink@psi.chsnuverink_jjochem.snuverink@psi.chhttps://gitlab.psi.ch/OPAL/src/-/issues/183Attributes PC, ENERGY and GAMMA of BEAM command not described2018-01-09T18:53:22+01:00krausAttributes PC, ENERGY and GAMMA of BEAM command not describedThere are several possible definitions for PC
1. $`PC = mc^2 \frac{\sqrt{\sum_i p_{x,i}^2 + p_{y,i}^2 + p_{z,i}^2}}{N}`$
1. $`PC = mc^2 \frac{\sum_i p_{z,i}}{N}`$
Currently the second definition is implemented. This has the advantage th...There are several possible definitions for PC
1. $`PC = mc^2 \frac{\sqrt{\sum_i p_{x,i}^2 + p_{y,i}^2 + p_{z,i}^2}}{N}`$
1. $`PC = mc^2 \frac{\sum_i p_{z,i}}{N}`$
Currently the second definition is implemented. This has the advantage that mean longitudinal momentum is well defined and thereby the reference particle has the same velocity as the centroid. The disadvantage is that the kinematic energy of the bunch is to high.
The definition for PC should be chosen and the two attributes should be described in the manual for 1.6 and 1.9.adelmannsnuverink_jjochem.snuverink@psi.chadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/182Autophasing gives unexpected results2017-11-19T13:26:34+01:00adelmannAutophasing gives unexpected resultsThe attached lattice works perfect in OPAL 1.4.0 and does not show autophasing information on the *master*.
IN xxxDesignPath.dat we only have NaN's.
[csu_linac.in](/uploads/d8df65871270d3d1f51bf62ca2498266/csu_linac.in)[UOF20LFCell1_B....The attached lattice works perfect in OPAL 1.4.0 and does not show autophasing information on the *master*.
IN xxxDesignPath.dat we only have NaN's.
[csu_linac.in](/uploads/d8df65871270d3d1f51bf62ca2498266/csu_linac.in)[UOF20LFCell1_B.T7](/uploads/0518005dfebb87560f7d4d796e4c683b/UOF20LFCell1_B.T7)[UOF20LHCell1_B.T7](/uploads/050945818499b0fa4b79b3fbd7c5310c/UOF20LHCell1_B.T7)
[UOF20LFCell2_B.T7](/uploads/a0d905e3e6908b712fa2daa96307e650/UOF20LFCell2_B.T7)
[UOF20S1.T7](/uploads/aa07e8534f8cec72e47148db6d45e196/UOF20S1.T7)OPAL 2.0.0krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/181timing.dat2018-01-25T12:21:49+01:00adelmanntiming.datAdd problem size to timing.dat
NP == number of particles
MX,MY,MZ == gridsizes
domain decomposition
Not shure how to cover AMR but that is a differnt topic.Add problem size to timing.dat
NP == number of particles
MX,MY,MZ == gridsizes
domain decomposition
Not shure how to cover AMR but that is a differnt topic.https://gitlab.psi.ch/OPAL/src/-/issues/180Use OPAL's native SDDS parser in the optimiser2017-11-22T22:38:09+01:00snuverink_jjochem.snuverink@psi.chUse OPAL's native SDDS parser in the optimiserAs discussed in #153. The optimiser has its own SDDS parser in opt-pilot/Util/SDDSReader. It would be better to reuse the SDDS parser from src/Structure/SDDSParser.As discussed in #153. The optimiser has its own SDDS parser in opt-pilot/Util/SDDSReader. It would be better to reuse the SDDS parser from src/Structure/SDDSParser.krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/179opt-pilot CONSTRAINT command not known2017-11-07T10:03:58+01:00snuverink_jjochem.snuverink@psi.chopt-pilot CONSTRAINT command not knownA opt-pilot constraint such as:
```
c1: CONSTRAINT, EXPR="fabs(rms_x)<1.5e-2";
constrs: CONSTRAINTS = (c1);
```
gives:
```
Error>
Error> *** Parse error detected by function "OpalParser::parseDefine()"
Error> *** in line 46 of file "...A opt-pilot constraint such as:
```
c1: CONSTRAINT, EXPR="fabs(rms_x)<1.5e-2";
constrs: CONSTRAINTS = (c1);
```
gives:
```
Error>
Error> *** Parse error detected by function "OpalParser::parseDefine()"
Error> *** in line 46 of file "RingOpt.in" before token ",":
Error> The object "CONSTRAINT" is unknown.
```
This is because the keyword CONSTRAINT is not skipped in [AbsFileStream](https://gitlab.psi.ch/OPAL/src/blob/master/src/Classic/Parser/AbsFileStream.cpp#L42).
I will fix this there.
One concern is that CONSTRAINT is also a keyword in the match routine: https://gitlab.psi.ch/OPAL/src/blob/master/src/Match/MatchParser.cpp.
However, as far as I can see this is currently not in OPAL? Quoting the manual: "Please note this is not yet available in: `DOPAL-t` and `DOPAL-cycl`." @adelmann can you confirm?snuverink_jjochem.snuverink@psi.chsnuverink_jjochem.snuverink@psi.chhttps://gitlab.psi.ch/OPAL/src/-/issues/178H5root in the binary Linux distribution2017-12-28T14:30:38+01:00adelmannH5root in the binary Linux distribution`
[aandreas@beboplogin1 OPAL-1.6.1]$ source etc/profile.d/opal.sh
[aandreas@beboplogin1 OPAL-1.6.1]$ opal
`
OPAL works as expected.
`
[aandreas@beboplogin1 OPAL-1.6.1]$ H5root
/home/aandreas/OPAL-1.6.1/bin/H5root: line 13: /opt/psi/C...`
[aandreas@beboplogin1 OPAL-1.6.1]$ source etc/profile.d/opal.sh
[aandreas@beboplogin1 OPAL-1.6.1]$ opal
`
OPAL works as expected.
`
[aandreas@beboplogin1 OPAL-1.6.1]$ H5root
/home/aandreas/OPAL-1.6.1/bin/H5root: line 13: /opt/psi/Compiler/H5root/1.3.4/gcc/5.4.0/bin/H5root.bin: No such file or directory
`OPAL 1.6.1gsellgsellhttps://gitlab.psi.ch/OPAL/src/-/issues/177python xxxx_ElementPositions.py --export-web2017-11-06T22:50:24+01:00adelmannpython xxxx_ElementPositions.py --export-web`adelmann@eduroam062-061 ~/Desktop/ANL/optLinac_40nC/data $ python optLinac_40nC_ElementPositions.py --export-web
Traceback (most recent call last):
File "optLinac_40nC_ElementPositions.py", line 590, in <module>
exportWeb()
File...`adelmann@eduroam062-061 ~/Desktop/ANL/optLinac_40nC/data $ python optLinac_40nC_ElementPositions.py --export-web
Traceback (most recent call last):
File "optLinac_40nC_ElementPositions.py", line 590, in <module>
exportWeb()
File "optLinac_40nC_ElementPositions.py", line 170, in exportWeb
decodeVertices()
File "optLinac_40nC_ElementPositions.py", line 16, in decodeVertices
for i in xrange(len(numVertices)):
NameError: name 'xrange' is not defined`
[optLinac_40nC_ElementPositions.py](/uploads/06f0c11ef6d6f05fcc0b40f43b8b7e67/optLinac_40nC_ElementPositions.py)OPAL 1.9.xkrauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/176no error when missing data file for optimisation2017-11-07T09:28:54+01:00ext-neveu_nno error when missing data file for optimisationWhen trying to run an optimisation problem, if the data file is missing from the directory (i.e. optLinac.data) OPAL quits running, but does not return an error. Please add an error when the data file is missing from the directory.When trying to run an optimisation problem, if the data file is missing from the directory (i.e. optLinac.data) OPAL quits running, but does not return an error. Please add an error when the data file is missing from the directory.krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/175CSR wakes not computed correctly2017-10-26T22:30:25+02:00krausCSR wakes not computed correctlyThe behavior of the computation of the CSR wakes dramatically changed on Aug. 18 (BFREQ change from Hz to MHz). The references of the CSRBendDrift-Regtest changed since (***thanks*** to @adelmann's effort to let the reference have the sa...The behavior of the computation of the CSR wakes dramatically changed on Aug. 18 (BFREQ change from Hz to MHz). The references of the CSRBendDrift-Regtest changed since (***thanks*** to @adelmann's effort to let the reference have the same version).OPAL 1.6.1krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/174optimiser run hasResultsAvailable()2019-04-06T10:08:12+02:00adelmannoptimiser run hasResultsAvailable()it seams that hasResultsAvailable() is sometimes true after I removed
the pid from the hash string. This was necessary when more than
one $CORE is used for a worker.
I probable need to add this back but not with the pid but with an
id ...it seams that hasResultsAvailable() is sometimes true after I removed
the pid from the hash string. This was necessary when more than
one $CORE is used for a worker.
I probable need to add this back but not with the pid but with an
id that represents the "worker with more than one core"
@ineichen can you point me to that structure.OPAL 2.0.0adelmannYves Ineichenadelmann2017-10-28https://gitlab.psi.ch/OPAL/src/-/issues/173optimiser run has two times the tmpl file specified2018-01-10T21:15:13+01:00adelmannoptimiser run has two times the tmpl file specifiedargv[1] is a mandatory argument for OPAL, however in case of a optimiser run there is an
additional argument --inputfile=$TEMPLATES/$FNBASE.tmpl. This can be removed and the argv[1] used.argv[1] is a mandatory argument for OPAL, however in case of a optimiser run there is an
additional argument --inputfile=$TEMPLATES/$FNBASE.tmpl. This can be removed and the argv[1] used.OPAL 2.0.0adelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/172All Fields in an expression must be aligned. (Do you have enough guard cells...2018-12-10T14:33:40+01:00adelmannAll Fields in an expression must be aligned. (Do you have enough guard cells?) OPAL-cyclmerlin-l-01:/gpfs/home/adelmann/scratch/UQ/isodar-1-O3/
Accelerated_BEAMCURRENT=0.0075_HW1=8.344454524637621_HL1=2.542497630448107_HW2=8.344454524637621_HL2=2.607642038949257
slurm-12130.out
```
OPAL{0}> *** Finished turn 23, Total num...merlin-l-01:/gpfs/home/adelmann/scratch/UQ/isodar-1-O3/
Accelerated_BEAMCURRENT=0.0075_HW1=8.344454524637621_HL1=2.542497630448107_HW2=8.344454524637621_HL2=2.607642038949257
slurm-12130.out
```
OPAL{0}> *** Finished turn 23, Total number of live particles: 330298
OPAL{0}> * Cavity RF1B Phase= 8.1602 [deg] transit time factor= 0.99972 dE= 0.091803 [MeV] E_kin= 15.05 [MeV]
OPAL{0}> * Cavity RF2A Phase= 17.119 [deg] transit time factor= 0.99972 dE= 0.089672 [MeV] E_kin= 15.14 [MeV]
OPAL{0}> * Cavity RF2B Phase= 8.4183 [deg] transit time factor= 0.99972 dE= 0.092922 [MeV] E_kin= 15.233 [MeV]
Error{4}> All Fields in an expression must be aligned. (Do you have enough guard cells?)
Error{4}> This error occurred while evaluating an expression for an LField with domain {[8:15:1],[0:8:1],[0:7:1]}
slurmstepd: error: *** JOB 12130 ON merlin-c-07 CANCELLED AT 2017-10-13T15:39:58 ***
```
*AND*
Accelerated_BEAMCURRENT=0.0075_HW1=7.655545475362379_HL1=2.607642038949257_HW2=8.344454524637621_HL2=2.542497630448107]
slurm-12492.out
```
OPAL{0}> * Cavity RF3B Phase= -1.6424 [deg] transit time factor= 0.99995 dE= 0.20723 [MeV] E_kin= 94.092 [MeV]
OPAL{0}> * Cavity RF4A Phase= 9.16 [deg] transit time factor= 0.99995 dE= 0.20493 [MeV] E_kin= 94.297 [MeV]
OPAL{0}> *** Finished turn 92, Total number of live particles: 289527
OPAL{0}> * Cavity RF2A Phase= 8.5664 [deg] transit time factor= 0.99995 dE= 0.20576 [MeV] E_kin= 95.123 [MeV]
OPAL{0}> * Cavity RF3A Phase= 8.5013 [deg] transit time factor= 0.99995 dE= 0.20631 [MeV] E_kin= 95.537 [MeV]
OPAL{0}> * Cavity RF3B Phase= -1.9567 [deg] transit time factor= 0.99995 dE= 0.2086 [MeV] E_kin= 95.746 [MeV]
Error{3}> All Fields in an expression must be aligned. (Do you have enough guard cells?)
Error{3}> This error occurred while evaluating an expression for an LField with domain {[0:5:1],[8:15:1],[8:15:1]}
slurmstepd: error: *** JOB 12492 ON merlin-c-40 CANCELLED AT 2017-10-16T03:25:28 DUE TO TIME LIMIT ***
```
*Go from 8 to 4 cores* in order to find out if the job is terminating nicely.OPAL 2.0.0adelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/171OPAL-t wrong results2017-10-22T10:10:53+02:00adelmannOPAL-t wrong resultsThe attached input files give a consistent solutions in V1.4 and V1.6 as
demonstrated in regtest.pdf.
[regtest.pdf](/uploads/57c7e0d924b6ae43095fe9b0ca133088/regtest.pdf)
With 1.9.x depending on the BFREQ we get a different set of so...The attached input files give a consistent solutions in V1.4 and V1.6 as
demonstrated in regtest.pdf.
[regtest.pdf](/uploads/57c7e0d924b6ae43095fe9b0ca133088/regtest.pdf)
With 1.9.x depending on the BFREQ we get a different set of solutions:
![v1.9err_2](/uploads/221e8b0cd7f810cc8eafaa1c8ac85fa9/v1.9err_2.png)
In case of Hz as units the energy is correct in case of MHz (as it should be)
the energy is wrong.
In both cases Autophase finds the correct energy.
[M_440.T7](/uploads/01c55ee8da1bcbc085eafbf42c7d9338/M_440.T7)
[DriveGun.T7](/uploads/015112fe7906c295a044d37b941c673a/DriveGun.T7)
[BF_550.T7](/uploads/1b31be08c1ea892ed0bfb23110e2310d/BF_550.T7)
[RFphotoinjector-1.9.in](/uploads/7bd8b3675626b4f84e2816f19bea1c74/RFphotoinjector-1.9.in)OPAL 2.0.0krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/170SurfacePhysics in OPAL-Cyc2020-04-22T11:41:42+02:00Valeria RizzoglioSurfacePhysics in OPAL-CycI ran a small test using OPAL-Cyc - RINGDEFINITION with a CCOLLIMATOR. I applied the SURFACEPHYSICS on the CCOLLIMATOR but the Monte Carlo was not performed. The beam colliding with the CCOLLIMATOR was simply lost and not scattered. This...I ran a small test using OPAL-Cyc - RINGDEFINITION with a CCOLLIMATOR. I applied the SURFACEPHYSICS on the CCOLLIMATOR but the Monte Carlo was not performed. The beam colliding with the CCOLLIMATOR was simply lost and not scattered. This is related to the
Issue #149
```
Coll: SURFACEPHYSICS, TYPE="DEGRADER", ENABLERUTHERFORD=TRUE, MATERIAL="GraphiteR6710";
Quad1_BP: CCollimator, XSTART=-1000, XEND=-1000, YSTART=1800, YEND=1810, ZSTART=70, ZEND=170, WIDTH=200.0, SURFACEPHYSICS=Coll;
```
I tried to change TYPE with "COLLIMATOR" and "CCOLLIMATOR", but the results did not change.
Attached the input file and the output.
[MonteCarlo_Cyc.in](/uploads/013bde1e7b0452d5fbbe266d0a7026ed/MonteCarlo_Cyc.in)[TYPE_COLLIMATOR.out](/uploads/a33c60beb640faccc6353c882565d3a8/TYPE_COLLIMATOR.out)
I ran on Merlin with the following settings:
```
1) gcc/5.4.0 3) OPAL/1.6.0 5) root/6.08.02 7) Tcl/8.6.4 9) Python/2.7.12 11) gsl/2.2.1 13) psi-python27/2.2.0
2) openmpi/1.10.4 4) OPAL/1.6 6) openssl/1.0.2j 8) Tk/8.6.4 10) boost/1.62.0
```OPAL 2.0.0adelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/169New Material: BoronCarbide2017-10-19T19:30:25+02:00adelmannNew Material: BoronCarbideOPAL Name: BoronCarbide
A : 55.25
Z : 26
rho : 2.48 g/cm^3
X0 : 50.14 g/cm^2
A2 : 3.963
A3 : 6065
A4 : 1243
A5 : 7.782e-03OPAL Name: BoronCarbide
A : 55.25
Z : 26
rho : 2.48 g/cm^3
X0 : 50.14 g/cm^2
A2 : 3.963
A3 : 6065
A4 : 1243
A5 : 7.782e-03OPAL 1.6.1adelmannadelmann