Skip to content

Tutorial Example for CO2 injection where the plume is different between the tutorial and the files to be loaded #3660

@vqueulain

Description

@vqueulain

Describe the bug
I rerun tutorial example for CO2 Injection

First problem: The co2flash.txt file created manually with the data in the tutorial is not the correct one. This file generates a bug. The correct one is at the same level as the 2 XML files in the inputFiles/compositionalMultiphaseWell/ directory.

Image

Second problem: The plume generated is not the same between the tutorial and the files to be loaded
See the difference in the picture below:

Image

To Reproduce
Go to the CO2 injection case in the documentation
Download the 2 files indicated at the top of the tutorial:
inputFiles/compositionalMultiphaseWell/simpleCo2InjTutorial_base.xml
inputFiles/compositionalMultiphaseWell/simpleCo2InjTutorial_smoke.xml
And launch the simulation with the latest version of GEOS

Expected behavior
We do not know the desired behavior because there are 2 possibilities. But we ask ourselves the following questions.
Where does the change in plume come from?
Which is the best rendering the one from the tutorial or the one we get now?
What do we do?

  • Update of the documentation?
    * Update images to match uploaded files?
    * Or update files to find previous images?

  • Why is this not detected by the regression tests? What checks are being made? Should the tests be updated?

Choice 1: Update of the XML content to find previous images
-> Can be made by TTE US team
Choice 2: Update of the co2flash.txt content and update of the picture in the documentation
-> Can be made by TTE Pau team

Platform (please complete the following information):

  • Machine: Pangea4
  • Compiler: gcc 12.2.1
  • GEOS Version: e09f499

Metadata

Metadata

Assignees

Labels

type: bugSomething isn't workingtype: newA new issue has been created and requires attention

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions