algorithmic modeling for Rhino
if you could explain yourself a bit more i could eventually give an answer
Convergence Graphs are built simply like the following:
- One graph per goal dimension Di
- Take the last X generations (depending on the 'history' slider in the top left of the viewport)
- Get the upper and lower bound of Di for each generations elite (light grey) and pareto front (dark grey)
- Take all the bounds of Di out of X and scale them to [0;1]
- Draw the bounds over the generations
.. this is the only 'function' they have got.
Regarding their change over generations, you might want to check on the formulation of your fitness functions. It's impossible to tell you what goes wrong without having a look at your setup.
David Rutten has elaborated fitness functions quite a bit on his blog, and recently also in a paper:
http://ieatbugsforbreakfast.wordpress.com/2014/08/22/icgg2014-paper/
http://ieatbugsforbreakfast.wordpress.com/2011/03/
http://ieatbugsforbreakfast.wordpress.com/2011/03/04/fitness-functi...
if you open up galapagos, you find the links.
Best
Robert
.. So a Convergence Graph which is just dark grey means that the algorithm found as many pareto-non-dominant solutions (forming the pareto front) such that all the elite consists of them.
from a certain point on, the pareto-front has to be truncated to fit the elite size - which is done either by the hypervolume contribution or after the SPEA2 archiving strategy.
And I find the result graph is also strange:
1. Most values of one objective (uniformity performance) are centralizing around one value (0). I think this is related to the objective features. Because my variable is discrete, the values of objectives may distribute unevenly. In other words, many individules may share a very closed value of one objective. Does this condition influence the optimization results?
2. And from the two-dimensional plane by other two objectives (total energy consumption and UDI100-2000), all the solution seem to be around a monotonous curve? What reasons lead to this condition?
3. If the generation is adequate, is it possible to solve those problems?
Thank you for your help.
the yellow solutions are the history of the run. only the red ones represent the current state of the search - where you can set different opacities for the pareto-front and the rest of the elite in the top left corner of the viewport.
1) yes this probably has an effect, since the algorithm potentially cannot make as good decisions on where to go when an objective remains the same for a set of different parameters. but it does not necessarily mean that it suffers badly.
2) the monotonous curve is the history. your solutions are quite sparsely distributed in the objective space which can mean an overconstrained problem (discontinuous pareto front) or that your search parameters have to be adjusted - respectively it found some niches to converge to.
3) what do you mean with adequate and solve..?! nobody knows your generation, problem, or how to solve it.
aparently the elite / pareto front had a reason to grow in its extents again.
option
1) the algorithm is still in the elite filling phase. means all the pareto-non-dominant solutions are contained in the elite. either the remaining space in the elite is filled with the best non-front-solutions according to SPEA2-fitness, or according to their hypervolume contribution (the hightest ones are added)
2) the algorithm is in the pareto-front-truncation phase if there are more non-dominant solutions than the elite can take. so either the front is truncated by the SPEA2-strategy based on euclidean multi-dimensional distances or, again, the least hypervolume contribution.
it can always happen that the algotihm discovers new solutions which make those filling / truncation schemes select a different set.
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by