mirror of
https://github.com/OPM/ResInsight.git
synced 2026-10-27 15:41:00 -05:00
The well list driving schedule generation originates from a std::set<RimWellPath*>, so it was ordered by pointer address and the per-well keyword records (WELSPECS, COMPDAT, COMPLUMP, MSW keywords, well control) came out in a non-deterministic order that only looked sorted by coincidence. Sort the well list once by the deck export name in generateSchedule, so every per-well keyword is emitted in a stable, well-name-sorted order, matching the convention already used by the file-based completion export. Schedule-level keywords (GRUPTREE, RPTRST, TUNING) are left untouched.
ResInsight Processing Server - rips
A Python interface for the ResInsight visualization and post-processing suite for Reservoir Simulations