Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gmsh gmsh
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 308
    • Issues 308
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gmsh
  • gmshgmsh
  • Issues
  • #175
Closed
Open
Created Mar 23, 2017 by Christophe Geuzaine@geuzaineOwner

"Adapt Visualization Grid" hides complete result of med library result

I’m loading a file in gmsh which was created by code_aster (a “med” format). It is easy to visualize the results on second order displacements:

  1. Switching on “Adapt visualization grid”
  2. Maximum recursion level = “1”
  3. Target visualization error = “-0.0001”

The gmsh debug info about this field is

Info    : Reading 2-component field <<&RESUR1_DEPL>>
Debug   : MED: eletyp=0 entity=3 (0:cell, 3:node, 4:elenode) ngauss=1 localizationName= profileName= -- stepDataType=1

However, when visualizing another field (here a nodal stress field"), pressing the "Adapt visualization grid" button will hide the entire result!. I found no options for "recursion level" or "target visualization error" which allows me to restore the result.

For example a result from a plain strain analysis:

Info    : Reading 4-component field <<&RESUR1_SIGM_NOEU>>
Debug   : MED: eletyp=0 entity=3 (0:cell, 3:node, 4:elenode) ngauss=1 localizationName= profileName= -- stepDataType=1

I'm attaching the file which contains both fields in order to let you reproduce this. The best way to see it is when using "Numerical Values" as "Intervals Type" and switching on the nodes "Mesh.Nodes=1". -Sebastian

Assignee
Assign to
Time tracking