Unable to retrieve load case results [SOLVED]

There appears to be a bug in the retrieval of load case results.

The GetResults method retrieves only results from load combinations but fails to capture load case results. Furthermore, the GetLoadCaseResults method returns an empty list.

The issue occurs in one model but not in another, despite both models having defined load cases and load combinations. Struxml file of the model from which results cannot be retrieved is attached.

Test.struxml (467.6 KB)

This issue arises even if analysis is ran with the calcCase set to true and it is persistent across several different result types, including NodalDisplacement and BarInternalForces.

Contents of log file that has been generated when running GetLoadCaseResults method is shown below:
step: cmdopen
t: 10/15 23.44.45.582
cmdopen:‘; CXL CS2SHELL OPEN’
t: 10/15 23.44.49.399
Script file finished
step: cmdsave
t: 10/15 23.44.49.762
cmdsave:‘; CXL CS2SHELL SAVE’
t: 10/15 23.44.49.929
Script file finished
step: cmduser
cmduser:‘; CXL $MODULE RESMODE’
step: cmdcalculation
t: 10/15 23.44.51.294
cmdcalculation:‘; CXL $MODULE CALC’
t: 10/15 23.45.03.405
Script file finished
step: cmdlistgen
t: 10/15 23.45.03.831
cmdlistgen:‘$ MODULECOM LISTGEN’
listgen successful
t: 10/15 23.45.04.104
Script file finished

Hi @TheFishTankGuy

I have just got back from holiday :slight_smile:
Thanks for opening the ticket. I will check it ASAP!

Hi @MarcoPelle,
Did you found out something new about this bug?

ehi @TheFishTankGuy

Looks like we have an issue with our parser.
LoadCase 1 fail to be parse for a bug in our Regex.

While we fix the bug, you can modify it with a different name such as “case 1” .

@TheFishTankGuy

I have just found the bug and solved it! 24.3.0 is plan to be release at the end of December. Let me know if you require a beta version and I will make one for you.

We are also planning to refactor our result reader class to make it more stable/fast. Do you notice some small performance right now?

Hi Marco and happy new year!

Sorry for late reply. I have now tested fix in version 24.3.0 and it works great. :slight_smile:
Thanks.

1 Like