src issueshttps://gitlab.psi.ch/OPAL/src/-/issues2018-09-22T17:14:37+02:00https://gitlab.psi.ch/OPAL/src/-/issues/237Pixmap image as input for collimator2018-09-22T17:14:37+02:00krausPixmap image as input for collimatorLet the users specify a black and white image that describes the hole of the collimator. An example of a black and white image is attached.
As input file format Portable Bitmap is suggested since a parser is relatively simple to implem...Let the users specify a black and white image that describes the hole of the collimator. An example of a black and white image is attached.
As input file format Portable Bitmap is suggested since a parser is relatively simple to implement and we'll avoid to rely on yet another library.
The simplest way to implement this is to extend the FlexibleCollimator and use one rectangle for each black pixel. However this isn't ideal because the number of rectangles can be big. Since we use a quadtree the performance may not be so bad. We'll have to test it.
Substantially more effort is needed if we try to minimize the number of rectangles by clustering pixels.
Submitted by @ext-roussel_r
![test_mask](/uploads/d4371d755495d590a39af25c65b93a0f/test_mask.png)krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/236Arbitrary reference point for hypervolume calculation2018-08-02T17:06:51+02:00snuverink_jjochem.snuverink@psi.chArbitrary reference point for hypervolume calculationAs discussed in #235: "the ability to set an arbitrary point would also be nice, but has no priority"As discussed in #235: "the ability to set an arbitrary point would also be nice, but has no priority"snuverink_jjochem.snuverink@psi.chsnuverink_jjochem.snuverink@psi.chhttps://gitlab.psi.ch/OPAL/src/-/issues/232Add argument DISTRIBUTIONDIR to Optimizer and Sample Command2018-07-30T08:36:17+02:00snuverink_jjochem.snuverink@psi.chAdd argument DISTRIBUTIONDIR to Optimizer and Sample CommandFrom @ext-bershanska_a: "It would be nice to add OPTIMIZER attribute for distribution directory (like for runOPAL.py)"From @ext-bershanska_a: "It would be nice to add OPTIMIZER attribute for distribution directory (like for runOPAL.py)"frey_mfrey_mhttps://gitlab.psi.ch/OPAL/src/-/issues/231Add z coordinate to stat file2018-07-11T16:57:17+02:00snuverink_jjochem.snuverink@psi.chAdd z coordinate to stat fileProposal from @winklehner_d and @ext-bershanska_a:
Add the z coordinate of the reference particle to the stat file (seems like only s is given, which probably stems from the mismatch between OPAL-T and OPAL-cycl coordinate systems).Proposal from @winklehner_d and @ext-bershanska_a:
Add the z coordinate of the reference particle to the stat file (seems like only s is given, which probably stems from the mismatch between OPAL-T and OPAL-cycl coordinate systems).snuverink_jjochem.snuverink@psi.chsnuverink_jjochem.snuverink@psi.chhttps://gitlab.psi.ch/OPAL/src/-/issues/228Restart optimizer from generation file2019-02-23T10:03:25+01:00frey_mRestart optimizer from generation file@snuverink_j and I discussed that it would be a nice feature of restarting the optimizer from a generation file. If the user put the generation number too low, this feature would help to continue computation instead of starting from scra...@snuverink_j and I discussed that it would be a nice feature of restarting the optimizer from a generation file. If the user put the generation number too low, this feature would help to continue computation instead of starting from scratch.frey_mfrey_mhttps://gitlab.psi.ch/OPAL/src/-/issues/225SCAN option adapted from OPTIMIZE command2018-06-22T11:11:14+02:00snuverink_jjochem.snuverink@psi.chSCAN option adapted from OPTIMIZE commandFrom a discussion in runOPAL#7 with @rizzoglio_v suggested by @adelmann. The optimiser mechanism of running with a master core that spawns several opal jobs can be adapted to run a scan through a parameter list. Compared to the scan opti...From a discussion in runOPAL#7 with @rizzoglio_v suggested by @adelmann. The optimiser mechanism of running with a master core that spawns several opal jobs can be adapted to run a scan through a parameter list. Compared to the scan option of runOPAL, an advantage is a single job in a batch system, and possibly better grouping of results.
E.g.
```
dv0: DVAR, VARIABLE="P0", LOWERBOUND=-10.0, UPPERBOUND=0.0, STEP = 0.5;
dv1: DVAR, VARIABLE="P1", LOWERBOUND=-10.0, UPPERBOUND=0.0, STEP = 1.0;
SCAN, INPUT="tmpl/model.tmpl",
OUTPUT="model",
OUTDIR="results",
DVARS = {dv0, dv1},
NUM_MASTERS=1,
NUM_COWORKERS=8,
SIMTMPDIR="tmp",
TEMPLATEDIR="tmpl",
FIELDMAPDIR="fieldmaps";
```
cc: @frey_mfrey_mfrey_mhttps://gitlab.psi.ch/OPAL/src/-/issues/209Compiling OPAL using OPAL package2020-04-22T11:42:20+02:00krausCompiling OPAL using OPAL packageIn the past it was possible to build OPAL using the OPAL package downloaded from the wiki (then it was still on trac not gitlab). Furthermore there was a description on the wiki how this can be done.
Currently I face the problem that I'...In the past it was possible to build OPAL using the OPAL package downloaded from the wiki (then it was still on trac not gitlab). Furthermore there was a description on the wiki how this can be done.
Currently I face the problem that I'd like to build OPAL on the servers of Helmholtz-Zentrum Berlin. They use a version of a Linux distro that is outdated (several years old). Modules that provide newer versions such as at PSI are, as far as I know, not supported. That means I would have to build a lot of tools (gcc, cmake, openmpi and possibly many more) before I could build OPAL.
With the current package, OPAL-1.6.1-3, building OPAL isn't supported. Among others cmake and mpicxx/mpicc are missing.
I would propose to reenable this feature since it lowers the barrier to build and develop OPAL. This applies especially to those that aren't yet used to build software from source.gselladelmanngsellhttps://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/176no error when missing data file for optimisation2017-11-07T09:28:54+01:00ext-neveu_nno error when missing data file for optimisationWhen trying to run an optimisation problem, if the data file is missing from the directory (i.e. optLinac.data) OPAL quits running, but does not return an error. Please add an error when the data file is missing from the directory.When trying to run an optimisation problem, if the data file is missing from the directory (i.e. optLinac.data) OPAL quits running, but does not return an error. Please add an error when the data file is missing from the directory.krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/170SurfacePhysics in OPAL-Cyc2020-04-22T11:41:42+02:00Valeria RizzoglioSurfacePhysics in OPAL-CycI ran a small test using OPAL-Cyc - RINGDEFINITION with a CCOLLIMATOR. I applied the SURFACEPHYSICS on the CCOLLIMATOR but the Monte Carlo was not performed. The beam colliding with the CCOLLIMATOR was simply lost and not scattered. This...I ran a small test using OPAL-Cyc - RINGDEFINITION with a CCOLLIMATOR. I applied the SURFACEPHYSICS on the CCOLLIMATOR but the Monte Carlo was not performed. The beam colliding with the CCOLLIMATOR was simply lost and not scattered. This is related to the
Issue #149
```
Coll: SURFACEPHYSICS, TYPE="DEGRADER", ENABLERUTHERFORD=TRUE, MATERIAL="GraphiteR6710";
Quad1_BP: CCollimator, XSTART=-1000, XEND=-1000, YSTART=1800, YEND=1810, ZSTART=70, ZEND=170, WIDTH=200.0, SURFACEPHYSICS=Coll;
```
I tried to change TYPE with "COLLIMATOR" and "CCOLLIMATOR", but the results did not change.
Attached the input file and the output.
[MonteCarlo_Cyc.in](/uploads/013bde1e7b0452d5fbbe266d0a7026ed/MonteCarlo_Cyc.in)[TYPE_COLLIMATOR.out](/uploads/a33c60beb640faccc6353c882565d3a8/TYPE_COLLIMATOR.out)
I ran on Merlin with the following settings:
```
1) gcc/5.4.0 3) OPAL/1.6.0 5) root/6.08.02 7) Tcl/8.6.4 9) Python/2.7.12 11) gsl/2.2.1 13) psi-python27/2.2.0
2) openmpi/1.10.4 4) OPAL/1.6 6) openssl/1.0.2j 8) Tk/8.6.4 10) boost/1.62.0
```OPAL 2.0.0adelmannadelmannhttps://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/150Add a user definable transverse limit to degrader class2017-08-12T18:17:25+02:00krausAdd a user definable transverse limit to degrader classOPAL 1.6.0krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/100Kickers with field maps2021-06-10T18:07:13+02:00krausKickers with field mapsKickers at bERLinPro are far from perfect dipoles. Instead they have a strong higher order components. The current implementation only provides a hard-edge model. Let the user add field maps to better model them.Kickers at bERLinPro are far from perfect dipoles. Instead they have a strong higher order components. The current implementation only provides a hard-edge model. Let the user add field maps to better model them.krauskraushttps://gitlab.psi.ch/OPAL/src/-/issues/71track-orbit of ID1 and ID2 OPAL-1.6 and master2021-06-10T18:49:09+02:00adelmanntrack-orbit of ID1 and ID2 OPAL-1.6 and masterIn data/track-orbit, the coordinates of ID1 and ID2 are **always** stored.
On the distribution command the user can set ID1 and ID2 by *hand*.
@rizzoglio_v : Please commentIn data/track-orbit, the coordinates of ID1 and ID2 are **always** stored.
On the distribution command the user can set ID1 and ID2 by *hand*.
@rizzoglio_v : Please commentadelmannadelmannhttps://gitlab.psi.ch/OPAL/src/-/issues/67Specification of distributions a la Elegant2020-04-22T11:38:48+02:00krausSpecification of distributions a la ElegantTo generate a distribution that corresponds to Elegant using betax, alphax, betay, alphay, nemittx, nemitty, sigma_s/sigma_t, p, sigma_dp.
J. KnedelTo generate a distribution that corresponds to Elegant using betax, alphax, betay, alphay, nemittx, nemitty, sigma_s/sigma_t, p, sigma_dp.
J. KnedelOPAL 1.9.xhttps://gitlab.psi.ch/OPAL/src/-/issues/352Collection of simple and commented input files2021-06-10T18:10:11+02:00krausCollection of simple and commented input files1. Start with external distribution, FROMFILE, (self generated, elegant, astra,...)
2. simple optimization of beamline with multi-part goal, e.g. to minimize 6D phase space
3. OPAL with CSR
4. OPAL with 3D Fields (RBend)
5. OPAL with arb...1. Start with external distribution, FROMFILE, (self generated, elegant, astra,...)
2. simple optimization of beamline with multi-part goal, e.g. to minimize 6D phase space
3. OPAL with CSR
4. OPAL with 3D Fields (RBend)
5. OPAL with arbitrary short range wakes
J. Knedelhttps://gitlab.psi.ch/OPAL/src/-/issues/65Quadrupole components of dipoles is missing2021-06-10T18:10:26+02:00krausQuadrupole components of dipoles is missingK1 has been removed from RBEND/SBEND, reimplement it.K1 has been removed from RBEND/SBEND, reimplement it.OPAL 1.9.xhttps://gitlab.psi.ch/OPAL/src/-/issues/66Reimplement boundary geometries, surface emission, multipacting etc in Parall...2021-06-10T18:10:55+02:00krausReimplement boundary geometries, surface emission, multipacting etc in ParallelTTrackerBoundary geometries, surface emission etc isn't ported from version 1.6 and in the near futur this won't be ported.Boundary geometries, surface emission etc isn't ported from version 1.6 and in the near futur this won't be ported.OPAL 1.9.xChuan WangChuan Wanghttps://gitlab.psi.ch/OPAL/src/-/issues/56Multi-Slit & PEPPERPOT2018-04-14T13:30:27+02:00adelmannMulti-Slit & PEPPERPOTPEPPERPOT with rectangular slits instead of circles.PEPPERPOT with rectangular slits instead of circles.OPAL 1.9.xadelmannkrausext-edelen_aadelmannhttps://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.x