youarenotyourstuff t1_j8mtm65 wrote
Reply to comment by dCLCp in NASA's "evolved structures" radically reduce weight – and waiting by Maxcactus
A big one is that designing with this process means at every step you are highly dependent on complex software modeling. Instead of using well known design rules to develop your design, you have to run a sophisticated algorithm that probably needs a hefty amount of compute power. Then you have to run FEA on literally every part, again needing lots of resources. That kind of software isn’t cheap and neither are the computer clusters.
Also, you have to put a lot of effort into defining your requirements very precisely and uncovering hidden requirements. For example, if you need a lot of strength in a part do you need that in both directions or only one? If you only need strength in one direction the best solution might be a steel cable, but I don’t know if there algorithms would consider that.
There’s also part integration. Things have to be designed for manufacturing and service (part tolerance stack up, order of operations, tool and hand clearances, etc.)
You also have to carefully consider your validation and what assumptions it makes about the parts that might no longer be true.
In the end, generative design is probably only worth the effort for specific parts or even portions of those parts, not the whole product.
____Theo____ t1_j8ny30p wrote
But all of these considerations are also in play when you design something without the gen algo. This is just engineering lol
youarenotyourstuff t1_j8o99hm wrote
Yeah that’s my point. All the normal engineering steps apply for sure. Just some of them are made more difficult due to a complex shape instead of a beam.
Viewing a single comment thread. View all comments