Karamba - user problems

please post here in case of karamba problems !

Replies to This Discussion

Permalink Reply by Erichen on October 27, 2015 at 2:50pm

Just some of them

Permalink Reply by Karamba3D on October 28, 2015 at 2:17am

Which of them?

Permalink Reply by Erichen on October 28, 2015 at 6:34pm

I just open the benchmark folder. The shell analysis is Okay, but the others are not.

Permalink Reply by Erichen on October 28, 2015 at 10:41pm

FYI, I use the free version.

Permalink Reply by Karamba3D on October 29, 2015 at 1:06am

Take a look at the Karamba manual. There the components are marked which are not part of the free version of Karamba.

Permalink Reply by Erichen on November 3, 2015 at 9:38am

Hi guys,

If I want to add a force in the middle of a beam, I need to create a node on this beam and separate the beam into two segments based on the node, right?

Thanks

Permalink Reply by Karamba3D on November 4, 2015 at 12:01pm

Hi Erichen,

at the moment (Karamba 1.1.0) this is the way to do it.

Best,

Clemens

Permalink Reply by Sean Reinsma on January 6, 2016 at 4:04pm

Hi,

I am attempting to run a buckling analysis on a grid shell under multiple loads cases. The model assembles and I can run the THII algorithm, but running the buckling analysis often causes rhino to crash and windows closes the application. Attached is my grasshopper file with the THII analysis set to load case 0. The file crashes if I attempt to change the load case to one of the others i have defined and results in the attached error report.

Any help in resolving this issue would be much appreciated.

Thanks,

Sean

Attachments:

Karamba Analysis.gh, 97 KB
Crash.PNG, 47 KB

Permalink Reply by Karamba3D on January 7, 2016 at 12:24am

Hi Sean,

with my current build of Karamba I was not able to reproduce the problem.

I changed the element identifier from '1' to '1a'. In Karamba 1.1.0 using integer numbers as identifiers sometimes leads to unexpected behavior.
Could you try to reduce the definition as much as possible? This would make it easier to find the bug.

Best,

Clemens

Permalink Reply by Sean Reinsma on January 7, 2016 at 8:32am

Thanks for your help. Using your current build seems to have fixed the issue.

Sean

Permalink Reply by Sean Reinsma on January 14, 2016 at 6:56am

Hi Clemens,

Further to my previous post, I am now attempting to iterate my previous definition with Galapagos in order to optimize the form for the minimum factor of safety against buckling. The definitions prior to Karamba are to allow the genes to manipulate the form of the shell and then kangaroo to relax the form to its "equilibrium" state.

The definition, as attached, runs fine over one iteration. However, when I run the Galapagos solver, rhino slowly uses up my computers memory and then ultimately crashes (around 80 Galapagos iterations). I don't think that the surface patch, or kangaroo are the issue, as I have run other iterative definitions through them without issue.

I believe Karamba may be occupying memory each iteration that is not released when a new iteration begins. This problem is exasperated by the fact that I am running 11 load cases, 9 of which are point loads defined over each vertex of the mesh. I ran a definition with only one load case, and it reached 170 generations (with a population of 50 for each generation). However, at this point it had occupied 90% of my computer's available memory.

Do you know of a way to ensure that Karamba purges its memory after an iteration, or is this a possible memory leak bug?

Thanks again, any help you can provide is much appreciated.

Sean

Attachments: