Kai Bao

jenkins build this opm-simulators=6097 failure_report please

FYI, https://ci.opm-project.org/job/opm-common-PR-builder/8291/testReport/junit/(root)/mpi/compareECLFiles_flow_02_WGRUPCON/ does not run through.

Is this during well potential calculation with 1 atm bhp limit? And also, do we know which OPM code trigger the error message? ```c++ /usr/include/c++/12/bits/stl_algo.h:3623: constexpr const _Tp& std::clamp(const _Tp&,...

Thanks for @akva2 pointing out. On my computer, it only triggers if we use the old 16-day time step limits and it runs through with default setting of the master...

I am testing the master branch, it runs through the 9_3D_GINJ_GAS_MAX_EXPORT_MSW.DATA without problem. It is still running the proved gcc12 data file, it was reported problem at report step 24...

We have a negative `rs` here and the simulation crashes with `9_3D_GINJ_GAS_MAX_EXPORT_MSW` ```c++ template std::pair dissolvedVaporisedRatio(const int io, const int ig, const Scalar rs, const Scalar rv, const Rates& surface_rates)...

And it happens with 1 bar bhp constraint,  and the pressure drop between the segments for this well looks weird, while in theory is possible but most likely problematic....

The weird pressure drop is from an incomplete initialization of the well states after changing to 1 bar bhp.

And the negative value for rsMax simply from the extrapolation at the lower pressure end. The PVTO table has a lower pressure end at 50 bar.

PVTG looks like patched til 1 bar, probably with https://github.com/OPM/opm-common/pull/3779. Maybe we should do it for the keyword PVTO?