The OPAL Discussion Forum

[Nicole Neveu <nneveu AT hawk.iit.edu>]

Update (for anyone who might have been watching this thread):

The issue was due to mismatch in types when looking at "numParticles".

Christof has fixed this in 2.0 master, and Jochem has added new error messages for bad objectives / constraints.

Thanks for the help!

Nicole

On Mon, Sep 24, 2018 at 4:24 AM Jochem Snuverink <jochem.snuverink AT psi.ch> wrote:

Hallo Nicole,

As far as I know there were no updates on the optimiser since last August.

The syntax looks alright to me, do you get this every time? Could it happen that the whole beam is lost before s=19.4? If you send me your input file, I can have a look (probably tomorrow though).

I will update the output so that one sees which constraint or objective is failing.

thanks, Jochem

On 24/09/18 06:22, Nicole Neveu wrote:

Hi Christof,

I use 2.0 master, and last build was on 8/28/2018.

We re-built to use the new mask feature.

Should I try doing a fresh build?

Thanks,

Nicole

On Sun, Sep 23, 2018 at 10:58 PM Christof Metzger-Kraus <christof.j.kraus AT gmail.com> wrote:

Hi Nicole, 

which version of Opal do you use, v 2.0 or compiled master (and if when did you update?

Christof 

Nicole Neveu <nneveu AT hawk.iit.edu> schrieb am Mo., 24. Sep. 2018, 04:43:

Hi All,

I'm getting the following error when running the GA:

Evaluation of objectives or constraints threw an exception!

Is there any way for me to find out which obj or const. is giving the exception?

I'm running with --info 5, and I suspect the following constraint:

c4: CONSTRAINT, EXPR="fabs(statVariableAt('numParticles', 19.4))>95000";

Or maybe my syntax is wrong?

Thanks,

Nicole