Proper parsers of optPilot commands that is based on OpalParser

Sofar the parser for optPilot within OPAl is rather a hack than properly done.

marked this issue as related to #8 (closed)

marked this issue as related to #165 (closed)

added Optimiser label

Well I disagree with the statement in its absolute form.

I agree with the fact that the integration could have be done nicer. However given the fact of the current manpower situation I decided to eliminate opt-pilot as a project (repo, executable etc.) and integrate this in a minimal invasive way with the amount of manpower available.

This eases our build/release chain and at the same time enables more easily large(est) scale optimisation with OPAL. Important for PSI and at the moment ANL (AWA).

I don't blame you. It was done in haste such that it's done and it works. And I know about the situation with manpower. Still (for me) this is a hack.

marked this issue as related to #179 (closed)

I've made the branch OptPilotOpalParser (529108af) where this is implemented. Now the commands of Opt-Pilot are parsed with Opals parser. For an example expand test_optPilot.tgz, change directory to test_optPilot and then

mpirun -np 4 opal 05-DL_QN3.in --info 2

N.B.: For usage of Opal variables in string argument use ${variable_name}. This is e.g. useful in expressions for objectives and contraints.

assigned to @kraus and unassigned @adelmann

This is implemented with commits 4bef62e7...2a1bc2f2.

closed

Rudimentary documentation can be found here. @ineichen and @adelmann please fill the gaps e.g. the file formats for the peak and probe files.

mentioned in commit b326340c

assigned to @snuverink_j

@snuverink_j Jochem can you take care on the documentation of the peakfinder and proble files?

I have added some bits. I don't have an example of a probe file, but I have added a link to the probe section.

@snuverink_j you wrote:

//////////////// QUOTE BEGIN /////////////////////

obj1: OBJECTIVE, EXPR="-energy";
obj2: OBJECTIVE, EXPR="emit_x";

This defines two objectives named obj1 and obj2. The optimiser knows several mathematical functions and methods to access output files (see below). Without the use of these special methods design variables or the variables from the .stat output file at the end of the simulation can be used for optimisation. Note that objectives are always minimised, so in this case a solution where the final energy is maximal and the final horizontal emittance is minimal is looked for.

con1: CONSTRAINT, EXPR="x1+x2<1.0";
con2: CONSTRAINT, EXPR="numParticles>1000";

This defines two constraints. The syntax is similar to the OBJECTIVE syntax. The first constraint consists of only design variables and will be evaluated before the simulation. The second constraint will be evaluated after the simulation.

///////////////// QUOTE END //////////////////////

1. Do expressions like in obj1 work, where you just give the name of a .stat variable?
2. Do expressions like in con1 and their pre-evaluation work?

I haven't been using opt-Pilot for a while and it definitely didn't work then. By the way, the usage of opt-pilot in Opal has changed since Opal parses the opt-Pilot commands natively. See the example at the bottom of the wiki page.

1. I believe this was working. With the new implementation this should be rechecked. I can do this at some point.
2. Such an expression and pre-evaluation was working, that was fixed with opt-pilot#6 (closed) .. I will recheck this too.

In #218 (closed) the constraints behaviour was rechecked and extended.