src issueshttps://gitlab.psi.ch/OPAL/src/-/issues2017-12-21T12:02:11+01:00https://gitlab.psi.ch/OPAL/src/-/issues/193Ippl reduce communication overhead2017-12-21T12:02:11+01:00frey_mIppl reduce communication overheadThe reduce operation in Ippl causes a communication overhead that can be observed for > 200 cores. The operation first does a reduce to the root core followed by a broadcast.The reduce operation in Ippl causes a communication overhead that can be observed for > 200 cores. The operation first does a reduce to the root core followed by a broadcast.frey_mfrey_mhttps://gitlab.psi.ch/OPAL/src/-/issues/82IPPL extra message error2017-12-21T12:02:10+01:00frey_mIPPL extra message errorOPAL crashes for > 16 cores (but works with #cores = 4) with the error message
>>>
Error{0}> get_iter(): no more items in Message
Error{0}> reduce: mismatched element count in vector reduction.
Warning{0}> CommMPI: Found extra message...OPAL crashes for > 16 cores (but works with #cores = 4) with the error message
>>>
Error{0}> get_iter(): no more items in Message
Error{0}> reduce: mismatched element count in vector reduction.
Warning{0}> CommMPI: Found extra message from node 11, tag 10218: msg = Message contains 2 items (0 removed). Contents:
Warning{0}> Item 0: 1 elements, 1 bytes total, needDelete = 0
Warning{0}> Item 1: 3 elements, 24 bytes total, needDelete = 0
>>>
in case of serial x and y directions (i.e. PARFFTX=false, PARFFTY=false) and parallel z direction (i.e. PARFFTT=true). The simulation that was ran is [psiring.in](/uploads/06e3f41f765be149e96b56bd6b277485/psiring.in). The fieldmaps can be found in the repository [AMAS-BDModels / PSI-Ring](https://gitlab.psi.ch/AMAS-BDModels/PSI-Ring/tree/master/Fieldmaps). Following modules were used for running on Merlin:
>>>
module use unstable
module add gcc/5.4.0
module add openmpi/1.10.4
module add hdf5/1.8.18
module add H5hut/2.0.0rc3
module add trilinos/12.10.1
module add gsl/2.2.1
module add boost/1.62.0
>>>
When changing to parallel x, y and serial z, i.e. PARFFTX=true, PARFFTY=true and PARFFTT=false) no error occurs.OPAL 1.9.xfrey_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/25SBEND3D - Local and Global Frame: different particle trajectories2017-12-18T18:21:19+01:00Valeria RizzoglioSBEND3D - Local and Global Frame: different particle trajectoriesThe tracking of the particles in the **LOCAL frame** reveals different behavior with respect to the **GLOBAL frame**
**Field Map**
* 120° Combined Function Magnet
* Reference energy: 230 MeV
**Beam distribution**
* From file...The tracking of the particles in the **LOCAL frame** reveals different behavior with respect to the **GLOBAL frame**
**Field Map**
* 120° Combined Function Magnet
* Reference energy: 230 MeV
**Beam distribution**
* From file: 10000 protons
* First 12 particles are:
```
#ID0: Reference particle
#ID1: Reference particle
#ID2 - #ID9: Particles with defined position and divergence offsets
#ID10: Off-momemtum particle (-11.5 % ) -> py = -0.08531
#ID11: Off-momemtum particle (+13.5 %) -> py = 0.1001511
#ID12: Dispersion function (1 %) -> py = 0.0074186
```
**Tracking** for particles #ID1 (reference), #ID10 and #ID11 (with momentum shift)
* **Global Frame**
![GlobalFrame](/uploads/3ade8aaf8db834db004c57cf8d1e49fa/GlobalFrame.png)
* **Local Frame**
![LocalFrame](/uploads/f079b9a5ee7e43b0918223b3d415f4ba/LocalFrame.png)
**Conclusion**
The particle trajectories in the **LOCAL frame**:
* show a "jump" at 3.8 m, where the field map ends.
* cross the reference trajectory, while in the **GLOBAL frame** the trajectory are separatedOPAL 1.5.2ext-rogers_cext-rogers_chttps://gitlab.psi.ch/OPAL/src/-/issues/194Injected FT gives quaternion isn't unit quaternion. Norm: nan2017-12-18T17:10:19+01:00adelmannInjected FT gives quaternion isn't unit quaternion. Norm: nanThis input file works with *DistOk* and gives an error **quaternion isn't unit quaternion. Norm: nan**
if one tries to inject: *Dist*
```
OPTION, ECHO=FALSE;
OPTION, INFO=FALSE;
OPTION, PSDUMPFREQ = 1000000;
OPTION, STATDUMPFREQ = 10;
...This input file works with *DistOk* and gives an error **quaternion isn't unit quaternion. Norm: nan**
if one tries to inject: *Dist*
```
OPTION, ECHO=FALSE;
OPTION, INFO=FALSE;
OPTION, PSDUMPFREQ = 1000000;
OPTION, STATDUMPFREQ = 10;
OPTION, VERSION=10901;
Title, string="Gun and cavity for Euclid";
REAL BEAM_BUNCH_CHARGE = 10e-12; // Beam bunch charge (C) = I/f = (density * 2Pi * r^2 )/freq
REAL RF_FREQUENCY = 26000.0; // using 26 Ghz
REAL gamma = 1.39139;
REAL beta = sqrt(1-(1/gamma^2));
REAL gammabeta = gamma*beta;
REAL P0 = gamma*beta*EMASS;
DR1: DRIFT, L = 0.5, ELEMEDGE = 0.0;
L1: Line = (DR1);
DistOk: DISTRIBUTION, TYPE = FLATTOP,
SIGMAX = 1.0e-6, SIGMAPX = 0.0,
SIGMAY = 1.0e-6, SIGMAPY = 0.0,
SIGMAZ = 5.0e-5, SIGMAPZ = 0.0,
TRISE = 1.0745e-12, // (s)
TFALL = 1.0745e-12, // See notes above for equation of TRISE
TPULSEFWHM = 1.5e-12, // FWHM length in ti
NBIN = 9,
EMISSIONSTEPS = 100,
EMISSIONMODEL = ASTRA,
EKIN = 0.2,
ELASER = 5.0,
W = 3.2,
FE = 3.2,
CATHTEMP = 321.95,
EMITTED = True,
WRITETOFILE = True;
Dist: DISTRIBUTION, TYPE = FLATTOP,
SIGMAX = 1.0e-6, SIGMAPX = 0.0,
SIGMAY = 1.0e-6, SIGMAPY = 0.0,
SIGMAZ = 5.0e-5, SIGMAPZ = 0.0,
TRISE = 1.0745e-12, // (s)
TFALL = 1.0745e-12, // See notes above for equation of TRISE
TPULSEFWHM = 1.5e-12, // FWHM length in ti
EKIN = 0.2,
ELASER = 5.0,
W = 3.2,
FE = 3.2,
CATHTEMP = 321.95,
EMITTED = False,
WRITETOFILE = True;
FS_SC: Fieldsolver, FSTYPE = FFT,
MX = 8, MY = 8, MT = 16,
PARFFTX = false, PARFFTY = false, PARFFTT = true,
BCFFTX = open, BCFFTY = open, BCFFTT = open,
BBOXINCR = 1, GREENSF = INTEGRATED;
value,{gamma,beta,gammabeta};
beam1: BEAM, PARTICLE = ELECTRON, PC = P0, NPART = 15000,
BCURRENT = BEAM_BUNCH_CHARGE * 26e9, BFREQ = RF_FREQUENCY, CHARGE = -1;
TRACK, LINE = L1, BEAM = beam1, MAXSTEPS = 100000000, DT = 1.0e-13, ZSTOP=0.5;
RUN, METHOD = "PARALLEL-T", BEAM = beam1, FIELDSOLVER = FS_SC, DISTRIBUTION = DIST;
ENDTRACK;
STOP;
```OPAL 1.9.xkrauskraushttps://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/191master dead2017-12-11T09:32:32+01:00adelmannmaster deadWe have to go back to a state where a simple OPAL space charge run is working.
```
OPAL>
OPAL> * **********************************************************************************
OPAL> * Selected Tracking Method == PARALLEL-T, NEW TR...We have to go back to a state where a simple OPAL space charge run is working.
```
OPAL>
OPAL> * **********************************************************************************
OPAL> * Selected Tracking Method == PARALLEL-T, NEW TRACK
OPAL> * **********************************************************************************
[merlin-l-01:18863] *** Process received signal ***
[merlin-l-01:18863] Signal: Segmentation fault (11)
[merlin-l-01:18863] Signal code: (128)
[merlin-l-01:18863] Failing at address: (nil)
[merlin-l-01:18863] [ 0] /usr/lib64/libpthread.so.0(+0xf5e0)[0x2b9a2044d5e0]
[merlin-l-01:18863] [ 1] opal(rffti+0xda)[0xef7bda]
[merlin-l-01:18863] [ 2] opal(_ZN3FFTI11RCTransformLj3EdEC2ERK7NDIndexILj3EES5_RKbi+0x2c7)[0xcc6567]
[merlin-l-01:18863] [ 3] opal(_ZN16FFTPoissonSolverC1EP16UniformCartesianILj3EdEP19CenteredFieldLayoutILj3ES1_4CellENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESC_+0xf5c)[0xcb9e2c]
[merlin-l-01:18863] [ 4] opal(_ZN11FieldSolver10initSolverEP13PartBunchBaseIdLj3EE+0x6e5)[0x9f3225]
[merlin-l-01:18863] [ 5] opal(_ZN8TrackRun16setupFieldsolverEv+0x1ef)[0xd05cff]
[merlin-l-01:18863] [ 6] opal(_ZN8TrackRun13setupTTrackerEv+0x1da)[0xd08eea]
[merlin-l-01:18863] [ 7] opal(_ZN8TrackRun7executeEv+0x5d1)[0xd0be31]
```
Do me this looks like a FFT problem.gsellgsellhttps://gitlab.psi.ch/OPAL/src/-/issues/192some regression-tests use removed keyword DEBIN2017-12-11T09:05:56+01:00adelmannsome regression-tests use removed keyword DEBINDEBIN was removed from the DISTRIBUTION **BUT** the regressiontests are **NOT** updated. We should avoid this ....
Sorry was not able to find out who did this ....
DEBIN was removed from the DISTRIBUTION **BUT** the regressiontests are **NOT** updated. We should avoid this ....
Sorry was not able to find out who did this ....
snuverink_jjochem.snuverink@psi.chsnuverink_jjochem.snuverink@psi.chhttps://gitlab.psi.ch/OPAL/src/-/issues/190BINOMIAL distribution documentation2017-12-08T12:25:32+01:00Valeria RizzoglioBINOMIAL distribution documentationI would suggest to slightly modify the documentation concerning the Binomial distribution documentation.
In particular:
* replace the 'm' in table 15 with 'M' to be consistent with table 16
* specify that the parameters SIGMAX, SIGMA...I would suggest to slightly modify the documentation concerning the Binomial distribution documentation.
In particular:
* replace the 'm' in table 15 with 'M' to be consistent with table 16
* specify that the parameters SIGMAX, SIGMAPX, CORRX etc are still needed. From table 16 it seems that MX, MY and MZ are enough. (Maybe other users are smarter than me and they don't need this additional explanation)
* is there a reason for a default value to 10001.0?OPAL 1.9.xsnuverink_jjochem.snuverink@psi.chsnuverink_jjochem.snuverink@psi.chhttps://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/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/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/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/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/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/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/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/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/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/6A new FFT solver2017-10-22T15:36:40+02:00adelmannA new FFT solverA new [FFT based solver](http://www.sciencedirect.com/science/article/pii/S0010465515003434) is
available and also integrated into DKSA new [FFT based solver](http://www.sciencedirect.com/science/article/pii/S0010465515003434) is
available and also integrated into DKSOPAL 1.9.xadelmannadelmann