src issueshttps://gitlab.psi.ch/OPAL/src/-/issues2018-01-04T18:14:26+01:00https://gitlab.psi.ch/OPAL/src/-/issues/200Optimiser throws unexpected Exceptions and later die2018-01-04T18:14:26+01:00adelmannOptimiser throws unexpected Exceptions and later dieAfter 3ed381f8 I see more Exceptions (merlinl01:/gpfs/home/adelmann/scratch/awa-optim/code/optLinac_40nC.o78706)
I am now a bit more confused:
- the *.data file should only read once (but we have over 600 Exeptions)
- we again have di...After 3ed381f8 I see more Exceptions (merlinl01:/gpfs/home/adelmann/scratch/awa-optim/code/optLinac_40nC.o78706)
I am now a bit more confused:
- the *.data file should only read once (but we have over 600 Exeptions)
- we again have directories that seams to exists
The real problem is reported in merlinl01:/gpfs/home/adelmann/scratch/awa-optim-0/code/optLinac_40nC.o78651
**░░░░░terminate called after throwing an instance of 'OpalException**OPAL 2.0.0krausadelmannYves Ineichenkraushttps://gitlab.psi.ch/OPAL/src/-/issues/199Rethink catching of exceptions2018-01-09T06:41:26+01:00krausRethink catching of exceptionsCurrently all exceptions are caught by the OpalParser. Whe it catches exceptions then it calls exit. This is a problem for the optimizer since it's very likely that an individual (optimization perspective) failes while the others run smo...Currently all exceptions are caught by the OpalParser. Whe it catches exceptions then it calls exit. This is a problem for the optimizer since it's very likely that an individual (optimization perspective) failes while the others run smoothly.
OpalParser shouldn't catch any exceptions except ParseErrors.krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/198Distribution-Binomial regression test is broken2019-02-15T08:51:23+01:00snuverink_jjochem.snuverink@psi.chDistribution-Binomial regression test is brokenThe binomial distribution regression test is broken.
According to the nightly tests this happened between [21 July](http://amas.web.psi.ch/opal/regressionTests/master/results_2017-07-21.xml), when the test was failing by a bit, and [23 ...The binomial distribution regression test is broken.
According to the nightly tests this happened between [21 July](http://amas.web.psi.ch/opal/regressionTests/master/results_2017-07-21.xml), when the test was failing by a bit, and [23 July](http://amas.web.psi.ch/opal/regressionTests/master/results_2017-07-23.xml), when the test was off much more.
So between commits b884784 and 3655140:
* 3655140 lift restriction on CORR[X|Y|Z] for binomial distributions
* e331e8b fixing issue with convertion to eV when ratio is small
* 6b08a26 add silencer to all tests
* 1a5bff8 fixing few issues binomial distribution and cleaning up
* acaf84b whitespaces
* 1c0fa9a further improve CMake files for opt-pilot: remove #define GIT_VERSION since already defined in OPAL
* df1840a (tag: OPAL-dev, tag: OPAL-1.9.0) fixing CMake files
* 85bc105 cleaning up Gauss distribution unit test; improve SilenceTest class to print output if tests fail
Of these 1a5bff8 is the most likely culprit. Assigning to @kraus who did all of those commits.krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/196Dumping phase space in global frame (Cyclotron-Tracker)2020-04-22T11:27:56+02:00frey_mDumping phase space in global frame (Cyclotron-Tracker)When dumping the phase space in global frame one obtains bad results if a core does not have particles, e.g.
```
OPAL{0}> * Integration step 0 (no phase space dump for <= 2 particles)
OPAL{0}> * T = 0 ns, Live Particles: 80640000
OPAL{0...When dumping the phase space in global frame one obtains bad results if a core does not have particles, e.g.
```
OPAL{0}> * Integration step 0 (no phase space dump for <= 2 particles)
OPAL{0}> * T = 0 ns, Live Particles: 80640000
OPAL{0}> * E = 71.6 MeV, beta * gamma = 0
OPAL{0}> * Bunch position: R = 0 mm, Theta = 0 Deg, Z = 0 mm
OPAL{0}> * Local Azimuth = -90 Deg, Local Elevation = -nan Deg
```
The reason is the usage of
```
meanR = itsBunch_m->R[0];
meanP = itsBunch_m->P[0];
```
in ```bunchDumpPhaseSpaceData()``` and ```bunchDumpStatData()```.frey_mfrey_mhttps://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/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/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/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/166Placement of elements with PSI different from 0 and pi2017-10-15T22:12:10+02:00krausPlacement of elements with PSI different from 0 and piThe elements between dipoles are placed incorrectly when the dipoles have e.g. PSI = pi/2.The elements between dipoles are placed incorrectly when the dipoles have e.g. PSI = pi/2.OPAL 2.0.0krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/164Compiling OPAL on Daint causes internal compiler error2017-09-18T10:18:43+02:00frey_mCompiling OPAL on Daint causes internal compiler errorWhen compiling OPAL on Piz Daint one obtains an internal compiler error
```
/users/freym/git/opal/src/opt-pilot/Util/MPIHelper.cpp:36:11: required from here
/users/freym/git/opal/src/opt-pilot/Util/Types.h:50:16: internal compiler err...When compiling OPAL on Piz Daint one obtains an internal compiler error
```
/users/freym/git/opal/src/opt-pilot/Util/MPIHelper.cpp:36:11: required from here
/users/freym/git/opal/src/opt-pilot/Util/Types.h:50:16: internal compiler error: Segmentation fault
typedef struct {
^
0xb0248f crash_signal
../../cray-gcc-5.3.0/gcc/toplev.c:383
0xafa0ff layout_decl(tree_node*, unsigned int)
../../cray-gcc-5.3.0/gcc/stor-layout.c:783
0x660ba4 require_complete_types_for_parms
../../cray-gcc-5.3.0/gcc/cp/decl.c:11148
0x660ba4 check_function_type
../../cray-gcc-5.3.0/gcc/cp/decl.c:13297
0x660ba4 start_preparsed_function(tree_node*, tree_node*, int)
../../cray-gcc-5.3.0/gcc/cp/decl.c:13471
0x70f654 synthesize_method(tree_node*)
../../cray-gcc-5.3.0/gcc/cp/method.c:798
0x6b29f3 mark_used(tree_node*, int)
../../cray-gcc-5.3.0/gcc/cp/decl2.c:5196
0x651dc4 build_over_call
../../cray-gcc-5.3.0/gcc/cp/call.c:7536
0x650976 build_new_method_call_1
../../cray-gcc-5.3.0/gcc/cp/call.c:8252
0x650976 build_new_method_call(tree_node*, tree_node*, vec<tree_node*, va_gc, vl_embed>**, tree_node*, int, tree_node**, int)
../../cray-gcc-5.3.0/gcc/cp/call.c:8322
0x64a6ba build_special_member_call(tree_node*, tree_node*, vec<tree_node*, va_gc, vl_embed>**, tree_node*, int, int)
../../cray-gcc-5.3.0/gcc/cp/call.c:7862
0x709877 build_value_init(tree_node*, int)
../../cray-gcc-5.3.0/gcc/cp/init.c:358
0x70de58 perform_member_init
../../cray-gcc-5.3.0/gcc/cp/init.c:646
0x70de58 emit_mem_initializers(tree_node*)
../../cray-gcc-5.3.0/gcc/cp/init.c:1167
0x684656 tsubst_expr
../../cray-gcc-5.3.0/gcc/cp/pt.c:13962
0x6844fc tsubst_expr
../../cray-gcc-5.3.0/gcc/cp/pt.c:14142
0x683267 instantiate_decl(tree_node*, int, bool)
../../cray-gcc-5.3.0/gcc/cp/pt.c:20589
0x6b271d mark_used(tree_node*, int)
../../cray-gcc-5.3.0/gcc/cp/decl2.c:5217
0x651dc4 build_over_call
../../cray-gcc-5.3.0/gcc/cp/call.c:7536
0x650976 build_new_method_call_1
../../cray-gcc-5.3.0/gcc/cp/call.c:8252
Please submit a full bug report,
```frey_mfrey_mhttps://gitlab.psi.ch/OPAL/src/-/issues/163Charge zero in OPAL-cycl & OPAL-t2017-10-02T09:29:53+02:00adelmannCharge zero in OPAL-cycl & OPAL-tCompare beam size of 1.6 and 1.9.x
![opal-cycl](/uploads/e0253f94e8aaec164cae26c992f33eab/opal-cycl.png)
for the IsoDAR cyclotron. Inputfiles can be found on
`merlin-l-01: /gpfs/home/adelmann/scratch/UQ/isodar-1/Accelerated and
...Compare beam size of 1.6 and 1.9.x
![opal-cycl](/uploads/e0253f94e8aaec164cae26c992f33eab/opal-cycl.png)
for the IsoDAR cyclotron. Inputfiles can be found on
`merlin-l-01: /gpfs/home/adelmann/scratch/UQ/isodar-1/Accelerated and
...../Accelerated-1.9`
FUN fact: **Qtot = 0.000**
`
OPAL{0}> * ************** B U N C H *********************************************************
OPAL{0}> * NP = 133000
OPAL{0}> * Qtot = 0.000 [fC] Qi = 1.017 [fC]
OPAL{0}> * Ekin = 361.221 [keV] dEkin = 1.445 [keV]
OPAL{0}> * rmax = ( 3.18003 , 8.91427 , 9.34380 ) [um]
OPAL{0}> * rmin = ( -3.18003 , -8.95209 , -9.36713 ) [um]
OPAL{0}> * rms beam size = ( 1.02826 , 2.91108 , 3.02269 ) [mm]
OPAL{0}> * rms momenta = ( 1.70888e-04 , 3.92498e-05 , 7.85035e-05 ) [beta gamma]
OPAL{0}> * mean position = ( 0.00000 , -0.00000 , 0.00009 ) [um]
OPAL{0}> * mean momenta = ( 2.92045e-15 , 1.96206e-02 , -1.26375e-09 ) [beta gamma]
OPAL{0}> * rms emittance = ( 8.78539e-06 , 5.71264e-06 , 1.18639e-05 ) (not normalized)
OPAL{0}> * rms correlation = ( 2.39105e-04 , 1.14814e-03 , 1.85573e-03 )
OPAL{0}> * hr = ( 0.44096 , 1.23873 , 1.29729 ) [mm]
OPAL{0}> * dh = 2.00000e+00 [%]
OPAL{0}> * t = 0.000 [fs] dT = 28.251 [ps]
OPAL{0}> * spos = 0.000 [um]
OPAL{0}> * **********************************************************************************
`OPAL 1.9.xadelmannwinklehner_dadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/162K0 attribute in RBend2017-10-22T14:14:11+02:00Valeria RizzoglioK0 attribute in RBendIt seems that the attribute K0 (to set the magnetic field) is not working in the RBend element.
In the regression test, if I am not wrong, only the Angle attribute is tested.
From a simple RBend test:
1- if **ANGLE** attribute is us...It seems that the attribute K0 (to set the magnetic field) is not working in the RBend element.
In the regression test, if I am not wrong, only the Angle attribute is tested.
From a simple RBend test:
1- if **ANGLE** attribute is used
```
RBend [2]> 1DPROFILE1-DEFAULT (1D Profile type 1)
RBend [2]> BEND using file 1DPROFILE1-DEFAULT (1D Profile type 1)
RBend [2]>
RBend [2]> Start of field map: 0.146472 m (in s coordinates)
RBend [2]> End of field map: 0.484418 m (in s coordinates)
RBend [2]> Entrance edge of magnet: 0.25 m (in s coordinates)
RBend [2]>
RBend [2]> Reference Trajectory Properties
RBend [2]> ===============================
RBend [2]>
RBend [2]> Bend angle magnitude: 0.523599 rad (30 degrees)
RBend [2]> Entrance edge angle: 0.261799 rad (15 degrees)
RBend [2]> Exit edge angle: 0.261799 rad (15 degrees)
RBend [2]> Bend design radius: 0.249982 m
RBend [2]> Bend design energy: 7e+06 eV
RBend [2]>
RBend [2]> Bend Field and Rotation Properties
RBend [2]> ==================================
RBend [2]>
RBend [2]> Field amplitude: 1.53217 T
RBend [2]> Field index: 0
RBend [2]> Rotation about x axis: 0 rad (0 degrees)
RBend [2]> Rotation about y axis: 0 rad (0 degrees)
RBend [2]> Rotation about z axis: 0 rad (0 degrees)
RBend [2]>
RBend [2]> Reference Trajectory Properties Through Bend Magnet with Fringe Fields
RBend [2]> ======================================================================
RBend [2]>
RBend [2]> Reference particle is bent: 0.523599 rad (30 degrees) in x plane
RBend [2]> Reference particle is bent: 0 rad (0 degrees) in y plane
RBend [2]>
```
2- if **K0** attribute is used:
```
RBend [2]> 1DPROFILE1-DEFAULT (1D Profile type 1)
RBend [2]> BEND using file 1DPROFILE1-DEFAULT (1D Profile type 1)
RBend [2]>
RBend [2]> Start of field map: 0.146472 m (in s coordinates)
RBend [2]> End of field map: -nan m (in s coordinates)
RBend [2]> Entrance edge of magnet: 0.25 m (in s coordinates)
RBend [2]>
RBend [2]> Reference Trajectory Properties
RBend [2]> ===============================
RBend [2]>
RBend [2]> Bend angle magnitude: -nan rad (-nan degrees)
RBend [2]> Entrance edge angle: 0.261799 rad (15 degrees)
RBend [2]> Exit edge angle: -0.261799 rad (-15 degrees)
RBend [2]> Bend design radius: 0.25001 m
RBend [2]> Bend design energy: 7e+06 eV
RBend [2]>
RBend [2]> Bend Field and Rotation Properties
RBend [2]> ==================================
RBend [2]>
RBend [2]> Field amplitude: 1.532 T
RBend [2]> Field index: 0
RBend [2]> Rotation about x axis: 0 rad (0 degrees)
RBend [2]> Rotation about y axis: 0 rad (0 degrees)
RBend [2]> Rotation about z axis: 0 rad (0 degrees)
RBend [2]>
RBend [2]> Reference Trajectory Properties Through Bend Magnet with Fringe Fields
RBend [2]> ======================================================================
RBend [2]>
RBend [2]> Reference particle is bent: -0 rad (-0 degrees) in x plane
RBend [2]> Reference particle is bent: 0 rad (0 degrees) in y plane
RBend [2]>
```
Could, please, someone check?OPAL 2.0.0adelmannkrausadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/158Somehow PSDump has influence on dumped statistics2017-08-18T09:32:49+02:00krausSomehow PSDump has influence on dumped statistics[red has PSDump simultaneously](/uploads/f289a4e3acd9d43703dc6b5c9c5c50fe/influencePSDump.png) This doesn't hurt any further but it's annoying.[red has PSDump simultaneously](/uploads/f289a4e3acd9d43703dc6b5c9c5c50fe/influencePSDump.png) This doesn't hurt any further but it's annoying.OPAL 1.6.0adelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/156The Degrader-1 test yields different results when dks is enabled2020-05-01T10:10:14+02:00krausThe Degrader-1 test yields different results when dks is enabledrms x and rms y seem to be fine, only the energy is affected. On a first inspection of the DKS code (CudaCollimatorPhysics.cu) I couldn't find anything obvious. I have no expertise nor the hardware to debug code for cuda.rms x and rms y seem to be fine, only the energy is affected. On a first inspection of the DKS code (CudaCollimatorPhysics.cu) I couldn't find anything obvious. I have no expertise nor the hardware to debug code for cuda.OPAL 2.4.0locans_ulocans_uhttps://gitlab.psi.ch/OPAL/src/-/issues/153Constraints validation fails2017-11-08T10:25:08+01:00frey_mConstraints validation failsI tried out the constraints with the condition that the number of particles should be greater than zero.
```
...
//c1: CONSTRAINT, EXPR="numParticles > 0";
//objs: OBJECTIVES=(dpeak1,dpeak2,dpeak3_5);
//constrs: CONSTRAINTS = (c1);...I tried out the constraints with the condition that the number of particles should be greater than zero.
```
...
//c1: CONSTRAINT, EXPR="numParticles > 0";
//objs: OBJECTIVES=(dpeak1,dpeak2,dpeak3_5);
//constrs: CONSTRAINTS = (c1);
//opt: OPTIMIZE, OBJECTIVES = objs, DVARS = dvars, CONSTRAINTS = constrs;
...
```
This is a dummy constraint since in our simulation we lose no particles. 'numParticles' is part of the SDDS file, i.e. *.stat file (OPAL 1.6).
For some reason -- I do not understand -- I get following message in [opt.trace.0](/uploads/71d42dd821ddfcc95d3fa165cb5ef5ad/opt.trace.0):
```
invalid individual, constraint "c1" failed to yield true; result: 0
```
OPT-Pilot never finds a solution. Without the constraint, it works fine. The template and data file attached:
[Ring.tmpl](/uploads/c94789c099aa26a0d20acd0daca29f93/Ring.tmpl)
[Ring.data](/uploads/95c2dac28b6a7785e708cc363977957c/Ring.data)
Best,
Matthias :bug:snuverink_jjochem.snuverink@psi.chsnuverink_jjochem.snuverink@psi.chhttps://gitlab.psi.ch/OPAL/src/-/issues/152More than 1 coworker2019-01-10T09:37:22+01:00adelmannMore than 1 coworker**--num-coworkers=2** does not work. Simulation of first generation is not terminating**--num-coworkers=2** does not work. Simulation of first generation is not terminatingYves IneichenYves Ineichenhttps://gitlab.psi.ch/OPAL/src/-/issues/151OPAL does not compile with DKS enabled after recent commits2017-08-14T21:21:16+02:00gsellOPAL does not compile with DKS enabled after recent commits@kraus, @uldis_l:
```
59%] Building CXX object src/CMakeFiles/OPALib.dir/Classic/Structure/LossDataSink.cpp.o
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:38:30: error: ‘const int Coll...@kraus, @uldis_l:
```
59%] Building CXX object src/CMakeFiles/OPALib.dir/Classic/Structure/LossDataSink.cpp.o
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:38:30: error: ‘const int CollimatorPhysics::numpar’ is not a static data member of ‘class CollimatorPhysics’
const int CollimatorPhysics::numpar = 13;
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp: In constructor ‘CollimatorPhysics::CollimatorPhysics(const string&, ElementBase*, std::__cxx11::string&, bool, double)’:
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:77:7: error: class ‘CollimatorPhysics’ does not have any field named ‘curandInitSet’
, curandInitSet(0)
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:78:7: error: class ‘CollimatorPhysics’ does not have any field named ‘ierr’
, ierr(0)
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:79:7: error: class ‘CollimatorPhysics’ does not have any field named ‘maxparticles’
, maxparticles(0)
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:80:7: error: class ‘CollimatorPhysics’ does not have any field named ‘numparticles’
, numparticles(0)
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:81:7: error: class ‘CollimatorPhysics’ does not have any field named ‘par_ptr’
, par_ptr(NULL)
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:82:7: error: class ‘CollimatorPhysics’ does not have any field named ‘mem_ptr’
, mem_ptr(NULL)
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp: In member function ‘void CollimatorPhysics::applyDKS(PartBunch&, size_t)’:
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:875:58: error: cannot allocate an object of abstract type ‘Degrader’
Degrader deg = dynamic_cast<Degrader *>(element_ref_m);
^
In file included from /home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.hh:16:0,
from /home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:9:
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/AbsBeamline/Degrader.h:38:7: note: because the following virtual functions are pure within ‘Degrader’:
class Degrader: public Component {
^
In file included from /home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/AbsBeamline/Component.h:26:0,
from /home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.hh:14,
from /home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:9:
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/AbsBeamline/ElementBase.h:190:29: note: virtual BGeometryBase& ElementBase::getGeometry()
virtual BGeometryBase &getGeometry() = 0;
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/AbsBeamline/ElementBase.h:195:35: note: virtual const BGeometryBase& ElementBase::getGeometry() const
virtual const BGeometryBase &getGeometry() const = 0;
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/AbsBeamline/ElementBase.h:311:26: note: virtual ElementBase* ElementBase::clone() const
virtual ElementBase *clone() const = 0;
^
In file included from /home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.hh:14:0,
from /home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:9:
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/AbsBeamline/Component.h:64:22: note: virtual EMField& Component::getField()
virtual EMField &getField() = 0;
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/AbsBeamline/Component.h:69:28: note: virtual const EMField& Component::getField() const
virtual const EMField &getField() const = 0;
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:875:14: error: cannot declare variable ‘deg’ to be of abstract type ‘Degrader’
Degrader deg = dynamic_cast<Degrader *>(element_ref_m);
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:878:60: error: no matching function for call to ‘CollimatorPhysics::setupCollimatorDKS(PartBunch&, Degrader&, size_t&)’
setupCollimatorDKS(bunch, deg, numParticlesInSimulation);
^
In file included from /home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:9:0:
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.hh:110:10: note: candidate: void CollimatorPhysics::setupCollimatorDKS(PartBunch&, Degrader*, size_t)
void setupCollimatorDKS(PartBunch &bunch, Degrader *deg, size_t numParticlesInSimulation);
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.hh:110:10: note: no known conversion for argument 2 from ‘Degrader’ to ‘Degrader*’
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp: In member function ‘void CollimatorPhysics::setupCollimatorDKS(PartBunch&, Degrader*, size_t)’:
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:1063:51: error: ‘numpar’ was not declared in this scope
par_mp = dksbase_m.allocateMemory<double>(numpar, ierr_m);
^
/home/opalci/NightlyBuild/workspace/OPAL-1.6-DKS/src/src/Classic/Solvers/CollimatorPhysics.cpp:1082:50: error: ‘class Degrader’ has no member named ‘getZSize’
double params[numpar_ms] = {zBegin, deg->getZSize(), rho_m, Z_m,
^
make[2]: *** [src/CMakeFiles/OPALib.dir/Classic/Solvers/CollimatorPhysics.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [src/CMakeFiles/OPALib.dir/all] Error 2
make: *** [all] Error 2
```krauskraus