Code indexing in gitaly is broken and leads to code not being visible to the user. We work on the issue with highest priority.

Skip to content
Snippets Groups Projects
Commit 39d5019d authored by ext-calvo_p's avatar ext-calvo_p
Browse files

improving doc for ascii2h5block

parent e5eb88fa
No related branches found
No related tags found
No related merge requests found
...@@ -1531,8 +1531,9 @@ ring: CYCLOTRON, TYPE=RING, CYHARMON=6, PHIINIT=0.0, ...@@ -1531,8 +1531,9 @@ ring: CYCLOTRON, TYPE=RING, CYHARMON=6, PHIINIT=0.0,
---- ----
If `TYPE` is set to `BANDRF`, the 3D electric field map of RF cavity will be If `TYPE` is set to `BANDRF`, the 3D electric field map of RF cavity will be
read from external {link_H5hut_wiki}[H5Hut] file and the following extra read from external {link_H5hut_wiki}[H5Hut] file
arguments need to specified: (see link:sec.opalcycl.read-3d-rf-field-map[Read 3D RF field-map]).
The following extra arguments need to specified:
RFMAPFN:: RFMAPFN::
The file name(s) for the electric field map(s) in H5Hut binary format. The file name(s) for the electric field map(s) in H5Hut binary format.
......
...@@ -492,20 +492,34 @@ respectively. ...@@ -492,20 +492,34 @@ respectively.
[[sec.opalcycl.read-3d-rf-field-map]] [[sec.opalcycl.read-3d-rf-field-map]]
==== Read 3D RF field-map ==== Read 3D RF field-map
The 3D RF field-map can be read from {link_H5hut_wiki}[H5Hut] type file for The 3D RF field-map can be read from {link_H5hut_wiki}[H5Hut] type
`TYPE=BANDRF`. To generate the _h5part_ field files, it is necessary to use the file for `TYPE=BANDRF`. To generate the _h5part_ field files, it is
_ascii2h5block_ conversion tool. This program builds h5part field files from necessary to use the _ascii2h5block_ conversion tool. This tool is
ASCII file output of ANSYS or OPERA 3D field data. The command to use it should be like: available after compiling _OPAL_ with `ENABLE_BANDRF=ON`. This program
builds h5part field files from ASCII file output of ANSYS or OPERA 3D
field data. The command to use it should be like:
---- ----
ascii2h5block efield.txt hfield.txt ehfout ascii2h5block efield.txt hfield.txt ehfout
---- ----
The ASCII input files must be adapted for an adequate conversion. The first The ASCII input files must be adapted for an adequate conversion. The
three rows of a field map that you wish to combine should include integers first row of each input field map that you wish to combine should specify
with the amount of steps (or different values) in latexmath:[x], latexmath:[y] the grid size in each direction, that is integers with the amount of
and latexmath:[z]. The 2D mid-plane map is in cylindrical coordinates, while steps (or different values) in latexmath:[x], latexmath:[y] and latexmath:[z].
the 3D map must be in Cartesian coordinates. The first three columns contains the spatial coordinates specified in meters,
and the last three columns store the field data. Positions and field are
supplied on points in a Cartesian coordinates grid:[(x, y, z)]. Example
showing the requiered format for ASCII file:
----
101 101 11
-0.110000 -0.018000 -0.006000 37.341814 226.620820 -319049.189111
-0.109200 -0.018000 -0.006000 56.839707 209.995240 303511.031113
-0.108400 -0.018000 -0.006000 -28.180696 37.248050 -292542.457735
-0.107600 -0.018000 -0.00600 8.412707 89.317296 -283046.136227
...
----
[[sec.opalcycl.particle-tracking-and-acceleration]] [[sec.opalcycl.particle-tracking-and-acceleration]]
=== Particle Tracking and Acceleration === Particle Tracking and Acceleration
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment