We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently CUDS objects are reloaded lazily, one by one after a simulation has been executed.
This approach is not beneficial for all scenarios, so the should be a keyword argument to let the user decide on the reload behavior:
E.g.
session.run(reload=True) session.run(reload=[<oclasses_to_reload>])
Anther idea is not reloading one-by-one but always also reload a neighborhood or or contained cuds when reloading.
The text was updated successfully, but these errors were encountered:
No longer relevant in SimPhoNy v4.
Sorry, something went wrong.
No branches or pull requests
Currently CUDS objects are reloaded lazily, one by one after a simulation has been executed.
This approach is not beneficial for all scenarios, so the should be a keyword argument to let the user decide on the reload behavior:
E.g.
Anther idea is not reloading one-by-one but always also reload a neighborhood or or contained cuds when reloading.
The text was updated successfully, but these errors were encountered: