General

General

  1. All Categories
  2. Structures - General
  3. Why there is a bad display with /ESHAPE,1 command with nodes initially coincident and have different displacements ?

Why there is a bad display with /ESHAPE,1 command with nodes initially coincident and have different displacements ?

Tagged: 1, bad display, coincident nodes, ESHAPE
    • June 6, 2022 at 9:58 am
      FAQFAQ
      Participant

      This is a limitation of /ESHAPE and PowerGraphics. /ESHAPE,0.99 is the correct workaround. From /ESHAPE: When nodes are initially coincident and PowerGraphics is active, duplicate polygons are eliminated to conserve display time and disk space. The command may degrade the image if initially coincident nodes have different displacements. The tolerance for determining coincidence is 1E-9 times the model’s bounding box diagonal. Since the tolerance in 1e-9, you can shrink as little as /ESHAPE,0.99999999.

Featured Articles

Introducing Ansys Electronics Desktop on Ansys Cloud

The Watch & Learn video article provides an overview of cloud computing from Electronics Desktop and details the product licenses and subscriptions to ANSYS Cloud Service that are...

How to Create a Reflector for a Center High-Mounted Stop Lamp (CHMSL)

This video article demonstrates how to create a reflector for a center high-mounted stop lamp. Optical Part design in Ansys SPEOS enables the design and validation of multiple...

Introducing the GEKO Turbulence Model in Ansys Fluent

The GEKO (GEneralized K-Omega) turbulence model offers a flexible, robust, general-purpose approach to RANS turbulence modeling. Introducing 2 videos: Part 1 provides background information on the model and a...

Postprocessing on Ansys EnSight

This video demonstrates exporting data from Fluent in EnSight Case Gold format, and it reviews the basic postprocessing capabilities of EnSight.

© 2024 Copyright ANSYS, Inc. All rights reserved.