You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, yes I have thought about that usecase. I agree that it would be useful and I think it could be done. Obviously the curves can only be compared if they have the same flow rate type, WFR type, GFR type, unit system, datum depth (?).
In addition, if the table input values (THP values etc) are not the same, one of the tables needs to be "resampled" to the values of other. It's not exactly clear for me how to do that, but I will think about it.
I have a vfp prod class implementation that has some functionality for doing that. If the two curves has the same parametrization type (rate type, GFR type, WFR type) it already has functionality to do the resampling. It uses Scipy for interpolation and there are different options to handle values that are outside the ranges (extrapolation etc). If the curves have different parametrization type, there is no functionality that takes care of that automatically. However, to avoid dealing with every possible combination of parametrizations there is an interpolation option that takes in rates (oil, gas,water,gaslift) and calculates BHP. So if the rates + fractions that are going to be interpolated are transformed to rates first, there is a function to do the interpolation.
For a first implementation of such functionality it is perhaps best to assume that the parametrization (type and ranges) is the same for the vlps. I think that simplifies the QC and covers most of the use cases.
...in order to compare them. Use case mentioned from Troll. What do you think @lindjoha?
The text was updated successfully, but these errors were encountered: