recording the report step that WTEST keyword is specified

so we can easily tell when a new WTEST keyword joins.

When a new WTEST keyword, we will reset the counting of the num_attempt
and maximum number of attempts for the associated well.
This commit is contained in:
Kai Bao
2019-06-26 14:48:46 +02:00
parent 8dbb8d70fc
commit 11bc26d28d
6 changed files with 74 additions and 24 deletions

View File

@@ -42,11 +42,15 @@ public:
double test_interval;
int num_test;
double startup_time;
// the related WTEST keywords is entered and will begin
// taking effects since this report step
int begin_report_step;
};
WellTestConfig();
void add_well(const std::string& well, Reason reason, double test_interval, int num_test, double startup_time);
void add_well(const std::string& well, const std::string& reasons, double test_interval, int num_test, double startup_time);
void add_well(const std::string& well, Reason reason, double test_interval, int num_test, double startup_time, int current_step);
void add_well(const std::string& well, const std::string& reasons, double test_interval,
int num_test, double startup_time, int current_step);
void drop_well(const std::string& well);
bool has(const std::string& well) const;
bool has(const std::string& well, Reason reason) const;

View File

@@ -48,6 +48,11 @@ public:
// or the time that the well is closed if not test has not been performed after
double last_test;
int num_attempt;
// if there is a WTEST setup for well testing,
// it will be the report step that WTEST is specified.
// if no, it is -1, which indicates we do not know the associated WTEST yet,
// or there is not associated WTEST request
int wtest_report_step;
};
@@ -113,6 +118,8 @@ private:
WTestWell* getWell(const std::string& well_name, WellTestConfig::Reason reason);
void updateForNewWTEST(const WellTestConfig& config);
};