src issueshttps://gitlab.psi.ch/OPAL/src/-/issues2017-03-20T11:29:27+01:00https://gitlab.psi.ch/OPAL/src/-/issues/54documentation2017-03-20T11:29:27+01:00adelmanndocumentationI am unable to tex the doc on my MAC.
version.tex is not found.
Who is creating version.tex?I am unable to tex the doc on my MAC.
version.tex is not found.
Who is creating version.tex?krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/53Layout-file (ascii-file with coordinates)2017-08-29T21:42:12+02:00baumgartenchristian.baumgarten@psi.chLayout-file (ascii-file with coordinates)It would be important not only for cross-checks but also for cooperation with engineers, to have the layout (numerical values) from OPAL. Especially useful are the central mechanical coordinates of the quadrupoles and the so-called "vert...It would be important not only for cross-checks but also for cooperation with engineers, to have the layout (numerical values) from OPAL. Especially useful are the central mechanical coordinates of the quadrupoles and the so-called "vertex"-points of dipoles (virtual intersection of the straights). A drawing is nice, but to compare the numerical data using sub-millimeter precision with drawings (or data from survey) is extremely important.OPAL 1.9.xhttps://gitlab.psi.ch/OPAL/src/-/issues/52Restarting from different file not working2019-10-25T13:47:36+02:00krausRestarting from different file not workingOPAL detects the following error when using restartfn to use a given h5 file :
User error detected by function "H5PartWrapper::copyHeader"
Error{3}> *** in line 118 of file "RestartTest-5.in" at end of statement:
Error{1}> RUN,METHOD...OPAL detects the following error when using restartfn to use a given h5 file :
User error detected by function "H5PartWrapper::copyHeader"
Error{3}> *** in line 118 of file "RestartTest-5.in" at end of statement:
Error{1}> RUN,METHOD="PARALLEL-T",BEAM=BEAM1,FIELDSOLVER=FS1,DISTRIBUTION=DIST1;
Error{1}> unknown data type: 0krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/51RestartTest-6 fails on master branch2017-03-16T14:25:46+01:00gsellRestartTest-6 fails on master branchRestartTest-6 never stops runningRestartTest-6 never stops runningOPAL 1.9.xkrauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/50RestartTest-3 test fails on master branch2017-03-16T14:26:17+01:00gsellRestartTest-3 test fails on master branchRestartTest-3 never stops runningRestartTest-3 never stops runningOPAL 1.9.xkrauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/49RestartTest-2 fails on master branch2017-03-16T14:21:46+01:00gsellRestartTest-2 fails on master branchRestartTest-2 never stops runningRestartTest-2 never stops runningOPAL 1.9.xadelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/48RestartTest-1 fails on master branch2017-03-16T14:26:39+01:00gsellRestartTest-1 fails on master branchRestartTest-1 never stopsRestartTest-1 never stopsOPAL 1.9.xkrauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/47Erice Work List2018-06-12T10:12:45+02:00adelmannErice Work ListWe should start with a list of things we want to achiveWe should start with a list of things we want to achiveOPAL 2.0.0adelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/46Renaming of Surfacephysics2018-05-01T15:08:03+02:00frey_mRenaming of SurfacephysicsMarco Schippers suggested to rename "Surfacephysics" to something more suitable (e.g. "Materialphysics"). The other description is misleading.Marco Schippers suggested to rename "Surfacephysics" to something more suitable (e.g. "Materialphysics"). The other description is misleading.OPAL 1.9.xhttps://gitlab.psi.ch/OPAL/src/-/issues/45Unification of OPAL-Cyc and OPAL-T2021-06-10T18:11:10+02:00frey_mUnification of OPAL-Cyc and OPAL-TAccording to the OPAL round table meeting of today (i.e. 2. March 2017) we need to unify the OPAL flavors OPAL-T and OPAL-Cyc in the following points:
- units
- convention of vertical and longitudinal plane
- definition of particle dist...According to the OPAL round table meeting of today (i.e. 2. March 2017) we need to unify the OPAL flavors OPAL-T and OPAL-Cyc in the following points:
- units
- convention of vertical and longitudinal plane
- definition of particle distribution (i.e. different meaning of py)
- OPAL-Cyc allows single particle tracking but in OPAL-T minimum 10 particles are needed
The points are also listed in Valeria's wiki page at point
[OPAL-Cyc: RINGDEFINITION](https://gitlab.psi.ch/AMAS-members/rizzoglio_v/wikis/OPAL_Meeting.html)adelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/44Adding outer aperture to elements2021-06-10T18:11:27+02:00krausAdding outer aperture to elementsCurrently OPAL-T only knows one aperture: if a particle is outside this aperture then it doesn't see the effect of the element, but it isn't stopped. We can't just kill all particles that are "outside" the element since the elements are ...Currently OPAL-T only knows one aperture: if a particle is outside this aperture then it doesn't see the effect of the element, but it isn't stopped. We can't just kill all particles that are "outside" the element since the elements are placed in 3D space (consider circular lattices of e.g. ERLs). Solution an outer aperture. Kill the particle if it is inside the outer but outside the inner aperture. Use 10 * beta * c * dt as default for thickness of outer aperture.krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/43Add WARP attribute to collimators2021-10-13T09:28:24+02:00krausAdd WARP attribute to collimatorsAll elements except the dipoles have a stright geometry in OPAL-T. Somtimes it would be nice if an element could warp to fit the design path. This should be fairly easy to apply to passive elements such as a collimator. More effort is ne...All elements except the dipoles have a stright geometry in OPAL-T. Somtimes it would be nice if an element could warp to fit the design path. This should be fairly easy to apply to passive elements such as a collimator. More effort is needed for multipoles / other magnets.krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/42APERTURE attribute does not work2019-11-06T10:22:10+01:00Valeria RizzoglioAPERTURE attribute does not workI test the following element without surface physics (as reported on the OPAL manual: **18.5 Example of an Input File**):
`FX5: SLIT, L=0.09, ELEMEDGE=0.01,APERTURE={0.005,0.003};`
This command is not recognized by OPAL and the ...I test the following element without surface physics (as reported on the OPAL manual: **18.5 Example of an Input File**):
`FX5: SLIT, L=0.09, ELEMEDGE=0.01,APERTURE={0.005,0.003};`
This command is not recognized by OPAL and the slit has no aperture:
```
OPAL[3]> * Slit x= 0 Slit y= 0 start= 0.01 fn=
Ippl[3]> FX5 gone live
```
Btw this information is displayed only with `--info 3`.
I could reproduce the same effect with different OPAL versions:
* **OPAL1.4.0 released version:** the beam is lost without any error or warning messages
```
OPAL >
OPAL > * ************** B U N C H *********************************************************
OPAL > * NP = 10000
OPAL > * Qtot = 1.60000e-06 [nC] Qi = 1.60000e-10 [nC]
....
OPAL > * spos = 9.14511e-03 [m]
OPAL > * **********************************************************************************
OPAL >
OPAL >
OPAL > * ************** B U N C H *********************************************************
OPAL > * NP = 1
OPAL > * Qtot = 1.60000e-10 [nC] Qi = 1.60000e-10 [nC]
....
OPAL > * spos = 1.00250e-01 [m]
OPAL > * **********************************************************************************
OPAL >
Ippl> Save FX5.h5
OPAL> done executing ParallelTTracker at 10:43:43
```
* **OPAL/1.5.1-20170217:** the beam is lost but at least there is an error message
```
ParallelTTracker > * Deleted 10000 particles, remaining 0 particles
Warning> reduce: there was nothing to reduce, since the masks were all false.
Warning> reduce: there was nothing to reduce, since the masks were all false.
Warning> reduce: there was nothing to reduce, since the masks were all false.
Warning> reduce: there was nothing to reduce, since the masks were all false.
Warning> reduce: there was nothing to reduce, since the masks were all false.
```
* **Solution and Request**
1- **Don't fix it:** in this case the APERTURE has to be removed as element attribute and delete every reference from the manual
2- **Fix it:** would be the nicer solution since it should allow to create asymmetric apertures in collimators and slits, otherwise not possibleOPAL 1.5.1adelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/41Stat file: OPAL version at the end of the header2017-02-21T13:58:00+01:00frey_mStat file: OPAL version at the end of the headerIn ROGER, we search for "OPAL " that is written at the end of the header in order to parse the stat file.
So, ROGER expects something like:
```
&data mode=ascii, no_row_counts=1 &end
8
OPAL 1.5.00.1 git rev. 2a9d889cc345b2130f9d7171d...In ROGER, we search for "OPAL " that is written at the end of the header in order to parse the stat file.
So, ROGER expects something like:
```
&data mode=ascii, no_row_counts=1 &end
8
OPAL 1.5.00.1 git rev. 2a9d889cc345b2130f9d7171dae4ba915805cf07
```
With the new OPAL module (OPAL/1.5.1-20170217), this is the string stored in the stat file
```
&data mode=ascii, no_row_counts=1 &end
8
IPPL 1.1.4 git rev.
```
ROGER returns an error and it does not read properly the stat file.adelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/40New OptPilot module: opt-pilot/0.1.3-201702172017-03-03T09:08:51+01:00Valeria RizzoglioNew OptPilot module: opt-pilot/0.1.3-20170217On Merlin
* **Module list**
```
Currently Loaded Modulefiles:
1) gcc/5.4.0 5) hdf5/1.8.18 9) OPAL/1.5.1-20170217
2) openmpi/1.10.4 6) H5hut/2.0.0rc3 10) parmetis/4.0.3
...On Merlin
* **Module list**
```
Currently Loaded Modulefiles:
1) gcc/5.4.0 5) hdf5/1.8.18 9) OPAL/1.5.1-20170217
2) openmpi/1.10.4 6) H5hut/2.0.0rc3 10) parmetis/4.0.3
3) cuda/8.0.44 7) gsl/2.2.1 11) root/6.08.02
4) dks/1.0.1 8) trilinos/12.10.1 12) opt-pilot/0.1.3-20170217
```
* **Command to run**
```
/opt/psi/Compiler/openmpi/1.10.4/gcc/5.4.0/bin/mpiexec \
--prefix /opt/psi/Compiler/openmpi/1.10.4/gcc/5.4.0 \
-x LD_LIBRARY_PATH -x OMP_NUM_THREADS -x OMPI_MCA_btl \
-np 10 -machinefile /tmp/2455742.1.prime_bd.q/machines \
/opt/psi/OPAL/opt-pilot/0.1.3-20170217/OPAL/1.5.1-20170217/openmpi/1.10.4/gcc/5.4.0/bin/pisa-opal.exe \
--inputfile=/gpfs/home/rizzoglio_v/CPT_Model/G2-LA2-LB-70/tmpl/PROSCAN-G2-LA2-LB-70.tmpl \
--outdir=PROSCAN-G2-LA2-LB-70-Results \
--outfile=1kG.dat --maxGenerations=1000 --initialPopulation=60 --sol-synch=0 --num-coworkers=1 \
--num-masters=1 --dump-dat=1
```
* **Cout**
`/opt/psi/OPAL/opt-pilot/0.1.3-20170217/OPAL/1.5.1-20170217/openmpi/1.10.4/gcc/5.4.0/bin/pisa-opal.exe: error while loading shared libraries: libOpenCL.so.1:`
Did I miss to load something?adelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/39New OPAL module (OPAL/1.5.1-20170217) and GPU2020-04-02T09:16:08+02:00Valeria RizzoglioNew OPAL module (OPAL/1.5.1-20170217) and GPUOn opalrunner:
* **Module list**
```
Currently Loaded Modulefiles:
1) gcc/5.4.0 3) hdf5/1.8.18 5) OPAL/1.5.1-20170217 7) dks/1.0.1
2) openmpi/1.10.4 4) H5hut/2.0.0rc3 6) cuda/8.0.44
```
...On opalrunner:
* **Module list**
```
Currently Loaded Modulefiles:
1) gcc/5.4.0 3) hdf5/1.8.18 5) OPAL/1.5.1-20170217 7) dks/1.0.1
2) openmpi/1.10.4 4) H5hut/2.0.0rc3 6) cuda/8.0.44
```
* **Run with GPU**
`mpirun -np 8 opal PROSCAN.in --use-dks`
* **Cout**
` Ippl> OPAL compiled without DKS, --use-dks flag has no effect`
Did I miss to load some modules? Did I do somethig wrong?OPAL 1.5.1gsellgsellhttps://gitlab.psi.ch/OPAL/src/-/issues/38Compiler error with AMR2020-04-02T09:16:08+02:00frey_mCompiler error with AMRAfter merging the OPAL master branch into my fork, OPAL does not compile anymore with AMR (i.e. -DENABLE_AMR_SOLVER=1).
The error message states
**/opt/psi/Compiler/boost/1.62.0/gcc/5.4.0/include/boost/mpl/vector/aux_/at.hpp:35:38: fata...After merging the OPAL master branch into my fork, OPAL does not compile anymore with AMR (i.e. -DENABLE_AMR_SOLVER=1).
The error message states
**/opt/psi/Compiler/boost/1.62.0/gcc/5.4.0/include/boost/mpl/vector/aux_/at.hpp:35:38: fatal error: template instantiation depth exceeds maximum of 64 (use -ftemplate-depth= to increase the maximum)
typedef __typeof__( Vector::item_(index_()) ) type;**
The following toolchain is used:
* source /opt/psi/config/profile.bash
* module use unstable
* module load cmake/3.6.3
* module load gcc/5.4.0
* module load boost/1.62.0
* module load gsl/2.2.1
* module load openmpi/1.10.4
* module load trilinos/12.10.1
* module load hdf5/1.8.18
* module load H5hut/2.0.0rc3
In order to compile with AMR, one has to install BoxLib first by subsequent steps:
1. git clone https://github.com/BoxLib-Codes/BoxLib
2. cd BoxLib
3. mkdir build
4. cd build
5. cmake -DBL_USE_PARTICLES=1 -DCMAKE_INSTALL_PREFIX=$TARGET_DIR ../
6. make
7. make install
8. export environment variables:
* $ export BOXLIB_HOME=$TARGET_DIR
* $ export BOXLIB_PREFIX=$BOXLIB_HOME
* $ export BOXLIB_INCLUDE_DIR=$BOXLIB_HOME/include
* $ export BOXLIB_LIBRARY_DIR=$BOXLIB_HOME/lib
* $ export BOXLIB_PERL_DIR=$BOXLIB_HOME/perl
The compilation of OPAL is then performed by configuring CMAKE with **-DENABLE_AMR_SOLVER=1**frey_mfrey_mhttps://gitlab.psi.ch/OPAL/src/-/issues/37Some particles get kicked more in corrector2019-08-01T16:14:24+02:00krausSome particles get kicked more in correctorFor short correctors some particles may get kicked one time more than the majority. E.g. in the regression test HKick-Test-2 when inspecting the phase space after the corrector one observes that some particles get twice the kick in trans...For short correctors some particles may get kicked one time more than the majority. E.g. in the regression test HKick-Test-2 when inspecting the phase space after the corrector one observes that some particles get twice the kick in transverse direction than the majority. The field is modeled as a hard edge magnet. The majority gets kicked only once while a few particles get kicked twice. This behavior isn't satisfactory.OPAL 1.9.xkrauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/36SurfacePhysics cout2017-03-07T09:56:32+01:00Valeria RizzoglioSurfacePhysics coutThis is the command to define a collimator with SurfacePhysics
`KMA3o: ECOLLIMATOR, XSIZE=0.0035, YSIZE=0.0035, L=0.002, SURFACEPHYSICS=CopperCol, ELEMEDGE=4.2105;`
and this is the corresponding OPAL cout
```
OPAL{0}> * *******...This is the command to define a collimator with SurfacePhysics
`KMA3o: ECOLLIMATOR, XSIZE=0.0035, YSIZE=0.0035, L=0.002, SURFACEPHYSICS=CopperCol, ELEMEDGE=4.2105;`
and this is the corresponding OPAL cout
```
OPAL{0}> * ************* S U R F A C E P H Y S I C S ****************************************
OPAL{0}> * SurfacePhysics::initSurfacePhysicsHandler
OPAL{0}> * **********************************************************************************
OPAL{0}> * ************* S U R F A C E P H Y S I C S ****************************************
OPAL{0}> * SURFACEPHYSICS KMA3O_sphys
OPAL{0}> * MATERIAL Copper
OPAL{0}> * RADIUS 0
OPAL{0}> * SIGMA 0
OPAL{0}> * TAU 0
OPAL{0}> * **********************************************************************************
OPAL{0}>
```
Would it be possible to print XSIZE, YSIZE, LENGTH or aperture? The printed cout does not change in case of Collimator or Degrader.
In addition, RADIUS, SIGMA and TAU are not properties of the collimator/degrader but of a wakefield function, that in this case was not used.
**Errata Corrige**
Attributes available for ECOLLIMATOR:
```
OPAL> string TYPE The element design type (the project name)
OPAL> real array APERTURE The element aperture
OPAL> real L The element length in m
OPAL> string WAKEF Defines the wake function
OPAL> string SURFACEPHYSICS Defines the surface physics handler
OPAL> real XSIZE Horizontal half-aperture in m
OPAL> real YSIZE Vertical half-aperture in m
OPAL> string OUTFN Monitor output filename
OPAL> real DX Misalignment in x direction
OPAL> real DY Misalignment in y direction
```
With **WAKEF**, it is possible to define RADIUS, SIGMA, TAU. So those are properties of the collimator. adelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/35Regression Tests for branch OPAL-1.62019-07-04T17:15:48+02:00krausRegression Tests for branch OPAL-1.6Currently we test branches master and OPAL-1.4. We should stop testing OPAL-1.4 but test OPAL-1.6 from now on. I don't think that any one is applying patches to OPAL-1.4 any more.
A branch OPAL-1.6 already exists in the repository of ...Currently we test branches master and OPAL-1.4. We should stop testing OPAL-1.4 but test OPAL-1.6 from now on. I don't think that any one is applying patches to OPAL-1.4 any more.
A branch OPAL-1.6 already exists in the repository of the regression test.OPAL 1.5.3gsellgsell