Hello everyone,
I would like to confirm whether the OSRT method is still supported in simulations of supercritical CO₂ (scCO₂) reactive transport.
When I modified the GIRT method to OSRT in the case5 (
Modeling supercritical co2 flow and mineralization in reactive host rocks with pflotran v7.0 ) of the code, an error occurred. I also tested other custom cases of my own, and all encountered the same error (see details below). My PETSc version is 3.21.5, and PFLOTRAN version is 7.0.
Is there any special configuration required for using the OSRT method?
== SCO2 FLOW ===================================================================
0 2r: 1.37E+01 2x: 0.00E+00 2u: 0.00E+00 ir: 3.96E+00 iu: 0.00E+00 rsn: 0
1 2r: 9.25E-04 2x: 4.12E+08 2u: 8.17E+04 ir: 3.49E-04 iu: 4.12E+04 rsn: 0
2 2r: 1.27E-05 2x: 4.12E+08 2u: 9.33E-01 ir: 5.00E-06 iu: 4.85E-01 rsn: 999
Step 1 Time= 3.17098E-08 Dt= 3.17098E-08 [y] conv_reason: 999
newton = 2 [ 2] linear = 4 [ 4] cuts = 0 [ 0]
--> SNES Linear/Non-Linear Iterations = 4 / 2
--> SNES Residual: 0.127004E-04 0.793777E-08 0.500330E-05
--> max chng: dpl= 4.1178E+04 dpg= 4.1178E+04 dpco2= 4.0795E+04
dxco2= 1.1750E-06 dxs= 0.0000E+00 dt= 0.0000E+00 dsg=
== OPER.-SPLIT REACTIVE TRANSPORT ==============================================
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[0]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind and https://petsc.org/release/faq/
[0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run
[0]PETSC ERROR: to get more information on the crash.
[0]PETSC ERROR: Run with -malloc_debug to check if memory corruption is causing the crash.
[16]PETSC ERROR: ------------------------------------------------------------------------
[16]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[16]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[16]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind and https://petsc.org/release/faq/
[16]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run
[16]PETSC ERROR: to get more information on the crash.
[16]PETSC ERROR: Run with -malloc_debug to check if memory corruption is causing the crash.
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 16 in communicator MPI_COMM_WORLD
with errorcode 59 .…………