News: HyperSizer.com has a Community Board and Customer Support System. Submit a ticket at http://hypersizer.com/ticket

Author Topic: Recursive Load Error  (Read 23890 times)

mnoftz

  • Client
  • **
  • Posts: 3
    •  
Recursive Load Error
« on: April 29, 2019, 03:24:52 PM »
Hello,

We came across this message when sizing one of our models last week. Despite our attempts to rename and re-apply the loads within Patran, there seems to be a recursive call to a non-existent load entry that appears only in a singular load cases. We have had a hard time replicating this error or trouble-shooting what causes it (load cases that share the same pressure conditions run perfect).

Besides completely throwing out this load-case, has anyone ever encountered this error and found a solution?

Best,

Mark

Stephen

  • Administrator
  • *****
  • Posts: 70
    •  
Re: Recursive Load Error
« Reply #1 on: April 29, 2019, 03:45:36 PM »
Hi Mark,

Can you provide a little more information about the problem? For instance, what version of HyperSizer are you using? And what is the solver you are using? Nastran?

Thanks,
Stephen

mnoftz

  • Client
  • **
  • Posts: 3
    •  
Re: Recursive Load Error
« Reply #2 on: May 01, 2019, 08:21:51 AM »
Hi Stephen,

We are using HypersizerPro v7.3.57 with Nastran 2018.2 and Patran 2018 installed.

This error is specific to the Assembly Projects tab. It occurs for beam elements during "importing material data" and "importing pressure/temperature loads." It only occurs in one load case. The affected beam assemblies will immediately throw this error upon sizing initiation. Skin assemblies are not affected.

After some tweaking, we found that the error does not occur if we split the force and pressure loading into different subcases. We also found that the error does not occur if we size components normally in the sizing tab or in HyperFEA.

-Mark

Stephen

  • Administrator
  • *****
  • Posts: 70
    •  
Re: Recursive Load Error
« Reply #3 on: May 01, 2019, 09:16:11 AM »
Mark,

I'm reaching out via email to gather more information.

Thanks,
Stephen