-
Notifications
You must be signed in to change notification settings - Fork 89
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
running simulation with a time step > 1e6 s #143
Comments
I have tried to increase this value up to 1e9. Now I have other problem. When the current time becomes higher than 1e9, the time step change from its original value to 1e9, whichever it value was before. |
The fix for this is real quick - I'll add it to the existing pull request for the event manager mpi fix (#136). |
1e9 is hardcoded here: https://github.com/GEOSX/GEOSX/blob/9f55428ad550a4a06dcc4e16ec907a223c3d92a0/src/components/core/src/managers/Events/PeriodicEvent.cpp#L186 |
This one is a bit different, since it is setting the forecast (integer number of cycles until the event is expected to execute), not the time-step. |
My bad, this is fine then |
We should also set the event start/end time appropriately in the EventBase. It may be useful to have this as a special argument to the documentation node @rrsettgast . |
Thanks for your answers, for me it's ok. I will close the issue once the PR is merged |
@cssherman @AntoineMazuyer Is this done? |
Yes, this should be working now. |
Describe the bug
I have noticed some problems when trying to run simulations with dt > 1e6 seconds. GEOSX comes back to a 1e6 seconds time step. 1e6 seconds is 10 days, so this limit is not very convenient when dealing with reservoir simulations.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The time step inputed should be taken into account
Additional context
@klevzoff and I have noticed that there is an hardcoded value here
The text was updated successfully, but these errors were encountered: