[PROGRAM PLAN]: The high level development plan for GEOS

[rrsettgast]

Description

This "issue" will track an evolving program plan for the development goals of GEOS from a high level perspective. Major projects will be listed with high level summaries, and their associated EPIC will be linked. Detailed discussions about projects should not be present on this issue, but rather confined to the associated project EPIC .

Development thrusts

• Compositional flow / Poromechanics
  • [EPIC] PVT modeling #2465
• Thermal (Coupling thermal into flow and mechanics)
• Geochemistry (reactive transport)
• Faults and Fracturing ( Fractures/Faults, Contact Mechanics, Hydraulic Fracturing )
  • [THEME] Faults & Fractures  #2361
  • [THEME] Hydraulic fracturing  #2381
• Geophysics - high order spectral finite element
• Constitutive Modeling
  • [THEME] Constitutive Models #2534
• Linear/Nonlinear solver strategies
• Matrix-Free
• Infrastructure (generality, efficiency, re-design)
  • [EPIC]: Reduce Memory Footprint #2338
• Workflow (pygeos, preprocessing, mesh reading, plotting, time histories )
  • [EPIC] Outputs in GEOS  #2356
• Target platforms, testing, benchmarks, deployment
  • [EPIC]: Transition to spack. Deprecate thirdPartyLibs #1801
• Documentation - user manual, tutorials, developer guide, doxygen.

[joshua-white]

Looks good. My only comments:

• Geophysics might grow to include other things, so perhaps just delete the "high order SEM" tag?
• Do you want to merge Matrix-Free under Linear / Nonlinear Solver Strategies, or keep on its own?

[rrsettgast]

Looks good. My only comments:

• Geophysics might grow to include other things, so perhaps just delete the "high order SEM" tag?

I think "high order SEM" is the first thing on this.

• Do you want to merge Matrix-Free under Linear / Nonlinear Solver Strategies, or keep on its own?

I want to keep them separate since they are completely separate paths in the code.

[herve-gross]

I have aligned the Slack channels against this plan.