Don't Write RSM File for Substeps
If the last report step happens to be split into multiple substeps (e.g., convergence problems or TUNING settings &c), then we will write the RSM file for each substep which will slow down the process. This commit explicitly ensures that we don't output the RSM file unless it is the last substep of the final report step.
This commit is contained in:
parent
403fd09e69
commit
50e4f9439b
@ -217,7 +217,7 @@ void EclipseIO::writeTimeStep(const Action::State& action_state,
|
|||||||
|
|
||||||
bool final_step { report_step == static_cast<int>(this->impl->schedule.size()) - 1 };
|
bool final_step { report_step == static_cast<int>(this->impl->schedule.size()) - 1 };
|
||||||
|
|
||||||
if (final_step && this->impl->summaryConfig.createRunSummary()) {
|
if (final_step && !isSubstep && this->impl->summaryConfig.createRunSummary()) {
|
||||||
Opm::filesystem::path outputDir { this->impl->outputDir } ;
|
Opm::filesystem::path outputDir { this->impl->outputDir } ;
|
||||||
Opm::filesystem::path outputFile { outputDir / this->impl->baseName } ;
|
Opm::filesystem::path outputFile { outputDir / this->impl->baseName } ;
|
||||||
EclIO::ESmry(outputFile).write_rsm_file();
|
EclIO::ESmry(outputFile).write_rsm_file();
|
||||||
|
Loading…
Reference in New Issue
Block a user