goat

goat is an optimization solver add-on component. It perfectly complements galapagos, David Rutten's evolutionary solver based on a randomized core. goat pursues a mathematical rigorous approach and relies on gradient-free optimization algorithms, delivering fast and deterministic results. At every run, goat will yield the same optimal result.

goat is a drop-in replacement for galapagos. It is based on David Rutten's galapagos GUI and interfaces NLopt, a collection of mathematical optimization libraries.

Tutorials

For getting started with optimization in parametric modelling environments in general and with goat in special, check out our presentation slides on Geometry and Optimization with several comprehensive examples.

Once you are familiar with the basics of optimization, head over to our comprehensive documentation on goat's different configuration options.

goat testing

Hey,

thanks for a great plugin giving the chance to know a bit more about the actual algorithm.

But strangely, I cannot connect to the gene-list as a set of input variables - just sometimes (reason unknown so far) I can connect. maybe when a galapagos component also is present on the canvas? whatsoever, it seems not to be supported cause goat crashes when starting with a gene list - can this be implemented maybe, if it was overseen or something? or is it for a reason?

the other thing is, i am currently running a global deterministic optimization with goat and karamba and see drops in the cpu-usage every ~second. the definition takes about 400ms to complete (i know this is still too long, but it's a temporary error in karamba i hope) - does it take that long to calculate the next step for the algorithm? also, i have 27 input variables for goat - is this too much?

thanks for the support,

best

robert

  • up

    phillip

    Noticed the gene-list problem as well. Though it shows the little Helix, it wont connect.

    • up

      Simon Flöry

      Hi,

      thanks for your feedback. 'Gene Lists' support is not yet implemented, I'll do this once i tracked down the reason for goat not working on 64-bit systems.


      Regarding CPU usage, 27 variables should not be too much for goat. However, goat requires a certain number of GH definition evaluations for the optimization. In total, the number will be less than for Galapagos, but still some. It would be nice to have a look at your GH model so that I can further benchmark things.

      thanks, simon

      3