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

Excessive time step choping for Norne when using flexible solvers. #2759

Closed
blattms opened this issue Sep 3, 2020 · 12 comments · Fixed by #2761
Closed

Excessive time step choping for Norne when using flexible solvers. #2759

blattms opened this issue Sep 3, 2020 · 12 comments · Fixed by #2761
Labels

Comments

@blattms
Copy link
Member

blattms commented Sep 3, 2020

Runing flow --linear-solver-configuration=ilu0 NORNE_ATW2013 results in excessive time step chopping for current master. Same for CPR. Using the default, i.e. without the flexible solver bx skipping the argument, works as before.

@blattms blattms added the bug label Sep 3, 2020
@akva2
Copy link
Member

akva2 commented Sep 3, 2020

I can reproduce.

However, results are ballpark similar (and no apparent excessive time step cutting) if --matrix-add-well-contributions=true is given with the flexible solver (ilu0). Maybe this is an implicit requirement with the flexible solver?

@blattms
Copy link
Member Author

blattms commented Sep 3, 2020

the connection with the wells might hint at the changes in #2694.

@GitPaean
Copy link
Member

GitPaean commented Sep 3, 2020

I guess --matrix-add-well-contributions=true is required for cpr.

@akva2
Copy link
Member

akva2 commented Sep 3, 2020

as stated, this was with ilu0, not cpr.

@blattms
Copy link
Member Author

blattms commented Sep 3, 2020

@GitPaean at least for ILU0 I thought this was resolved with #2694. For CPR you might be right, but currently no exception is thrown when not passing this option and I am pretty sure we did throw one some time ago.

@blattms
Copy link
Member Author

blattms commented Sep 3, 2020

Seem like when running with 1 process there is an if-else missing in ISTLSolverEbos.hpp#L771-L775.

@blattms
Copy link
Member Author

blattms commented Sep 3, 2020

Will try to fix

@akva2
Copy link
Member

akva2 commented Sep 3, 2020

beat me by 1 min ;)

@akva2 akva2 closed this as completed Sep 3, 2020
@akva2 akva2 reopened this Sep 3, 2020
@blattms
Copy link
Member Author

blattms commented Sep 3, 2020

Well, I still have to compile and run norne before posting a pr. hence if yours is tested....

@atgeirr
Copy link
Member

atgeirr commented Sep 3, 2020

This is indeed a bug as described above, #2706 has also fixed this I think, but has become stale.

@blattms
Copy link
Member Author

blattms commented Sep 3, 2020

Maybe we should not hide bug fixes in feature PRs?

@atgeirr
Copy link
Member

atgeirr commented Sep 3, 2020

Maybe we should not hide bug fixes in feature PRs?

I was actually not aware it would have fixed a bug in the existing code, I just made sure it worked in the new...

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

Successfully merging a pull request may close this issue.

4 participants