I am trying to find a workaround to the lack of load combination in karamba while using the crossection optimisation but i am not sure about few things, I have two options so far:
- Use the LCfactor in the model viewer, feed different load combination and “browse” through them to find the worst case.
- Does the crossection optimisation component is done on a model with the LCfactors applied or without?
- Is there an already coded way to envelop the crossection optimisation when browsing through the different Load combinations, in order to find the biggest crossection? (Worst case scenario)
- Creating one karamba load case per load combination and feed various multiplication factors to the seperate Karamba load cases:
This option allows the corssection optimisation to be done through all the load combinations but is extremely heavy computation wise and does not allow to have a lot of different load combinations
Any thoughts or better ideas?