Error: RandomizedMaterialWrapper "invalid literal for int(): 'rebar'"

Post Reply
amb_1
Posts: 63
Joined: Wed Jun 08, 2022 11:32 am

Error: RandomizedMaterialWrapper "invalid literal for int(): 'rebar'"

Post by amb_1 » Mon Apr 07, 2025 11:55 am

Dear STKO Team,
I need help resolving an error when switching from ASD3D to RandomizedMaterialWrapper in an eccentric column model.

Issue:
Model works with ASD3D.
Fails with RandomizedMaterialWrapper, throwing:
invalid literal for int() with base 10: 'rebar' (new error).

Actions:
Checked material definitions, input files (attached), and documentation—no solution found.
Questions:
Are additional inputs required for RandomizedMaterialWrapper?
Could parameter parsing (e.g., string vs. integer) cause this?

Attachments:
Input files (working/error versions).
Error screenshot.
Thank you for your support.
Best regards,
Attachments
57d6231a0197dd051207b2a55bc1737.png
57d6231a0197dd051207b2a55bc1737.png (233.71 KiB) Viewed 1399 times
9a1d7eac56154b735fc2baff4e74247.png
9a1d7eac56154b735fc2baff4e74247.png (710.3 KiB) Viewed 1399 times
model.zip
(741.45 KiB) Downloaded 374 times

amb_1
Posts: 63
Joined: Wed Jun 08, 2022 11:32 am

Re: Error: RandomizedMaterialWrapper "invalid literal for int(): 'rebar'"

Post by amb_1 » Tue Apr 08, 2025 2:57 am

Dear STKO Team,

I am writing to seek your technical support regarding an issue encountered during my recent testing. After troubleshooting, I identified that the problem likely stems from the Recorder function: the software operates normally when the Recorder is removed, but fails to generate output when the Recorder is enabled. This suggests a potential conflict or bug within the Recorder module. Could you kindly investigate this behavior?

Thank you for your prompt attention to this matter.
Attachments
ede55240324d5571ad49c73bea2f0e6.png
ede55240324d5571ad49c73bea2f0e6.png (82.39 KiB) Viewed 1379 times

STKO Team
Posts: 3066
Joined: Tue Oct 29, 2019 8:45 am

Re: Error: RandomizedMaterialWrapper "invalid literal for int(): 'rebar'"

Post by STKO Team » Thu Apr 24, 2025 8:12 am

I cannot reproduce the error with my STKO version 4.0.0.
What version are you using?

Post Reply