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

Incorrect reporting of date for E300 in combination with lab units #4770

Closed
alifbe opened this issue Sep 26, 2019 · 4 comments
Closed

Incorrect reporting of date for E300 in combination with lab units #4770

alifbe opened this issue Sep 26, 2019 · 4 comments
Labels
BugInRelease Bug in an official release FromCommunity Issue originates from the community.

Comments

@alifbe
Copy link

alifbe commented Sep 26, 2019

It seems like ResInsight has issue loading simulation result in lab unit. Due to the issue in E300, We have to convert our model into lab unit and ResInsight didn't load the dynamic data.

image

Floviz seems to load the case just fine. I have tried 2019.08.1 and 2019.04.0 both Windows and Unix with no luck.

@magnesj
Copy link
Member

magnesj commented Sep 26, 2019

Hi, thanks for your feedback.

To further investigate this issue, it would be useful to get a copy of your test dataset. Send by mail, or upload as attachment to a comment.

@magnesj magnesj added FromCommunity Issue originates from the community. BugInRelease Bug in an official release labels Sep 26, 2019
@alifbe
Copy link
Author

alifbe commented Sep 26, 2019

Unfortunately the dataset is confidential. But I have made a simple dataset which I exhibit the same issue.

The data file was simulated using E300. It works fine when I simulated using E100 lab unit. So it seems to be combination of lab unit and E300.
COREFLOOD.zip

@magnesj
Copy link
Member

magnesj commented Sep 27, 2019

Thanks for your dataset.

For some reason, the date for all time steps is identical (2018-09-31). We also read the DAYS vector (double values), and the values here ranges from 0.0 to 1.9. This looks like a bug in E300 to me. Can you report this bug to the relevant people?

As a workaround, we will identify the situation you have reported and use the double value from DAYS vector as offset to the date reported as integer triplet for day, month and year. This fix will be included in the upcoming patch release planned to be released in a few days. The fix will be available on dev-branch today.

Thanks for your feedback.

@magnesj magnesj changed the title Resinsight in lab unit Incorrect reporting of date for E300 in combination with lab units Sep 27, 2019
magnesj added a commit that referenced this issue Sep 27, 2019
User reports issues with import of dynamic properties for E300 simulation. E100 works as expected. For some reason, the date for all time steps for the E300 simulations is identical. This fix detects the situation, and use the double value from days vector as offset.
magnesj added a commit that referenced this issue Sep 27, 2019
#4770 Incorrect reporting of date for E300 in combination with lab units
@magnesj magnesj closed this as completed Sep 27, 2019
@magnesj magnesj added this to the Patch release 2019.08.2 milestone Oct 1, 2019
@alifbe
Copy link
Author

alifbe commented Oct 4, 2019

Hi @magnesj

I tried the patch release and it works on the file that I have sent you. But not the one that I am actually working it.

The case is attached here.
test_case.zip

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

No branches or pull requests

2 participants