hexagon logo

AUTOMSET + RIGID=LAGRAN?

Is there a way to use CTE on RBE2 with AUTOMSET? It seems AUTOMSET is ignored while using RIGID=LAGRAN in SOL101, can't run without it on the model we have to run... Any way of doing this, it's a simple TEMP(INIT)/TEMP(LOAD) case, but the rigids need to be able to expand...
Parents
  • Thanks @Zachary Fata​, removing RBE2 is what I'm doing right now, and it's very tedious as it is a rather large model. AUTOMSET is about 20 years-old, it's been a long time since I've seen "don't connect RBEs this way" to be honest Grinning APEX is actually allowing this and creating these connections. The preferred way would be for Nastran to take care of it, naturally. We'll file an Enhancement Request with PD to get AUTOMSET and LAGRAN to work together, this shouldn't be that much trouble to implement.
     
    Switching to RBE3 is not a workable solution, the underlying issue in the fault with the RBE2s would be exactly the same with RBE3s. Besides, results might be "less wrong" but they're still wrong, and induce some REB3-specifics that would break other things in our model, which is why we don't use RBE3 in the first place.
Reply
  • Thanks @Zachary Fata​, removing RBE2 is what I'm doing right now, and it's very tedious as it is a rather large model. AUTOMSET is about 20 years-old, it's been a long time since I've seen "don't connect RBEs this way" to be honest Grinning APEX is actually allowing this and creating these connections. The preferred way would be for Nastran to take care of it, naturally. We'll file an Enhancement Request with PD to get AUTOMSET and LAGRAN to work together, this shouldn't be that much trouble to implement.
     
    Switching to RBE3 is not a workable solution, the underlying issue in the fault with the RBE2s would be exactly the same with RBE3s. Besides, results might be "less wrong" but they're still wrong, and induce some REB3-specifics that would break other things in our model, which is why we don't use RBE3 in the first place.
Children
No Data