GeometryGym, ggGSA bake problem, duplicate beam elements, need help

Dear all,

I made a geodesic dome model with several parameters in Grasshopper and create Beams and Nodes in the end. Baking to GSA worked just fine and also retrieving data back from GSA.

However I discovered that all of my beam elements were baked twice in GSA. "New model each bake" is set to true in Grasshopper so that shouldn't be an issue.

I also encountered the problem that nothing was displayed / no document was created in GSA if I didn't open GSA prior to baking in Grasshopper. That's why I tried out commands in Rhino (ggGSA delete model, draw model, etc) and all of a sudden also the previously baked models remained in GSA overlapping the new bake.

I tried opening a new document in GSA, deleting the stored data in Grasshopper and rerunning the calculation, opening and closing all programs, restarting the computer and yet still the same issue. The previously baked model was "stored" in GSA and additional models were added "on top" with each bake.

I am really clueless as everything worked just fine this morning, I didn't change any settings in GSA or Rhino or Grasshopper and now all of a sudden I have duplicate beams and overlaying models and I am inable to retrieve meaningful results from GSA / work on the model (which sucks if you are working on your graduation thesis).

The Grasshopper file is attached. If you want to run it you can delete all containers after "ggGSA create beam" (pink groups) as they don't have any effect on the problem I described.

Another problem is the ggGSA query weight (see attachment). If you have any idea how to fix that I would also appreciate it.

Thanks a lot!

Cheers

Lisa

Attachments:

case study v3 2014-05-28.gh, 87 KB

Replies to This Discussion

Permalink Reply by Jon Mirtschin on May 29, 2014 at 7:06am

Hi Lisa,

What is printed to rhino command prompt about number of elements created ?

Baking Structure....
Material Count: 1, SectionProperty Count: 3, Node Count: 199, Element Count: 491, List Count: 1
Load Case Count: 1

Is what I get.

Can you try running rhino command ggGSAProps, click on options and make sure legacy mode for shared database is unticked? If it's not, and you have 2 gh definitions open (or data baked to rhino), it would all be stored in a common database.

If you don't have GSA already running, it's started as a background service (when model generation si triggered) which the user can't access. Watch this webinar for a little more description.

https://www.youtube.com/watch?v=jcDPeaKP8n0&list=PL0463D12B0DED...

I'll have to check if Self Weight can be extracted for a load case, I've attached a modification where an analysis case is generated (I disabled other solver components).

Let me know if this doesn't help.

Cheers,

Jon

Attachments:

casestudyv320140528.gh, 70 KB

Permalink Reply by Lisa O on May 31, 2014 at 7:11am

Hi Jon,

thanks for your reply. Legacy mode for database is unticked.

I followed your advise and first opened GSA, created a new document and then opened Rhino and Grasshopper.

Yet this is what I get when I first opened the file:

Material Count: 1, SectionProperty Count: 3, Node Count: 199, Element Count: 491, List Count: 1
Load Case Count: 1
Material Count: 2, SectionProperty Count: 6, Node Count: 199, Element Count: 982, List Count: 2
Load Case Count: 2
Material Count: 3, SectionProperty Count: 9, Node Count: 199, Element Count: 1473, List Count: 3
Load Case Count: 3

And for a new bake it then remains with

Baking Structure....
Material Count: 3, SectionProperty Count: 9, Node Count: 199, Element Count: 1473, List Count: 3
Load Case Count: 3

Now I did the same with a Grasshopper file that didn't contain analysis components and the problem was gone. I then unloaded Grasshopper restarted it and opened the file you attached and miraculously it worked (no duplicate beams and if I create a new document in GSA prior to each bake, the problem is fixed). So I hope it stays like this.

Thanks a lot for the components you added to my analysis. The results are exactly what I was looking for.

Thanks a lot!

Cheers

Lisa

Permalink Reply by Jon Mirtschin on May 31, 2014 at 8:09am

Hi Lisa,

I'll look further into this when I have a little more time.

Can you try consolidate the solvers into a single component? Leave the query input flattened. The output data should be on branches that you can extract out different results. This might work better in the interim. My saved def only had one active solver component.

Cheers,

Jon

Permalink Reply by Lisa O on May 31, 2014 at 9:47am

Dear Jon,

the problem occurred when I used your file but I might have had several grasshopper files opened. I will change it to 1 solver only and then investigate further. Thank you!

Lisa

RSS