Grasshopper

algorithmic modeling for Rhino

Hi,

I finished the greatest part of the bridge optimization project with Grasshopper and Geometry Gym. From the results I can obtain the node displacement and the maximum node displacement.

I also managed to obtain the axial forces and perform a unity check for compression (and buckling) and tension for the beams. I set the solver settings for 'new model' to true, close model 'true' and solver on to 'true'.

By first starting up GSA and then Grasshopper, the data for the node displacement and the axial forces is retrieved and works correctly. But when I change the variables (for example the span length) the 'results' component of the axial forces turns red and gives an error, while the node displacement component is still working and adjusts the result to the new span length.

When I manually set the 'close model' function in the results component to 'false' the axial force results are adjusted to the new model. This also happens when I set the solver manually from true to false and then back to true. But for the optimization process, this can't be manually done. I thought the settings 'new model -- true' would take care of this, but this doesn't work for me.

Does anyone know how to solve this error?

The first picture shows the results of the axial forces (before adjusting the variables). The second picture shows the error when I made a change in one of the number sliders of the variables (for example span length). The third picture shows that I manually changed the settings of the 'result component' (close model from 'true' to 'false') and then the component does show the new results of the axial forces for the new span length and the error is gone until I make another change in one of the variables.

Views: 453

Attachments:

Replies to This Discussion

There was an issue with an older build of the plugin that might explain this.

http://geometrygym.wikidot.com/local--files/downloads/ggRhinoGSAv8.... is the latest and updating might help.

What also I would recommend is only having a single solve component, and extracting out the different queries in a list (else the model would update and solve twice for each change).

Refer to the attached which works for slider changes for me.

Cheers,

Jon

Attachments:

Thanks for the reply Jon, it works for me too when changing the sliders. I also updated the plugin to the latest version.

I am making three more queries, and I will use a single solve component and then extract all the queries out of that solve component. Before I used the 'cull pattern' component for extracting out the queries, but that didn't work for me, that is why I used multiple solve components. But with List Item this is even easier.

I can't thank you enough!

Cheers,

Stefan

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service