Divergence in execution path upon restart for single phase thermal well simulation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 287
- Forks
- 109
- Avg merge
- 4d 41m
- Merged PRs (30d)
- 5
Description
Describe the bug
When running a single-phase thermal simulation with a well, running a restart from a generated restart file (cycle 10) causes the simulation to follow a different execution path/trajectory compared to the continuous base case.
To Reproduce
Steps to reproduce the behavior:
-
Run the base single-phase thermal simulation to generate a restart file at cycle 10:
geosx -i thermal_compressible_single_phase_wells_1d.xml -
Run the simulation using the generated restart file:
geosx -i thermal_compressible_single_phase_wells_1d.xml -r thermal_compressible_single_phase_wells_1d_restart_000000010 -
Compare the results/log of the restarted run with the continuous base case run.
-
See issue: The outputs/paths diverge after the restart point instead of matching the base case exactly.
Expected behavior
The simulation restarted from cycle 10 should follow the same computational path and yield identical results as the uninterrupted base case run.
Platform (please complete the following information):
-
Compiler: gcc 12.2.0
-
GEOS Version: 1.1.0 (develop, sha1: 0139435c82)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running geosx with thermal_compressible_single_phase_wells_1d.xml, first without and then with the cycle-10 restart file, using the supplied data_files.zip if needed. Compare the restarted run's outputs and logs with the uninterrupted run; done means both follow the same execution path and produce identical results after the restart point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- hpc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100