Closed sveinung-r closed 6 years ago
Thanks. I have tested this and can verify that it fixes my issue i.e #236.
WEFAC is not implemented correctly. I can communicate the issue directly.
WEFAC is not implemented correctly. I can communicate the issue directly.
Could you enlighten me on the issue as well?
Sure, but I am not sure I have time before the weekend.
@alfbr:
WEFAC is not implemented correctly. I can communicate the issue directly.
Is this a review comment for the current PR?
The WEFAC
functionality is quite weird - it would be beneficial (also for the reviewer ...) if you could explain the principles in a comment.
My two cents, the well rate is an instantaneous rate, so WEFAC will not impact the RATE. WEFAC is to handle the downtime, basically it means the Well is not operating full time, maybe 80% of the time (20% downtime, WEFAC=0.8) .
I do not see anything obviously wrong in the description in the PR.
The well and the group efficiency factors, as @GitPaean describes, provide means do incorporate downtime/maintenance time for wells, without changing the rates explicitly.
It will not impact the well rate itself, but is rather applied for accumulated values. The WEFAC can be considered to shut and open the well for short intervals within the same timestep, and the well is therefore solved at full speed. When WEFAC is set to 0.8 for all wells in a group, it is considered that every well is flowing at full speed, but only 80% of them are flowing at any given time. The rate of a group therefore takes into account well efficiency factors.
Groups are treated similarly as wells. The group's GEFAC is not applied for rates, only for accumulated volumes. When GEFAC is set to 0.8 for a group, it is considered that all wells are taken down simultaneously, and GEFAC is therefore not applied to the group's rate. However, any efficiency factors applied to the group's wells or sub-groups must be included.
Regions and fields will have the well and group efficiency applied for both rates and accumulated values.
Thanks for the explanation @lars-petter-hauge!
@lars-petter-hauge : Thank you for a good explanation; since this feature is quite weird I would actually like a comment in the code - essentially an excerpt of what you have written here.
Some minoor comments - then this is ready to be merged (when rebased!)
jenkins build this please
jenkins build this update_data please
jenkins build this opm-data=308 please
Efficiency factors are multiplied when specified at multiple levels of the well/group hierarchy.
The factors are included as follows:
Ref #236