Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different results using SERIALIZER_TRACE_ERROR and SERIALIZER_NO_TRACE #12222

Open
aronnoordam opened this issue Mar 22, 2024 · 1 comment
Open

Comments

@aronnoordam
Copy link
Member

When im loading a derived class from set_moving_load_process from the StructuralMechanicsApplication with the kratos serializer, I get the message:

"MemoryError: bad array new length"

when im using SERIALIZER_NO_TRACE SerializerTraceType.

However when Im using the SerializerTraceType SERIALIZER_TRACE_ERROR, I do not have any problem and my simulation runs well.

Any idea what can cause this issue?

@aronnoordam
Copy link
Member Author

aronnoordam commented Mar 27, 2024

update for the people interested:

in my case: I was adding each stage to a list something like:

` model = Kratos.Model()

stages = []

for parameter_file_name in parameter_files:

    with open(parameter_file_name,'r') as parameter_file:

        parameters = Kratos.Parameters(parameter_file.read())

    simulation = Analysis(model,parameters)

    simulation.Run()

    stages.append(simulation)`

this was causing the memory error. I do not understand why my simulation was working with: SERIALIZER_TRACE_ERROR though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant