src issueshttps://gitlab.psi.ch/OPAL/src/-/issues2018-12-10T14:30:45+01:00https://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/247Strange Probe behavior2018-12-10T14:30:45+01:00luethi_mStrange Probe behaviorThe Probes in OPAL 2.0.0 also show a strange behavior.
I placed a test probe in the cyclotron. Every particle in the cyclotron goes through this probe exactly once.
I noticed that some particles are counted twice, some particles not at a...The Probes in OPAL 2.0.0 also show a strange behavior.
I placed a test probe in the cyclotron. Every particle in the cyclotron goes through this probe exactly once.
I noticed that some particles are counted twice, some particles not at all.
I made a minimal example to show the problem.
This is the input file:
[comet_min_example.in](/uploads/6ca49aab2a954fb42fb7bd958c054f7d/comet_min_example.in)
The magnetic field map:
[BMap_Dummy_m.txt](/uploads/1d796cbaeddf63359605094c31d57745/BMap_Dummy_m.txt)
Here is a plot of the tracks:
![probe](/uploads/6aa0aaa1410d4d4dc578026b38674ff4/probe.png)
You see clearly, that every particle goes through the probe.
The simulation was done with NPART=1000. However in the PROBE.hist file, only 996 particles are counted.
With this example I was not able to reproduce a situation where some particles are counted twice, but this also happened in my original simulation.snuverink_jjochem.snuverink@psi.chfrey_msnuverink_jjochem.snuverink@psi.chhttps://gitlab.psi.ch/OPAL/src/-/issues/248Problems with flexible collimator when used with optimizer2018-11-20T20:30:57+01:00adelmannProblems with flexible collimator when used with optimizerI am getting messages like this:
```
░No reference point provided: using the origin
Individual not viable, I try again: iter= 0
Individual not viable, I try again: iter= 0
░No reference point provided: using the origin
Individua...I am getting messages like this:
```
░No reference point provided: using the origin
Individual not viable, I try again: iter= 0
Individual not viable, I try again: iter= 0
░No reference point provided: using the origin
Individual not viable, I try again: iter= 0
Individual not viable, I try again: iter= 1
Individual not viable, I try again: iter= 2
```
and then the optimisation is killed with
```
===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= PID 61951 RUNNING AT bdw-0026
= EXIT CODE: 9
= CLEANING UP REMAINING PROCESSES
= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
Intel(R) MPI Library troubleshooting guide:
https://software.intel.com/node/561764
===================================================================================
```
No further information !
All simulation in progress, at the time when the optimisation is killed,
are terminating just fine.
There is the new flexible collimator involved and a constraint w.r.t. number of particles.
When removing the flexible collimator the optimisation works just fine.
Will add input files later. Need to catch my airplane now!krausadelmannkraushttps://gitlab.psi.ch/OPAL/src/-/issues/230Non-existing objective gives segfault2018-06-22T11:11:14+02:00snuverink_jjochem.snuverink@psi.chNon-existing objective gives segfaultAs seen with @frey_m: in the `OPTIMIZE` command, a non-existing objective gives a segfault. Rather a warning should be printed.
```
OPAL{0}> opal opt-pilot/optRing.in --inputfile=template/Ring.tmpl --outfile=RingOpt --outdir=RingOpt --i...As seen with @frey_m: in the `OPTIMIZE` command, a non-existing objective gives a segfault. Rather a warning should be printed.
```
OPAL{0}> opal opt-pilot/optRing.in --inputfile=template/Ring.tmpl --outfile=RingOpt --outdir=RingOpt --initialPopulation=31 --num-masters=1 --num-coworkers=1 --num-ind-gen=31 --maxGenerations=30 --gene-mutation-probability=0.5 --mutation-probability=0.5 --recombination-probability=0.5 --simtmpdir=/home/scratch/AMAS-BDSModels/PSI-Ring/tmp --templates=/home/scratch/AMAS-BDSModels/PSI-Ring/template
[pc12290:09252] *** Process received signal ***
[pc12290:09252] Signal: Segmentation fault (11)
[pc12290:09252] Signal code: Address not mapped (1)
[pc12290:09252] Failing at address: 0x10
[pc12290:09249] *** Process received signal ***
[pc12290:09249] Signal: Segmentation fault (11)
[pc12290:09249] Signal code: Address not mapped (1)
[pc12290:09249] Failing at address: 0x10
[pc12290:09252] [ 0] [pc12290:09249] [ 0] /lib64/libpthread.so.0[0x3ab660f7e0]
[pc12290:09249] [ 1] /lib64/libpthread.so.0[0x3ab660f7e0]
[pc12290:09252] [ 1] opal(_ZNK9Objective13getExpressionB5cxx11Ev+0x1)[0x710301]
[pc12290:09252] opal(_ZNK9Objective13getExpressionB5cxx11Ev+0x1)[0x710301]
[pc12290:09249] [ 2] [ 2] -------------------------------------------------------
Primary job terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
-------------------------------------------------------
opal(_ZN11OptimizeCmd7executeEv+0x24cb)[0x6d679b]
[pc12290:09249] [ 3] opal(_ZN11OptimizeCmd7executeEv+0x24cb)[0x6d679b]
[pc12290:09252] [ 3] opal(_ZNK10OpalParser7executeEP6ObjectRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x3a)[0x6c8b1a]
[pc12290:09249] [ 4] opal(_ZNK10OpalParser11parseActionER9Statement+0x142)[0x6cce92]
[pc12290:09249] [ 5] opal(_ZNK10OpalParser5parseER9Statement+0x173)[0x6cc733]
[pc12290:09249] [ 6] opal(_ZNK10OpalParser3runEv+0x2c)[0x6c87bc]
[pc12290:09249] [ 7] opal(_ZNK10OpalParser3runEP11TokenStream+0x70)[0x6cd5b0]
[pc12290:09249] [ 8] opal(main+0x1e8f)[0x618bef]
[pc12290:09249] [ 9] /lib64/libc.so.6(__libc_start_main+0xfd)[0x3ab5e1ed1d]
[pc12290:09249] [10] opal[0x60b559]
[pc12290:09249] *** End of error message ***
opal(_ZNK10OpalParser7executeEP6ObjectRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x3a)[0x6c8b1a]
[pc12290:09252] [ 4] opal(_ZNK10OpalParser11parseActionER9Statement+0x142)[0x6cce92]
[pc12290:09252] [ 5] opal(_ZNK10OpalParser5parseER9Statement+0x173)[0x6cc733]
[pc12290:09252] [ 6] opal(_ZNK10OpalParser3runEv+0x2c)[0x6c87bc]
[pc12290:09252] [ 7] opal(_ZNK10OpalParser3runEP11TokenStream+0x70)[0x6cd5b0]
[pc12290:09252] [ 8] opal(main+0x1e8f)[0x618bef]
[pc12290:09252] [ 9] /lib64/libc.so.6(__libc_start_main+0xfd)[0x3ab5e1ed1d]
[pc12290:09252] [10] opal[0x60b559]
[pc12290:09252] *** End of error message ***
```snuverink_jjochem.snuverink@psi.chsnuverink_jjochem.snuverink@psi.chhttps://gitlab.psi.ch/OPAL/src/-/issues/143BoundaryGeometries VTK output produces odd results2018-05-16T13:12:14+02:00krausBoundaryGeometries VTK output produces odd resultsUsed the SAAMG-Test-1 to produce [attached screenshot](/uploads/695901d8c9e8a2e7afc37278f666eef7/Pipe_1m_10cm.png) (serial and parallel).Used the SAAMG-Test-1 to produce [attached screenshot](/uploads/695901d8c9e8a2e7afc37278f666eef7/Pipe_1m_10cm.png) (serial and parallel).gsellgsellhttps://gitlab.psi.ch/OPAL/src/-/issues/223The flexible collimator yields different results on different computers2018-04-19T09:16:01+02:00krausThe flexible collimator yields different results on different computersThe regression tests slit-1 and slit-2 fail on opalrunner while they yield correct results on my laptop.The regression tests slit-1 and slit-2 fail on opalrunner while they yield correct results on my laptop.krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/220Missing unit attributes in H5 file in OPAL-Cycl2018-04-11T09:12:23+02:00frey_mMissing unit attributes in H5 file in OPAL-CyclThe H5-file for OPAL-Cycl does not write the units of following attributes:
* centroid
* minX, maxX
* minP, maxP
* LOCAL
* REFPR
* REFPT
* REFPU
* REFTHETA
* REFZ
* AZIMUTH
* ELEVATION
* Ex, Ey, Ez
* Bx, By, Bz
* rhoThe H5-file for OPAL-Cycl does not write the units of following attributes:
* centroid
* minX, maxX
* minP, maxP
* LOCAL
* REFPR
* REFPT
* REFPU
* REFTHETA
* REFZ
* AZIMUTH
* ELEVATION
* Ex, Ey, Ez
* Bx, By, Bz
* rhoOPAL 1.9.xsnuverink_jjochem.snuverink@psi.chsnuverink_jjochem.snuverink@psi.chhttps://gitlab.psi.ch/OPAL/src/-/issues/219Missing header attributes for H5 in OPAl-T2018-04-11T09:12:23+02:00frey_mMissing header attributes for H5 in OPAl-TThe H5PartWrapper for OPAL-T does not write all units into the header. E.g. the phase space variables are missing. For OPAL-Cycl they are in
```
WRITESTRINGFILEATTRIB(file_m, "xUnit", "m");
WRITESTRINGFILEATTRIB(file_m, "yUnit", "m");
W...The H5PartWrapper for OPAL-T does not write all units into the header. E.g. the phase space variables are missing. For OPAL-Cycl they are in
```
WRITESTRINGFILEATTRIB(file_m, "xUnit", "m");
WRITESTRINGFILEATTRIB(file_m, "yUnit", "m");
WRITESTRINGFILEATTRIB(file_m, "zUnit", "m");
WRITESTRINGFILEATTRIB(file_m, "pxUnit", "#beta#gamma");
WRITESTRINGFILEATTRIB(file_m, "pyUnit", "#beta#gamma");
WRITESTRINGFILEATTRIB(file_m, "pzUnit", "#beta#gamma");
```OPAL 1.9.xfrey_madelmannfrey_mhttps://gitlab.psi.ch/OPAL/src/-/issues/216FindHDF5 is broken2018-04-09T21:41:15+02:00gsellFindHDF5 is brokenThe FindHDF5 in OPAL is broken. If you link static the order of libraries matters on Linux. Linking with a static HDF5 library will most likely fail since the libraries required by libhdf5.a are not listed after libhdf5.a:
Linking with
...The FindHDF5 in OPAL is broken. If you link static the order of libraries matters on Linux. Linking with a static HDF5 library will most likely fail since the libraries required by libhdf5.a are not listed after libhdf5.a:
Linking with
```
g++ -o opal ... -ldl -lm -lz ... -lhdf5
```
will fail on Linux with a static HDF5 library. This will do:
```
g++ -o opal ... -ldl -lm -lz ... -lhdf5 -ldl -lm -lz
```OPAL-1.6.2gsellgsellhttps://gitlab.psi.ch/OPAL/src/-/issues/208Destructors are noexcept(true) in C++112018-03-22T16:33:26+01:00frey_mDestructors are noexcept(true) in C++11With ```gcc/7.3.0``` one gets the following warning due to the ```CLOSE_FILE``` macro in ```LossDataSink```:
```
src/Classic/Structure/LossDataSink.cpp: In destructor 'LossDataSink::~LossDataSink()':
/scratch1/scratchdirs/frey_m/libs/op...With ```gcc/7.3.0``` one gets the following warning due to the ```CLOSE_FILE``` macro in ```LossDataSink```:
```
src/Classic/Structure/LossDataSink.cpp: In destructor 'LossDataSink::~LossDataSink()':
/scratch1/scratchdirs/frey_m/libs/opal/src/src/Classic/Structure/LossDataSink.cpp:100:70: warning: throw will always call terminate() [-Wterminate]
throw GeneralClassicException(std::string(__func__), ss.str()); \
^
/scratch1/scratchdirs/frey_m/libs/opal/src/src/Classic/Structure/LossDataSink.cpp:156:9: note: in expansion of macro 'CLOSE_FILE'
CLOSE_FILE ();
^
/scratch1/scratchdirs/frey_m/libs/opal/src/src/Classic/Structure/LossDataSink.cpp:100:70: note: in C++11 destructors default to noexcept
throw GeneralClassicException(std::string(__func__), ss.str()); \
```
As the warning explains: In C++11 destructors are ```noexcept(true)``` by default. I'll fix this by setting the destructor ```noexcept(false)``` explicitly.OPAL 1.9.xfrey_mfrey_mhttps://gitlab.psi.ch/OPAL/src/-/issues/73'RestartTest-2' fails on master branch2018-03-20T10:08:59+01:00gsell'RestartTest-2' fails on master branch'RestartTest-2' fails with the following error message:
```
Error{0}> get_iter(): no more items in Message
Error{0}> reduce: mismatched element count in vector reduction.
```'RestartTest-2' fails with the following error message:
```
Error{0}> get_iter(): no more items in Message
Error{0}> reduce: mismatched element count in vector reduction.
```OPAL 1.9.xadelmannadelmannhttps://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/2option SCAN broken2018-01-09T09:27:20+01:00adelmannoption SCAN brokenThe option SCAN is broken.The option SCAN is broken.OPAL 1.9.xadelmannadelmannhttps://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/14Particles stored in trackOrbit.dat2018-01-05T08:58:48+01:00Valeria RizzoglioParticles stored in trackOrbit.datAccording to the OPAL manual (pag. 40):
**Multi-particle tracking mode**
The intermediate phase space data of centeral particle (with ID of 0) and an off-centering particle (with ID of 1) are stored in an ASCII file.
Concernin...According to the OPAL manual (pag. 40):
**Multi-particle tracking mode**
The intermediate phase space data of centeral particle (with ID of 0) and an off-centering particle (with ID of 1) are stored in an ASCII file.
Concerning the particle with *ID0*:
* particle position is not updated in case OFFSETY > 0 is set in the distribution definition. The tracking of this particle does not reflect the beam behavior (because of the offset)
* Is the general idea: ID0 particle = reference particle?
Concerning the particle with *ID1*:
* ***Distribution from file:*** the second particle in the distribution file is used as ID1
* ***Generated distribution:*** It seems that a random particle from the distribution is set as ID1
A possible suggestion:
* ***Distribution from file:*** the first and the second particle in the file are used as ID0 and ID1, respectively. The user is completely free to decide which particles track.
* ***Generated distribution (Option 1):*** ID0 is by default assigned to the reference particle (with updated offset). An option can be added to the DISTRIBUTION command where the user can specify which particle uses as ID1 (ie: DISPERSION, CENTROID or USERDEF or NULL = not stored). This means that the first two particles generated by OPAL are replaced with ID0 (reference) and ID1, if option NULL is not specified.
* ***Generated distribution (Option 2):*** An option can be added to the DISTRIBUTION command where the user can specify which particle uses as ID0 and ID1 (ie: DISPERSION, CENTROID or USERDEF or or NULL = not stored)
A possible problem could arise in case of multi-distribution or vector of distributionOPAL 1.5.1adelmannadelmannhttps://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/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/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_c