Solid material fields missing in silo output

GEOS-DEV / GEOS

GEOS Simulation Framework

GNU Lesser General Public License v2.1

210 stars 84 forks source link

Solid material fields missing in silo output #1650

Open sytuannguyen opened 2 years ago

sytuannguyen commented 2 years ago

Describe the bug _Solid_MaterialFields is missing in Silo output while running poromechanics problems

To Reproduce Steps to reproduce the behavior: Re-run the poroelastic case defined by one of the following xmls

inputFile/multiphysics/PoroElastic_Mendel_FIM.xml
inputFile/multiphysics/PoroElastic_Terzaghi_FIM.xml Then verify that the _Solid_MaterialFields such as stress_11, stress_22 etc. are missing

Notes: This issue seems only happen to the poromechanics coupled solver. Indeed, it is not the case while running the solid mechanics examples. For example, the _Solid_MaterialFields appears while re-running the solid mechanics integrated test located at

inputFile/solidMechanics/SSLE-QS-beamBending.xml

jhuang2601 commented 2 years ago

@sytuannguyen How about other format, such as VTK or HDF5? The described issue has never been seen for the poromechanics wellbore problems.

sytuannguyen commented 2 years ago

@jhuang2601 Yeah this is the first time I see this issue happening. I guess it is linked to recent updates of the poromechanics solver.

jhuang2601 commented 2 years ago

I reran the tutorial example (inputFiles/poromechanics/PoroElasticWellbore_benchmark.xml) with the recent develop repo and observed the same issue.

jhuang2601 commented 2 years ago

@CusiniM @rrsettgast I just checked the VTK output and no issue with that format.

TotoGaz commented 1 year ago

What's our relation to Silo outputs? @rrsettgast @castelletto1 @white238 @herve-gross

castelletto1 commented 1 year ago

My preference is to support only VTK output and ditch Silo.

@cssherman could you remind me what Visit functionalities are missing in Paraview that justify supporting Silo in the long term?

cssherman commented 1 year ago

@castelletto1 - Here's an old thread on this: https://github.com/GEOSX/GEOSX/issues/1402

I'm working with vtk exclusively now myself, and it sounds like @povolny1 has most of his issues resolved.

castelletto1 commented 1 year ago

Based on #1402, I would say we can safely stop supporting Silo outputs.

TotoGaz commented 1 year ago

Let's have the discussion tomorrow in the infrastructure meeting?

paveltomin commented 1 year ago

any update?