The OPAL Discussion Forum

[Christof Metzger-Kraus <christof.j.kraus AT gmail.com>]

Hi Simon,

it's correct that VALUE, OPTION->AUTOPHASE doesn't yield the correct value, but Opal-t still gets the correct value. With OPTION, AUTOPHASE=3 you create a new instance of the class Option which updates a global variable. If you would use

myOpt: OPTION, AUTOPHASE=3;

VALUE, myOpt->AUTOPHASE;

then you get the correct value also in the output. I've improved the source code such that the global instance of the class Option named OPTION is updated each time one sets an option.

Best regards,

Christof

On Thu, Jan 28, 2021 at 4:47 PM Simon Friederich <sifriede AT uni-mainz.de> wrote:

Dear OPAL-Team,

For my purpose I need to make sure, that Autophase is not turned off.
According to the manual (http://amas.web.psi.ch/opal/Documentation/master/OPAL_Manual.html#sec.control.option),
this is the case, if AUTOPHASE = -1.

I realized, that this value is not set and does not differ from the default value 6 though.
test.in

OPTION, AUTOPHASE = -1;
VALUE, OPTION->AUTOPHASE;

OPAL> value: OPTION->AUTOPHASE = {6}

(Same result for different values of AUTOPHASE).

Am I missing something?

Best regards,
Simon

-- 
Dr. Simon Friederich
Helmholtz-Institut Mainz | Insitut für Kernphysik
Kollaboration ACID       | B
Johannes Gutenberg-Universität Mainz
Staudingerweg 18         | Johann-Joachim-Becherweg 45
55128 Mainz, Deutschland

Tel.: +49 (0)6131 39-23160
E-Mail: s.friederich AT uni-mainz.de