src issueshttps://gitlab.psi.ch/OPAL/src/-/issues2017-06-17T20:38:34+02:00https://gitlab.psi.ch/OPAL/src/-/issues/105RectangularDomain::getBoundaryStencil typo2017-06-17T20:38:34+02:00snuverink_jjochem.snuverink@psi.chRectangularDomain::getBoundaryStencil typolines [51-53](https://gitlab.psi.ch/OPAL/src/blob/master/src/Solvers/RectangularDomain.cpp#L51):
```c++
S = -hr[0] * hr[2] / hr[1];
F = -hr[0] * hr[1] / hr[2];
S = -hr[0] * hr[1] / hr[2];
```
The second `S` assignment is lik...lines [51-53](https://gitlab.psi.ch/OPAL/src/blob/master/src/Solvers/RectangularDomain.cpp#L51):
```c++
S = -hr[0] * hr[2] / hr[1];
F = -hr[0] * hr[1] / hr[2];
S = -hr[0] * hr[1] / hr[2];
```
The second `S` assignment is likely a typo and should be `B`, but it would be good if someone could check the formulas.OPAL 1.6.1https://gitlab.psi.ch/OPAL/src/-/issues/102PSDUMPFRAME report is wrong in OPTIOn TELL=TRUE2017-06-17T20:38:34+02:00adelmannPSDUMPFRAME report is wrong in OPTIOn TELL=TRUEThe following trivial OPAL input file:
```
OPTION, TELL=TRUE;
OPTION, PSDUMPFRAME=REFERENCE;
QUIT;
```
shows
OPAL> Current settings of options:
OPAL> OPTION,ECHO=FALSE,INFO=TRUE,TRACE=FALSE,VERIFY=FALSE,WARN=TRUE,
OPAL> SEED=1.2...The following trivial OPAL input file:
```
OPTION, TELL=TRUE;
OPTION, PSDUMPFRAME=REFERENCE;
QUIT;
```
shows
OPAL> Current settings of options:
OPAL> OPTION,ECHO=FALSE,INFO=TRUE,TRACE=FALSE,VERIFY=FALSE,WARN=TRUE,
OPAL> SEED=1.23457e+08,TELL=TRUE,PSDUMPFREQ=10,STATDUMPFREQ=10,
OPAL> PSDUMPEACHTURN=FALSE,PSDUMPLOCALFRAME=FALSE,**PSDUMPFRAME="GLOBAL"**,
OPAL> SPTDUMPFREQ=1,REPARTFREQ=10,REBINFREQ=100,SCSOLVEFREQ=1,
OPAL> MTSSUBSTEPS=1,REMOTEPARTDEL=0,SCAN=FALSE,RHODUMP=FALSE,
OPAL> EBDUMP=FALSE,CSRDUMP=FALSE,AUTOPHASE=0,PPDEBUG=FALSE,
OPAL> SURFDUMPFREQ=-1,NUMBLOCKS=0,RECYCLEBLOCKS=0,NLHS=1,CZERO=FALSE,
OPAL> RNGTYPE="RANDOM",SCHOTTKYCORR=FALSE,SCHOTTKYRENO=-1,ENABLEHDF5=TRUE,
OPAL> ASCIIDUMP=FALSE,BOUNDPDESTROYFQ=10,BEAMHALOBOUNDARY=0,
OPAL> CLOTUNEONLY=FALSE,VERSION=10000;OPAL 1.6.1adelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/106Segfault in case of Material at beginning of beamline2017-07-24T10:29:37+02:00frey_mSegfault in case of Material at beginning of beamlineWe run [sim.in](/uploads/94c1f0db20f572ae97a6a320574d9545/sim.in).
Error output:
```
OPAL>
OPAL> --- BEGIN FIELD LIST ---------------------------------------------------------------
OPAL>
OPAL> --- 0.2 m -- 0.200228 m -- has surface...We run [sim.in](/uploads/94c1f0db20f572ae97a6a320574d9545/sim.in).
Error output:
```
OPAL>
OPAL> --- BEGIN FIELD LIST ---------------------------------------------------------------
OPAL>
OPAL> --- 0.2 m -- 0.200228 m -- has surface physics ------------------------------------
OPAL> DMA_DEG1
OPAL> --- 0.200228 m -- 1.20023 m -- -----------------------------------------------------
OPAL> D1
OPAL>
OPAL> --- END FIELD LIST -----------------------------------------------------------------
OPAL>
[opalrunner:18498] *** Process received signal ***
[opalrunner:18498] Signal: Segmentation fault (11)
[opalrunner:18498] Signal code: Address not mapped (1)
[opalrunner:18498] Failing at address: 0x30
[opalrunner:18498] [ 0] /lib64/libpthread.so.0[0x32ea20f7e0]
[opalrunner:18498] [ 1] opal(_ZN12OpalBeamline14switchElementsERKdS1_S1_RKb+0x1cf)[0xf1829f]
[opalrunner:18498] [ 2] opal[0x10758bd]
[opalrunner:18498] [ 3] opal(_ZN16ParallelTTracker21executeDefaultTrackerEv+0x2c0)[0x107c520]
[opalrunner:18498] [ 4] opal(_ZN16ParallelTTracker7executeEv+0x1f)[0x107d35f]
[opalrunner:18498] [ 5] opal(_ZN8TrackRun7executeEv+0x751)[0x1043b51]
[opalrunner:18498] [ 6] opal(_ZNK10OpalParser7executeEP6ObjectRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x35)[0xcac6c5]
[opalrunner:18498] [ 7] opal(_ZNK10OpalParser11parseActionER9Statement+0x11a)[0xcb062a]
[opalrunner:18498] [ 8] opal(_ZNK10OpalParser5parseER9Statement+0x186)[0xcb0076]
[opalrunner:18498] [ 9] opal(_ZNK10OpalParser3runEv+0x2c)[0xcb158c]
[opalrunner:18498] [10] opal(_ZN8TrackCmd7executeEv+0x343)[0xd63cb3]
[opalrunner:18498] [11] opal(_ZNK10OpalParser7executeEP6ObjectRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x35)[0xcac6c5]
[opalrunner:18498] [12] opal(_ZNK10OpalParser11parseActionER9Statement+0x11a)[0xcb062a]
[opalrunner:18498] [13] opal(_ZNK10OpalParser5parseER9Statement+0x186)[0xcb0076]
[opalrunner:18498] [14] opal(_ZNK10OpalParser3runEv+0x2c)[0xcb158c]
[opalrunner:18498] [15] opal(_ZNK10OpalParser3runEP11TokenStream+0x6a)[0xcb0a8a]
[opalrunner:18498] [16] opal(main+0x8e8)[0xc3f858]
[opalrunner:18498] [17] /lib64/libc.so.6(__libc_start_main+0xfd)[0x32e961ed1d]
[opalrunner:18498] [18] opal[0xc36cb5]
[opalrunner:18498] *** End of error message ***
--------------------------------------------------------------------------
mpirun noticed that process rank 0 with PID 18498 on node opalrunner exited on signal 11 (Segmentation fault).
```
We doesn't crash when we add a drift in front of the material.OPAL 1.6.1adelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/169New Material: BoronCarbide2017-10-19T19:30:25+02:00adelmannNew Material: BoronCarbideOPAL Name: BoronCarbide
A : 55.25
Z : 26
rho : 2.48 g/cm^3
X0 : 50.14 g/cm^2
A2 : 3.963
A3 : 6065
A4 : 1243
A5 : 7.782e-03OPAL Name: BoronCarbide
A : 55.25
Z : 26
rho : 2.48 g/cm^3
X0 : 50.14 g/cm^2
A2 : 3.963
A3 : 6065
A4 : 1243
A5 : 7.782e-03OPAL 1.6.1adelmannadelmannhttps://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/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/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/213Phase output in OPAL-Cycl2018-04-19T10:30:32+02:00baumgartenchristian.baumgarten@psi.chPhase output in OPAL-CyclThe output of the phases in a multiprocessor run involving N nodes is not reliable.
a) if you run the simulation with one core you get all the information about the phases.
b) with more than one core the situation is different: becaus...The output of the phases in a multiprocessor run involving N nodes is not reliable.
a) if you run the simulation with one core you get all the information about the phases.
b) with more than one core the situation is different: because we sample this information always at the same particle (the one with ID==0) and only node==0 is writing, you only see phase information iff particle with ID==0 is on node 0.OPAL 1.6.1adelmannadelmann