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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pvt issue 1202 #1212

Merged
merged 4 commits into from
May 23, 2023
Merged

Pvt issue 1202 #1212

merged 4 commits into from
May 23, 2023

Conversation

asnyv
Copy link
Collaborator

@asnyv asnyv commented Apr 24, 2023

Insert a description of your pull request (PR) here, and check off the boxes below when they are done.


Contributor checklist

  • 馃帀 This PR closes Bugs in PvtPlot聽#1202.
  • 馃摐 I have broken down my PR into the following tasks:
    • Task 1
    • Task 2
  • 馃 I have added tests, or extended existing tests, to cover any new features or bugs fixed in this PR.
  • 馃摉 I have considered adding a new entry in CHANGELOG.md, and added it if should be communicated there.

Copy link
Collaborator

@rubenthoms rubenthoms left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. There is still uncertainty if the data frame is coming in presorted.

Comment on lines +92 to +95
# data_frame = data_frame.sort_values(
# ["PRESSURE", "VOLUMEFACTOR", "VISCOSITY"],
# ascending=[True, True, True],
# )
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I remember correctly this was only to ensure that the list is sorted and that the points plotted are connected with lines in the correct order (under the assumption that Plotly is plotting in the order given by the input array). This might not have an effect since the data frame might already be sorted beforehand. However, I wonder if the plots would still be correct if the df wasn't. If we are 100% sure that the df is always sorted correctly, this can be removed.

@anders-kiaer anders-kiaer marked this pull request as ready for review May 23, 2023 11:38
Copy link
Collaborator

@anders-kiaer anders-kiaer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed offline, we merge this as is and include it in the upcoming komodo test phase. We think the correct way is to use the incoming sorting of the Eclipse PVT data (i.e. the way it comes out of ecl2df).

@anders-kiaer anders-kiaer merged commit 1b1bb17 into equinor:master May 23, 2023
4 checks passed
@anders-kiaer anders-kiaer deleted the pvt_gor_bug branch May 23, 2023 12:56
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

Successfully merging this pull request may close these issues.

Bugs in PvtPlot
3 participants