Closed damianbobrowski closed 10 months ago
What I see now is
RSTAB 9.02.67 returns empty string ""
RSTAB 9.02.69 throw error ValueError: invalid literal for int() with base 10: 'IPE 100 | 1 - S235
so maybe my API call is wrong, and the difference is how RSTAB handle it between mentioned versions?
Hi @damianbobrowski, no this is in fact a bug. The SUDS is expecting integer where string is placed. We've been registering this error since 13.6.
How far is the work on this? Is it still present in Version 9.03.0007?
@scja1991
When I test above script with RSTAB 9.03.0007
it works without error.
Example two rows:
{
"location_flags": null,
"member_number": 1.0,
"location": 0.0,
"internal_force_n": 0.0,
"internal_force_vz": 2000.0,
"node_number": 1.0,
"internal_force_my": -10000.0,
"internal_force_mt": 0.0,
"internal_force_mz": 0.0,
"internal_force_vy": 0.0,
"specification": "1,2 | Beam | 1 - IPE 100 | L : 5.000 m"
},
{
"location_flags": null,
"member_number": 1.0,
"location": 5.0,
"internal_force_n": 0.0,
"internal_force_vz": 2000.0,
"node_number": 2.0,
"internal_force_my": 2.8683189157163724e-10,
"internal_force_mt": 0.0,
"internal_force_mz": 0.0,
"internal_force_vy": 0.0,
"specification": "1,2 | Beam | 1 - IPE 100 | L : 5.000 m"
},
@OndraMichal Is it officially fixed?
Hello @damianbobrowski, I just tested the script above on versions RSTAB: 9.04.007 and tool 1.09.1 and it worked. So I would consider it as officially fixed. Thank you for reaching out to us.
Describe the bug ResultTables.MembersInternalForcesBySection won't work with RSTAB 9.02.0069. It works with 9.02.0067
To Reproduce Run script:
Expected behavior ResultTables.MembersInternalForcesBySection should work as in RSTAB 9.02.0067
Screenshots
Desktop (please complete the following information):
Additional context not this time