src issueshttps://gitlab.psi.ch/OPAL/src/-/issues2018-06-05T09:22:31+02:00https://gitlab.psi.ch/OPAL/src/-/issues/207Virtual memory exhausted2018-06-05T09:22:31+02:00adelmannVirtual memory exhaustedDoes anybody know this error?
```
*** Error:
Error{3}> *** in line 76 of file "opal_FermiD.in":
Error{3}> RUN,METHOD="PARALLEL-T",BEAM=BEAM1,FIELDSOLVER=FS1,DISTRIBUTION=DIST1;
Error{3}> Sorry, virtual memory exhausted.
```
I’...Does anybody know this error?
```
*** Error:
Error{3}> *** in line 76 of file "opal_FermiD.in":
Error{3}> RUN,METHOD="PARALLEL-T",BEAM=BEAM1,FIELDSOLVER=FS1,DISTRIBUTION=DIST1;
Error{3}> Sorry, virtual memory exhausted.
```
I’m trying to simulated a NONEQUIL- emission from a cathode.
The files are at merlin-l-01:~adelmann/KuskeOPAL 2.0.0krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/206Cyclotron elements require end position to have larger radius than start posi...2018-12-10T14:30:45+01:00snuverink_jjochem.snuverink@psi.chCyclotron elements require end position to have larger radius than start positionFound with @nesteruk_k:
In the [current implementation](https://gitlab.psi.ch/OPAL/src/blob/master/src/Classic/AbsBeamline/Probe.cpp#L195) it is assumed that the Probe (x,y) end position has a larger radius than the (x,y) starting posit...Found with @nesteruk_k:
In the [current implementation](https://gitlab.psi.ch/OPAL/src/blob/master/src/Classic/AbsBeamline/Probe.cpp#L195) it is assumed that the Probe (x,y) end position has a larger radius than the (x,y) starting position.
If not, almost no particles are recorded. This is not documented and without warning not very user-friendly, therefore labelling this a bug. For 1.6 perhaps a documentation update would be enough.
EDIT (23 April): (C)Collimator, Septum, Stripper make the same assumption.snuverink_jjochem.snuverink@psi.chsnuverink_jjochem.snuverink@psi.chhttps://gitlab.psi.ch/OPAL/src/-/issues/205ippl/tests2018-02-09T10:58:07+01:00adelmannippl/testsI need to build IPPL tests for benchmarking purposes.
How do we build these day's?I need to build IPPL tests for benchmarking purposes.
How do we build these day's?krausfrey_mkraushttps://gitlab.psi.ch/OPAL/src/-/issues/204rename opt-Pilot function sameSDDSVariableAt to statVariableAt2018-01-20T14:15:19+01:00krausrename opt-Pilot function sameSDDSVariableAt to statVariableAtI think the name `sameSDDSVariableAt` isn't a good choice (if I remember correctly it was my own...). This function uses the results of the `.stat` file. Accordingly it should be called `statVariableAt`.I think the name `sameSDDSVariableAt` isn't a good choice (if I remember correctly it was my own...). This function uses the results of the `.stat` file. Accordingly it should be called `statVariableAt`.adelmannkrausadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/203Structure/H5PartWrapper.cpp Error2018-01-11T08:45:06+01:00adelmannStructure/H5PartWrapper.cpp ErrorOn merlin: */gpfs/home/adelmann/scratch/opal-scaling/Merlin/test* check **scaling-1.o92428**
`Error{91}> H5 rc= -2 in /gpfs/home/adelmann/opal/opal-1.9/src/Structure/H5PartWrapper.cpp @ line 94`
The simulation does not crash maybe als...On merlin: */gpfs/home/adelmann/scratch/opal-scaling/Merlin/test* check **scaling-1.o92428**
`Error{91}> H5 rc= -2 in /gpfs/home/adelmann/opal/opal-1.9/src/Structure/H5PartWrapper.cpp @ line 94`
The simulation does not crash maybe also because **OPTION, PSDUMPFREQ = 1E9;**OPAL 2.0.0krausgsellkraushttps://gitlab.psi.ch/OPAL/src/-/issues/202Scan-1 regression test is broken2018-03-30T19:06:21+02:00snuverink_jjochem.snuverink@psi.chScan-1 regression test is brokenNow that the Scan option is fixed (issue #2) the regression test [Scan-1](https://gitlab.psi.ch/OPAL/regression-tests/tree/master/RegressionTests/Scan-1) looks [better](http://amas.web.psi.ch/opal/regressionTests/master/results_2018-01-0...Now that the Scan option is fixed (issue #2) the regression test [Scan-1](https://gitlab.psi.ch/OPAL/regression-tests/tree/master/RegressionTests/Scan-1) looks [better](http://amas.web.psi.ch/opal/regressionTests/master/results_2018-01-08.xml#Scan-1_rms_x), but is still broken.
@kraus: do you perhaps understand why?OPAL 2.0.0snuverink_jjochem.snuverink@psi.chsnuverink_jjochem.snuverink@psi.chhttps://gitlab.psi.ch/OPAL/src/-/issues/201Stat file dumping in ParallelCyclotronTracker2018-04-09T12:19:50+02:00frey_mStat file dumping in ParallelCyclotronTrackerThis issue is related to the discussion in #196. I'd like to fix the dumping and reference particle in the cyclotron tracker such that it works and gives reasonable results for single as well as multi bunch simulations. My idea is to wri...This issue is related to the discussion in #196. I'd like to fix the dumping and reference particle in the cyclotron tracker such that it works and gives reasonable results for single as well as multi bunch simulations. My idea is to write a stat-file per bunch. What do you think?OPAL 1.9.xfrey_mfrey_mhttps://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/197Scan-1 regression test is broken2017-12-21T12:07:54+01:00snuverink_jjochem.snuverink@psi.chScan-1 regression test is brokenThe [Scan-1 regression test](https://gitlab.psi.ch/OPAL/regression-tests/tree/master/RegressionTests/Scan-1) is broken since the beginning of the year.
It seems there were no significant changes to the test.
One thing I don't understan...The [Scan-1 regression test](https://gitlab.psi.ch/OPAL/regression-tests/tree/master/RegressionTests/Scan-1) is broken since the beginning of the year.
It seems there were no significant changes to the test.
One thing I don't understand is why in master the simulation starts at a later s-position, s=0.15m instead of the reference of s=0.0m.
The regression plots show it best:
http://amas.web.psi.ch/opal/regressionTests/master/results_2017-12-19.xml#Scan-1_rms_xhttps://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/195Strange element positions RINGDEFINITION2018-05-18T16:22:00+02:00Valeria RizzoglioStrange element positions RINGDEFINITIONI tried to run my simulation using the RINGDEFINITION and Sbend3D with OPAL/1.9.
Starting from the input file properly running with OPAL/1.6, I have
* update the version number
* replace DISTRIBUTION=FROMFILE with TYPE=FROMFILE
all t...I tried to run my simulation using the RINGDEFINITION and Sbend3D with OPAL/1.9.
Starting from the input file properly running with OPAL/1.6, I have
* update the version number
* replace DISTRIBUTION=FROMFILE with TYPE=FROMFILE
all the rest of the input file is unchanged.
I realized that there is a problem with the element position:
* OPAL1.6 (correct)
```
OPAL> * Added OFFSET to Ring
OPAL> * Start position (-1547.1, 9.47297e-14, 0) normal (6.12303e-17, 1, 0), phi 6.12303e-17
OPAL> * End position (-1547.1, 1800, 0) normal (6.12303e-17, 1, 0)
OPAL> * Added MAPS to Ring
OPAL> * Start position (-1547.1, 1800, 0) normal (6.12303e-17, 1, 0), phi 6.12303e-17
OPAL> * End position (1297.51, 2642.61, 0) normal (0.544639, -0.838671, 0)
```
* OPAL1.9
```
OPAL> * Added OFFSET to Ring
OPAL> * Start position (-1.5471e+06, 9.47297e-11, 0) normal (6.12303e-17, 1, 0), phi 6.12303e-17
OPAL> * End position (-1.5471e+06, 1800, 0) normal (6.12303e-17, 1, 0)
OPAL> * Added MAPS to Ring
OPAL> * Start position (-1.5471e+06, 1800, 0) normal (6.12303e-17, 1, 0), phi 6.12303e-17
OPAL> * End position (-1.54426e+06, 2642.61, 0) normal (0.544639, -0.838671, 0)
```
Are there modification also to RINGDEFINITION element between OPAL/1.6 and OPAL/1.9? I don't get any warning or error message.OPAL 2.0.0ext-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/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/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/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/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/189DESIGNENERGY and Field map extension2020-06-09T12:08:54+02:00Valeria RizzoglioDESIGNENERGY and Field map extensionAccording to the manual for OPAL <=1.6:
> If the bend strength is set by K0 and/or K0S, then the actual beam will be bent a different angle if its energy
> does not correspond to the DESIGNENERGY of the bend
A beam energy different fro...According to the manual for OPAL <=1.6:
> If the bend strength is set by K0 and/or K0S, then the actual beam will be bent a different angle if its energy
> does not correspond to the DESIGNENERGY of the bend
A beam energy different from DESIGNENERGY would change the bending radius and angle depending on K0. The beam trajectory matches always with the reference path inside the dipole.
The bending radius defines the extension of the field map. It is not clear to me **if and how the redefinition of bending radius (due to a beam energy different from DESIGNENERGY) impacts on the field map extension.**krauskraushttps://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]
```gsellgsell