Skip to Content.
Sympa Menu

opal - Re: [Opal] usage of 1DDynamic field map

opal AT

Subject: The OPAL Discussion Forum

List archive

Re: [Opal] usage of 1DDynamic field map

Chronological Thread  
  • From: Philippe Piot <philippe.piot AT>
  • To: "Adelmann Andreas (PSI)" <andreas.adelmann AT>
  • Cc: "opal AT" <opal AT>
  • Subject: Re: [Opal] usage of 1DDynamic field map
  • Date: Thu, 20 Jan 2022 06:53:38 -0600
  • Authentication-results: mc1; iprev=pass ( smtp.remote-ip=; spf=pass; dkim=pass header.s=20210112 header.a=rsa-sha256; dmarc=pass

  Andreas was able to run my file and got the correct results without changing anything. I checked on my computer, recompiled everything (as I had upgraded to Linux from fc33 to fc35) but the problem subsisted. 
  However, I found that it disappear depending on how I invoke the OPAL command. 
  For instance I usually run as
     mpirun --mca btl ^uct /home/piot/Simulations/OPAL/opal/build_2021.1/src/opal  (and get the strange modulate pattern I reported in this thread). 
  If I just run as 
      /home/piot/Simulations/OPAL/opal/build_2021.1/src/opal  I get the results I expect. 

  So still a little puzzle! Thank you,  -- Philippe. 

PS: for completeness, I use gcc (GCC) 11.2.1 20211203, and below is an output of ldd on the compiled exec 

[piot@localhost opal]$ ldd /home/piot/Simulations/OPAL/opal/build_2021.1/src/opal (0x00007ffc4f1cf000) => /lib64/ (0x00007fb22c4b7000) => /lib64/ (0x00007fb22c475000) => /home/piot/Simulations/OPAL/h5hut/build/build/lib/ (0x00007fb22c3d9000) => /lib64/ (0x00007fb22c3bf000) => /lib64/ (0x00007fb22c2e3000) => /usr/lib64/openmpi/lib/ (0x00007fb22c2c7000) => /usr/lib64/openmpi/lib/ (0x00007fb22c199000) => /lib64/ (0x00007fb22bf7a000) => /lib64/ (0x00007fb22bf5f000) => /lib64/ (0x00007fb22bd55000) => /lib64/ (0x00007fb22bd4b000) => /usr/lib64/openmpi/lib/ (0x00007fb22b983000)
/lib64/ (0x00007fb22c79c000) => /usr/lib64/openmpi/lib/ (0x00007fb22b8c9000) => /usr/lib64/openmpi/lib/ (0x00007fb22b8c4000) => /usr/lib64/openmpi/lib/ (0x00007fb22b817000) => /lib64/ (0x00007fb22b7ba000) => /lib64/ (0x00007fb22b781000) => /lib64/ (0x00007fb22b77a000)

On Wed, Jan 19, 2022 at 12:02 AM Adelmann Andreas (PSI) <andreas.adelmann AT> wrote:
Hi Philippe the easiest way to look at this by having the complete
input file available. Would that be possible? 

Cheers A
Dr. sc. math. Andreas (Andy) Adelmann
Head a.i. Labor for Scientific Computing and Modelling 
Paul Scherrer Institut OHSA/ CH-5232 Villigen PSI
Phone Office: xx41 56 310 42 33 Fax: xx41 56 310 31 91
Zoom ID: 470-582-4086 Password: AdA
Zoom Link:

Friday: ETH HPK G 28   +41 44 633 3076
The more exotic, the more abstract the knowledge, 
the more profound will be its consequences.
Leon Lederman 

On 18 Jan 2022, at 12:56, Philippe Piot <philippe.piot AT> wrote:

Also, I forgot to mention that setting FAST= TRUE does not affect the results. Best,  -- Philippe.

On Tue, Jan 18, 2022 at 5:42 AM Philippe Piot <philippe.piot AT> wrote:
Dear All,
   I am using the 1DDynamic representation of an electromagnetic field for a gunf with the following block
1DDynamic 20 True
0 11.5 2999
0.0 2.0 199
... 2998 lines ...
when I track particles arranged on an initial grid I observe a modulation of transverse momentum as function position (see plot on the right below) while the use of a 3D map directly produced in omega3P give the expected dependency (left below). Could somebody comments if anything in my block above if wrong?
The call inside OPAL is as follows:
GUN: RFCavity, L = gun_len,
     VOLT = 40.0,
     ORIGIN = {0,0,0},
     FMAPFN = "Ezvsz.dat",
     FREQ = gun_freq,
     LAG = (gun_inj_phase*Pi)/180.0;

Thank you very much. All the best,  -- Philippe.

px**2+py**2 (colormap) as function of x (horizontal) and y (vertical) axis obtained by tracking in a 3D map of the EM field (left) and with the 1DDynamic field map (right).

Archive powered by MHonArc 2.6.19.

Top of Page