Dear all:
The shell optimization in this script (Shell Cross Section Optimization - Karamba3D) as well as the shell optimization in my own script do not seem to work. For example, in the Karamba example script above, you can change the loading, utilization limit, or the displacement limit, and either Opticrosec does not change the shell size, or model view does not update the cross section tags with the final sections, and only shows you the tags of the section the model was initialized with. Please help!!
Hi, the model view will only show the starting cross section name for shells. This is because of the rendering time to needed to display all the names for all the mesh faces. If you disassemble your Model, your shells and then the cross sections, you will see each face has a different cross section.
Hi Matthew,
Thanks for your response. I tried disassemble model, and reduced the DCR to 0.2 to try and get the model to choose anything other than its starting section. However, it still does not, and the element output from disassemble model is still “shell 10”
Further, it states that a certain number of shells exceed their max available size, but I have still no way of knowing what size they are.
The way this manifests in my own model is shown below. The shells have a range of 20cm to 50cm. The “model view” component always displays ‘Shell 20’ (the initialized section) and the “disassemble model” widget always outputs ‘Shell 20’ as well no matter what the design criteria are. I tried to check this using the “Element query” widget, by dividing the volume by the surface area of each shell and get results that range from 13-15.5cm, which does not make sense, since shells less than 20cm are not an input to the model at all.
Hi Matthew,
That works! Thank you very much.
Best,
Dev
Hi Matthew, I have one more question about this example model (and I’m seeing the same issue in mine). Why doesn’t the output displacement match the displacement limit? The shell thickness has not reached its maximum in either models.
Try to adjust the SLS iterations in the options.
please refer to Error with OptiCroSec results - Grasshopper / Karamba3D - McNeel Forum
1 Like
Understood, thank you so much Matthew.