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

running simulation with a time step > 1e6 s #143

Closed
AntoineMazuyer opened this issue Aug 28, 2018 · 9 comments
Closed

running simulation with a time step > 1e6 s #143

AntoineMazuyer opened this issue Aug 28, 2018 · 9 comments
Labels
type: bug Something isn't working

Comments

@AntoineMazuyer
Copy link
Contributor

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:

  1. Clone the develop branch
  2. Try to run a TPFA simulation with a time step > 1e6

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

@AntoineMazuyer
Copy link
Contributor Author

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.

@cssherman
Copy link
Contributor

The fix for this is real quick - I'll add it to the existing pull request for the event manager mpi fix (#136).

@klevzoff
Copy link
Contributor

1e9 is hardcoded here: https://github.com/GEOSX/GEOSX/blob/9f55428ad550a4a06dcc4e16ec907a223c3d92a0/src/components/core/src/managers/Events/PeriodicEvent.cpp#L186
We should probably get rid of both constants. Simulation time scales are physics-dependent and can be arbitrary.

@cssherman
Copy link
Contributor

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.

@klevzoff
Copy link
Contributor

My bad, this is fine then

@cssherman
Copy link
Contributor

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 .

@AntoineMazuyer
Copy link
Contributor Author

AntoineMazuyer commented Aug 29, 2018

Thanks for your answers, for me it's ok.

I will close the issue once the PR is merged

@joshua-white joshua-white added type: bug Something isn't working priority: high labels Sep 6, 2018
@rrsettgast
Copy link
Member

@cssherman @AntoineMazuyer Is this done?

@cssherman
Copy link
Contributor

Yes, this should be working now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants