Skip to Content.
Sympa Menu

opal - Re: [Opal] Error OPAL

opal AT

Subject: The OPAL Discussion Forum

List archive

Re: [Opal] Error OPAL

Chronological Thread 
  • From: "Adelmann Andreas (PSI)" <andreas.adelmann AT>
  • To: "Calvo Portela, Pedro" <Pedro.Calvo AT>
  • Cc: opal <Opal AT>
  • Subject: Re: [Opal] Error OPAL
  • Date: Thu, 9 Feb 2017 11:05:29 +0000
  • Accept-language: en-US, de-CH

How do you plot this?

Dr. sc. math. Andreas (Andy) Adelmann
Staff Scientist
Paul Scherrer Institut WBBA/219 CH-5232 Villigen PSI
Phone Office: xx41 56 310 42 33 Fax: xx41 56 310 31 91
Phone Home: xx41 62 891 91 44
Friday: ETH CAB F37 or HPK G 28   +41 44 632 75 22
The more exotic, the more abstract the knowledge, 
the more profound will be its consequences.
Leon Lederman 

On 9 Feb 2017, at 11:47, Calvo Portela, Pedro <Pedro.Calvo AT> wrote:

Dear Andreas

I've include the modification at the Field Solver, and now the error doesn't occur. But the tracking of the particles are absolutely unexpected. I attach two plots of the orbits with 1000 and 999 particles. You could see that the results are complete different.

Best regards

De: Adelmann Andreas (PSI) [andreas.adelmann AT]
Enviado el: miércoles, 08 de febrero de 2017 21:15
Para: Calvo Portela, Pedro
Asunto: Re: [Opal] Error OPAL

Hi Pedro, try to change:

FSTYPE=FFT, MX=32, MY=32, MT=64


FSTYPE=FFT, MX=16, MY=16, MT=32, ….

You only have 1000 particles and apps. 65k grid cells.
How many cores do you use?


On 31 Jan 2017, at 08:58, Calvo Portela, Pedro <Pedro.Calvo AT> wrote:

Dear Andreas.

I'm using the version 1.4.0 of OPAL. 
I share with you the input files in a dropbox folder.


De: Adelmann Andreas (PSI) [andreas.adelmann AT]
Enviado el: viernes, 27 de enero de 2017 23:35
Para: Calvo Portela, Pedro
Cc: opal AT
Asunto: Re: [Opal] Error OPAL

Hi Pedro 

can you make all the input files available so we can reproduce the problem.
Which version of OPAL are you using?
Cheers Andreas 

On 27 Jan 2017, at 11:03, Calvo Portela, Pedro <Pedro.Calvo AT> wrote:

Dear OPAL users, I write you because we have some problems about the simulation of a big number of particles.
We simulate without problems our machine with the correct electric and magnetic fields, including the geometry in the simulation. But when we increase the number of particles above 1000, we obtain the following error in the output:

Error> Interpolator::getFieldIter: attempt to access non-local index{[-2147483648:-2147483648:1],[-2147483648:-2147483648:1],[-2147483648:-2147483648:1]} on node 0
Error> Dumping local owned and allocated domains:
Error> 0: owned = {[0:31:1],[0:31:1],[0:31:1]}, allocated = {[-1:32:1],[-1:32:1],[-1:32:1]}
Error> Error occurred for BareField with layout = Domain = {[0:31:1],[0:31:1],[0:31:1]}
Error> FieldLayoutUsers = 3
Error> Total number of vnodes = 1
Error> Local Vnodes = 1
Error>  vnode 0: Node = 0 ; vnode_m = -1 ; Domain = {[0:31:1],[0:31:1],[0:31:1]}
Error> Remote Vnodes = 0
Error> Calling abort ...

This error don't occur when the number of particles is lower than 1000.
We have tried to solve this error changing the fieldsolver in the code for a 1000 particles, but the results are completly diferent if we compare with the simulation with a number of particles of 999.  I 

I will appreciate any suggestion to solve this problem.
Best Regards
Pedro Calvo

Este mensaje y sus ficheros adjuntos se dirige exclusivamente a su destinatario y puede contener información privilegiada o 
confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está 
prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique 
inmediatamente respondiendo al mensaje y proceda a su destrucción.
This message and its attached files is intended exclusively for its recipients and may contain confidential information. If you received 
this e-mail in error you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited and 
may be unlawful. In this case, please notify us by a reply and delete this email and its contents immediately.


Archive powered by MHonArc 2.6.19.

Top of Page