opt-pilot: objectives based on design variables
as mentioned in #8 (comment 3112) writing objectives like (where d1 and d2 are design variables):
seem not to work (not sure if it ever did). Since the optimiser still tries to look in the output file:
Exception while getting value from SDDS file: unkown column name!
Still such an objective could potentially be useful.
I might have a look at this eventually, or if there is a direct need for it. Right now putting a low weight on it.