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/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/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/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/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/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/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/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.1krauskraus