always applying the BHP limit from WCONINJE.

This commit is contained in:
Kai Bao
2016-10-28 16:32:11 +02:00
parent c07878800f
commit eb6c8aa1dc
2 changed files with 8 additions and 10 deletions

View File

@@ -617,17 +617,15 @@ namespace Opm {
properties.dropInjectionControl(WellInjector::THP);
/*
What a mess; there is a sensible default BHP limit
defined, so the BHPLimit can be safely set
unconditionally - but should we make BHP control
available based on that default value - currently we
do not do that.
There is a sensible default BHP limit defined, so the BHPLimit can be
safely set unconditionally, and we make BHP limit as a constraint based
on that default value. It is not easy to infer from the manual, while the
current behavoir agrees with the behovir of Eclipse when BHPLimit is not
specified while employed during group control.
*/
properties.BHPLimit = record.getItem("BHP").getSIDouble(0);
if (!record.getItem("BHP").defaultApplied(0)) {
properties.addInjectionControl(WellInjector::BHP);
} else
properties.dropInjectionControl(WellInjector::BHP);
// BHP control should always be there.
properties.addInjectionControl(WellInjector::BHP);
if (well->isAvailableForGroupControl(currentStep))
properties.addInjectionControl(WellInjector::GRUP);

View File

@@ -5,7 +5,7 @@
{"name" : "CMODE" , "value_type" : "STRING" },
{"name" : "RATE" , "value_type" : "DOUBLE" , "dimension" : "ContextDependent"},
{"name" : "RESV" , "value_type" : "DOUBLE" , "dimension" : "ReservoirVolume/Time"},
{"name" : "BHP" , "value_type" : "DOUBLE" , "dimension" : "Pressure" , "default" : 6891},
{"name" : "BHP" , "value_type" : "DOUBLE" , "dimension" : "Pressure" , "default" : 6895},
{"name" : "THP" , "value_type" : "DOUBLE" , "dimension" : "Pressure"},
{"name" : "VFP_TABLE" , "value_type" : "INT" , "default" : 0},
{"name" : "VAPOIL_C" , "value_type" : "DOUBLE" , "default" : 0},