Skip to content

feature: propagate field attribute from input #4077

Open
npillardou wants to merge 6 commits into
developfrom
feature/npillardou/addFieldAttribute
Open

feature: propagate field attribute from input #4077
npillardou wants to merge 6 commits into
developfrom
feature/npillardou/addFieldAttribute

Conversation

@npillardou
Copy link
Copy Markdown
Contributor

This PR adds the potential opportunity to propagate the attribute field to the ouput pvd results.

By default, this option is ignored but optionnally added such as:

<VTK 
  name="vtkOutput"
  plotFileRoot="faultModel"
  fieldNames="{ attribute }" />

@npillardou npillardou added the type: feature New feature or request label Jun 5, 2026
@npillardou npillardou requested review from bd713 and jafranc as code owners June 5, 2026 14:50
@npillardou npillardou added ci: run CUDA builds Allows to triggers (costly) CUDA jobs flag: requires rebaseline Requires rebaseline branch in integratedTests ci: run integrated tests Allows to run the integrated tests in GEOS CI ci: run code coverage enables running of the code coverage CI jobs labels Jun 5, 2026
@rrsettgast
Copy link
Copy Markdown
Contributor

@npillardou Can you describe the benefit to this? You want to be able to visualize the "attribute" in the output? Is that "attribute" not already in the output? Things like initial stress/pore pressure?

@alexbenedicto
Copy link
Copy Markdown
Contributor

alexbenedicto commented Jun 8, 2026

@rrsettgast The goal is to not lose information that was given in input such as:

  • GLOBAL_IDS_CELLS and GLOBAL_IDS_POINTS.
  • any CellData/PointData array used to tag cells/points.

Currently, you cannot easily compare an input .vtu with the output .vtu given by GEOS. All the indexes of the cells and points are reconstructed by GEOS. There is no easy mapping solution other than using 3D coordinates.

EDIT1:

Ok I thought this would also work with any property given in fieldNames like fieldNames="{ my_property1, my_property2... }" but apparently it is not the case. Only works if your mesh has a property called "attribute" and you just want this one in output.

This would also be great to have for any property, not just "attribute".

EDIT2:

I cannot make it work when using "attribute". The "attribute" does not exist in the output.

@jafranc
Copy link
Copy Markdown
Contributor

jafranc commented Jun 8, 2026

Ok I thought this would also work with any property given in fieldNames like fieldNames="{ my_property1, my_property2... }" but apparently it is not the case. Only works if your mesh has a property called "attribute" and you just want this one in output.

This would also be great to have for any property, not just "attribute".

@alexbenedicto IIRC localToGlobal maps are in the Outputs, so mapping cells should be possible from here.
See GEOS-DEV/geosPythonPackages#193 for application

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci: run code coverage enables running of the code coverage CI jobs ci: run CUDA builds Allows to triggers (costly) CUDA jobs ci: run integrated tests Allows to run the integrated tests in GEOS CI flag: requires rebaseline Requires rebaseline branch in integratedTests type: feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants