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

Cell result: Shifting of some results properties where model includes inactive cells #11743

Open
permeAbiliTy opened this issue Oct 3, 2024 · 4 comments
Labels
Bug Bug not yet in an official release FromCommunity Issue originates from the community.

Comments

@permeAbiliTy
Copy link

When viewing cell results for two different models created for SPE CSP11 (one 2D and one 3D) run using tNavigator, cell results are distorted for a number of the properties, but are fine for others. Visually, this seems to be related to the inactive cells present in the model. These model results plot without issue in an alternative 3rd party post-processor. The problem only seems to occur if the INIT & X0000 files are read in along with a dynamic grid file. Probably also worth noting that this is a thermal model and there are cells that are inactive for flow (zero PV) but active for the thermal calculations.

Examples below show ZMF_1 in the 2D model where the blue cells (ZMF=0.0) should align with the inactive zone, but are shifted to the right, increasing in distance every time an inactive cell is reached. Second plot shows SGAS for the same model plotting as expected. ZMF_2 is similarly distorted. From memory, an old case included some additional output, which resulted in additional distorted properties, but not the ones that were added.

A similar effect is seen in the 3D model for ZMF_1 and _2, but with everything shifted in each layer and then shifts continuing in subsequent layers. Another two screenshots included below for the 3D case.

image
image

image
image

@magnesj
Copy link
Member

magnesj commented Oct 7, 2024

Hi, thanks for the detailed bug description. We support two grid model readers, resdata and opm-common. Please check if your data can be imported correctly using opm-common.

If you still have issues, we need a test dataset to be able to investigate further.

image

@magnesj magnesj added Bug Bug not yet in an official release FromCommunity Issue originates from the community. labels Oct 7, 2024
@permeAbiliTy
Copy link
Author

Hi, I don't see quite the same dialog and by default I'm seeing libecl rather than resdata:
image
But switching to opm-common (beta) results in a crash on loading the 2D model, and the 3D model seems to load without any dynamic grid results.

I can provide a test case, but it is a few GB. What is the best way to transfer this over to you?

@magnesj
Copy link
Member

magnesj commented Oct 10, 2024

Hi, we have fixed several issues for the opm-common reader that is available in the latest release. Please test the opm-common reader before we transfer the data.

https://github.com/OPM/ResInsight/releases/tag/v2024.09.1

@permeAbiliTy
Copy link
Author

Sorry, I had tested originally on v2024.09.1 but when I reported the opm-common tests above, I was using an older version. I have now tested on v2024.09.1:
for the 2D model, using opm-common seems to resolve the issue
for the 3D model, the dynamic results do not get loaded in at all using opm-common

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Bug not yet in an official release FromCommunity Issue originates from the community.
Projects
None yet
Development

No branches or pull requests

2 participants