algorithmic modeling for Rhino
My first look at this but for starters you can only apply a point load at a node of the system which you are not doing. I think you need to convert your point load to an equivalent linearly distributed load and input that into the L node of the FE component. Secondly even if your point load was located at a node of the system you're attaching it to the wrong input builder component.
Thank you so much for the fast reply!
What you meant is that I should use linear load instead of point load for that single line?
And I did not quite understand "even if your point load was located at a node of the system you're attaching it to the wrong input builder component." So which one shall I choose?
Thx
>What you meant is that I should use linear load instead of point load for that single line?
Yes. Use an equivalent linear load.
The applied point load has to be applied at an already defined node of the system. You can't just apply it somewhere in space.
If you were properly using a point load (which you're not doing in your current definition) you would input it at the M input in the System Builder component. You're currently inputting it into the 'Minc' input which sets the 'Minimum allowed length for a frame element'.
I posted the file again in case I forgot to internalize the curve data in the earlier attachment.
Well, I do not know how to express my gratitude.
I put it into GH, and it works well. Now I began to apply it to more difficult
situation. Thank you!
1) I thought that the X translation of the supports would need to be free to account for the axial shortening of the bar end points as the bar bends. However this doesn't seem to be accounted for in the output. There is no movement of the supports axially inward. RY is free to allow the ends to bend without inducing a moment at the supports.
2)The "L" (load) of the curve component is not a node (end point) of the curve system and cannot therefore take input from the Point Load component (at least to my understanding).
Keep in mind that it's very possible that I'm making mistakes with Millipede both in implementing it and in assuming how it should work. This is the first definition that I've tried to work through.
Yes. True means 'can't move'; false means 'can move'.
What are you trying to determine in this recent definition?
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by