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

Minimal value in keyword TSTEP #5769

Open
Ruslan1541 opened this issue Nov 28, 2024 · 1 comment
Open

Minimal value in keyword TSTEP #5769

Ruslan1541 opened this issue Nov 28, 2024 · 1 comment

Comments

@Ruslan1541
Copy link

Ruslan1541 commented Nov 28, 2024

Hello!

I want to know, if it is possible to set a value in TSTEP below than 1 second?
Because after several tests, I estimated that all steps below this limit are skipped unil the simulation reaches to 1 second (below is an example).

Input file (there is a lab unit (hours)):
Снимок экрана 2024-11-28 180011

simulation:
Снимок экрана 2024-11-28 175933

@blattms
Copy link
Member

blattms commented Dec 3, 2024

Please also consult the reference manual.

It is a bit unclear to me, what you want to achieve. The output that you are showing indicates that OPM-flow is having convergence issues. What it does in this case is to decrease the time step and retry. Often smaller time steps make the system easier to solve. If this approach does not lead to successful convergence, then we eventually give up and abort the simulation. It might be a coincidence that this happens for 1 second time steps in your case.

Giving up because of excessive time stepping might be a sign that your model is not physically sound / well posed. It also can be a bug on our side, of course. It might be good to take a look at the warnings that the simulator is printing.

TSTEP tells the simulator when it should output report steps. This also means that it implicitly sets a maximum step size to be used. You may use small values for this. Just be aware that the simulator will create output for each of theses steps and hence this might consume a lot of space. Maybe that is not what you want?

If you know that the simulation will need to use small time steps, then I would prefer the keywords NEXTSTEP together with DATES.

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

No branches or pull requests

2 participants