Wallacei - Wallacei X - Streamlining Objective Inputs

In this short video tutorial, we introduce an alternative method to inputting fitness objective values into the Wallacei.X component.
In Wallacei version 2.4 and later, it is now possible to input multiple fitness objective values using a single 'Number' parameter (in previous versions of Wallacei, each fitness objective value required its own 'Number' parameter). The video also introduces new features such as displaying the names of the fitness objectives under each of the analysis graphs within the Wallacei.X user interface window.
------------------
Click here to download the latest version of Wallacei:
www.food4rhino...
Click here to watch the Wallacei X tutorial series and for more short video tutorials:
www.youtube.co....
Click here to download the Wallacei Primer:
www.wallacei.c...
Click here to see some of the work created by Wallacei:
www.wallacei.c...
And for more information on everything Wallacei, please visit:
www.wallacei.com

[@marcomondello8790]

Wouldn´t "stremlineng data as Fitness Objective" mean that the algorythm will now try to MINIMIZE what before was treated as data? For example: if one of my data is Gross Floor Area but my fitness objective is to contain this GFA within a certain domain, connecting both the GFA measurement as well as the FO as a domain (as per your other video) would be interpreted by wallacei as two separate and conflicting optimizations (I want GFA to be between A nd B, not 0 -, wouldn´t it? Surely, not being able to see any data before exporting solutions is user unfriendly, mostly because the FO are formulas that servethe minimization strategy - but may not represent the actual values users are after.