Remove functions to filter connections#1059
Conversation
|
Thanks. There was an email conversation between @joakim-hove, @GitPaean and me about that functionality.
Not sure whether the last point isn't rather a bug than a feature. |
45bb067 to
e850906
Compare
|
jenkins build this opm-grid=393 opm-simulators=2041 please |
e850906 to
94f679e
Compare
94f679e to
3f2f75a
Compare
|
jenkins build this opm-grid=393 opm-simulators=2041 please |
|
jenkins build this opm-grid=393 opm-simulators=2041 opm-upscaling=279 please |
1 similar comment
|
jenkins build this opm-grid=393 opm-simulators=2041 opm-upscaling=279 please |
|
for one real case, it throws at the |
Thank you for looking into this - that is extremely valuable. I must say I was a little surprised by where the exception was raised; it "should" have been here, anyway I will look into it. |
|
@joakim-hove : Are we going to pick this up or should we just close this PR? |
|
I'm closing this now. The patch no longer applies cleanly and nobody appears to care enough to shepherd it into master. |
It is all about active cells!
Background
The first implementation of the EclipseGrid in opm-common only took the
ACTNUMvalues from the deck into account. Then at a later stage the grid processing code would calculatePORVand possibly deactivate some additional cells. When assembling theWellConnectionsobject the cells will be checked, and connections to inactive cells will be ignored. However, because the downstream grid processing might deactivate addition cells we must check the connections in a second pass. This is the purpose of theSchedule::filterConnections()method.Since the original implementation of the EclipseGrid the PORV calculations have been moved to opm-common, we should therefor now be in a situation where the ACTNUM in the original EclipseGrid is complete, and no further cells should be deactivated. This PR removes the
filterConnections()functionality and downstream PR's remove the calls tofilterConnections(). This will be one step further to get an immutableScheduleobject, and should also help in currently ongoing parallellizing efforts.Disclaimer
The grid processing code is complex, and not very well tested in terms of unit tests. I might have misunderstood things, this set of PR's should be tested on relevant industrial models beyond the testcases found in jenkins.
OPM/opm-upscaling#279
OPM/opm-simulators#2041
OPM/opm-grid#393