Grasshopper 0.7.0055 available for download

Dear testers,

a minor update to Grasshopper is available for download.

● Galapagos can now start a solution from the initial slider layout.

● Galapagos can now start a solution from a selected genome.

● Added a Mutate override button to the Galapagos solver process.

● Added Save, Load and Defaults to the Galapagos settings UI.

● Added Curve Extremes component.

● Added [Set All Sliders] item to Galapagos Gene input menu.

● Added [Set Selected Sliders] item to Galapagos Gene input menu.

● Added auto-mutators which are triggered by low bio-diversity.

● Added feedback enable/disable button to the Galapagos window to speed up the process.

● Added direct colour casts to the Shader type.

● Added a Surface Split component.

○ Fixed missing undo event for grouping.

○ Fixed missing undo event with the slider popup editor.

○ Fixed String to Interval conversion not dealing with all formats.

○ Fixed chain inversion bug with Catenary component.

○ Changed Galapagos controls background and foreground colour defaults.

Enjoy,

David

David Rutten

david@mcneel.com

Poprad, Slovakia

Replies to This Discussion

Permalink Reply by Claudio on September 17, 2010 at 10:29am

Hi David,

First thank you very much for this wonderful tool. I really enjoy it and at my office we are very exited sand trying to integrate GH/Galapagos in our design process. A simple questions: What will be a practical use of the mutation button. Will it activate a mutation during a given generation while solver is running?...am I completely lost here?

thanks

Permalink Reply by David Rutten on September 17, 2010 at 1:52pm

Hi Claudio,

hopefully the button won't be needed for long. At the moment it is a way to add random noise (mutations) to the genomes in the next generation. The more often you press it, the more noise will be added.

It is a way to nudge a process out of a tight spot. However, I've already added extra algorithms that automatically add some mutations willy-nilly whenever the bio-diversity of the population drops too low.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by Mårten Nettelbladt on September 17, 2010 at 1:18pm

● Added [Set All Sliders] item to Galapagos Gene input menu.
● Added [Set Selected Sliders] item to Galapagos Gene input menu.

Wonderful!
Excited about all the attention Galapagos is getting (from David) at the moment...

Permalink Reply by to] on September 17, 2010 at 4:47pm

Hi David

thanks for the surface split ;)
i think we have found a bug in the meshsplitplane component in the new version
in the last one it worked fine
if the mesh and the plane are perpendicular to each other than we get a wrong result
if we rotate the plane just 1 degree everything is fine
- to]

Permalink Reply by David Rutten on September 18, 2010 at 4:14am

Yup, intersector bug. I'll forward it to the guys in Seattle.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by Philipp on September 18, 2010 at 4:44am

Thank you very much, David!
is there any good real-world examples of galapagos implementation?

Permalink Reply by taz on September 18, 2010 at 7:01pm

I may be crazy, but geometry preview isn't working for me with Rhino 5, 64 bit (as of GH 0.7.0055).

Any geometry is still there and will bake, but no GH geometry is displayed.

Anyone else finding this? I haven't had any troubles previously and everything works fine with Rhino 4 SR8...

Permalink Reply by David Rutten on September 19, 2010 at 3:39am

Are there messages in the command history? Steve added a new method to the SDK that allowed me to *not* draw preview geometry in layout pages. If you are running Grasshopper 0.7.0055 on a Rhino SDK which does not yet have this method, there will be an error in the display. This problem will be fixed with the next Rhino5 update.

Sorry about this.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by taz on September 19, 2010 at 5:49pm

I'll check the command line and report back on Monday...

Permalink Reply by taz on September 20, 2010 at 2:44pm

Is it Monday yet?

I guess I was a build behind. I updated to the 15-Sep-2010 WIP build and now everything works fine.

Sorry for the alarm.

Permalink Reply by taz on September 18, 2010 at 7:12pm

Here's a buggie...

I'm not sure what point X-tremes is finding, but it doesn't appear to be the highest or lowest and it's outputting the same point for both.

Permalink Reply by David Rutten on September 19, 2010 at 3:36am

Hi taz,

could be, I wrote the component in a bit of a hurry and it's possible my algorithm doesn't work under certain circumstances. However, based on the screenshot, it would appear you are looking straight down onto the plane that is used for the extremes direction. The extremes are defined relative to this plane (WorldXY by default).

--
David Rutten
david@mcneel.com
Poprad, Slovakia