The OPAL Discussion Forum

[christof kraus <christof.j.kraus AT gmail.com>]

Hi Nicole,

you're right, I claimed that the scaling of the field maps changes for v1.4, but it doesn't. Following our conversation on 11/18/15 I sent an email to Steve Russel to explain the situation for v1.4, see below. Unfortunately I didn't send this email to you.

christof

---------- Forwarded message ----------
From: christof kraus <christof.j.kraus AT gmail.com>
Date: Fri, Nov 20, 2015 at 9:39 AM
Subject: Re: [Opal] V1.2 and V1.4
To: Russell, Steve, Andreas Adelmann

Hi Steve,

you're right or, better, I was wrong: in version 1.4 it's more complicated

FM2DDynamic: max Ez field value

FM2DElectroStatic: max Ez field value on axis

FM2DMagnetoStatic: max Bz field value

FM3DDynamic: max Ez field value on axis

FM3DH5Block: not normalized

FM3DH5Block_noscale: not normalized

This situation raises the question whether we should change them such that either all field maps normalize with the max field value or with the max field value on axis.

For versions post 1.4 I have changed the normalization of all field map types to use the max field value on axis.

christof

On Fri, Nov 20, 2015 at 12:49 AM, Russell, Steve wrote:

Hi Christof,

I think you're partially right. I wasn't looking closely enough, but
from what I see the FM2DMagnetoStatic_cspline class does indeed use the
field on axis. I missed that change. However, the FM2DMagnetoStatic
class still uses the max Bz field value.

Steve

On Thu, 2015-11-19 at 11:45 +0100, christof kraus wrote:
> I have to contradict: Scaling of the field maps is somethings that
> will change in version 1.4. All field maps will normalize the field on
> axis. Before I changed that behavior I tried to convert a 2D field map
> into a 1D field map. It took me quite some time to figure out why Opal
> produced different results.
>
>
> christof
>
>