Optimize cross section - Beam sets

Replies to This Discussion

Permalink Reply by Kaveh Allahdin on August 9, 2013 at 6:15am

can you upload the definition.I will look at it tonight!

Permalink Reply by Rasmus Holst on August 9, 2013 at 7:09am

Hey.

Yes here I have attached the definition. I am starting to suspect that the meshLoad which is acting weird, might have some connection to the problem.

 

Attachments:

• Altan.gh, 47 KB

Permalink Reply by Kaveh Allahdin on August 10, 2013 at 5:16am

HI Rasmus,

I checked your definition. For optimization of the crosssection you need to define a domain of cross section . means you have to let it to choose between a list of cross section. 

for making the group of beams you need to define a family in the cross section component. So basically you dont need that python script which gives every section an ID(however I liked that).

I did not clean the definition. but seems working!

check it if it is what you want

Regards,

Kaveh

Attachments:

• Altan.gh, 44 KB

Permalink Reply by Rasmus Holst on August 12, 2013 at 1:29am

Hi Kaveh.

Thanks a lot for your help. But I am wondering. When doing like this. It seems all cross sections in "a" becomes" the same and all the ones in "b" becomes the same. In this case I have a lot of beams in group "a", therefor it might be more optimal in terms of material etc. if they had different sections.

 

In this case, do I then need to turn group "a" into "a,b,c,d,e.." where each letter corresponds to each beam? So all parts of the same beam will have the same letter? I find it a bit strange that I wasn't able to do it with my naming of ID's.

 

Anyways thanks alot for you help.

Do you have any idea of what is going on with the mesh to line loads?

 

Best regards Rasmus

Permalink Reply by Kaveh Allahdin on August 12, 2013 at 2:07am

That was Just how you do it as you want to assign a section for a group of beams not every beam gets different cross section. actually the idea of a python component that set one ID for a group of beams based on the number of row they are in or the number of column they are in makes it very versatile which you almost did with your python component but for every one of beams. Also in the cross section definition component  they need also to  be used as not just for  element ID but also for Family name of beams.

Moreever If you think ,Section optmization for every beam is not very practical. In reality you would have continuous beams as rows which would cut other beams into separate beams or simply the other set of beams are still continuous and simply go above them or undera t least in flat structures.

 

Permalink Reply by Rasmus Holst on August 12, 2013 at 3:09am

Okay. Thanks a lot. I am also going to try and make the optimization with Galapagos, to account for the displacement as well as the moment.

 

I you get an idea of whats wrong with my meshLoads let me know.

 

Thanks again.

 

Best regards Rasmus