General

General

  1. All Categories
  2. General
  3. Why are some segments or entire surfaces absent in the binary interface force file intfor for *CONTACT_TIED?

Why are some segments or entire surfaces absent in the binary interface force file intfor for *CONTACT_TIED?

Tagged: , , , ,

    • March 17, 2023 at 8:59 am
      FAQFAQ
      Participant

      In MPP, unless the tied contact is made “groupable”, slave nodes are paired with master segments during decomposition, and the unnecessary master segment s are deleted from the contact definition. This makes it impossible to write all the original master surface data to the intfor file. The good news is you can make the tied contacts groupable by adding the following 2 lines to the input deck: *CONTROL_MPP_CONTACT_GROUPABLE 2

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.

© 2023 Copyright ANSYS, Inc. All rights reserved.