Ansys Geometry Interface

[Adah Orhenkowski]

TheCAESES ACT app is an ANSYS geometry interface by FRIENDSHIP SYSTEMS that allows CFD engineers to automate the entire geometry generation process, for the purpose of running shape optimization and design studies.

With the ACT app, new design variants are created with a single click in the background of the ANSYS GUI, and the new geometry is transferred to the Workbench without any manual user interaction. These externally created geometry candidates can be automatically meshed and analyzed with all the ANSYS tools, which is the prerequisite for CFD-driven studies.

We prepared a short video that demonstrates how easy it is to connect CAESES to the ANSYS Workbench. As an example, a parametric pump impeller is given in CAESES. The geometry setup contains a set of design variables that controls the shape modifications. A dedicated TurboGrid feature of CAESES then exports the geometry using the TurboGrid format. By running CAESES in batch mode, the entire geometry generation is automated without any scripting efforts by the ANSYS user.

Compared to the use of traditional CAD tools, the main benefits of this CAESES-ANSYS geometry interface are the robust variant generation (no failed designs during the process) and a parameter-reduced, highly efficient CAD model (less computations). Since CAESES is a generalized CAD solution for shape optimization with simulation tools, any application from any industry can be considered. In particular, CAESES focuses on complex free-form shapes and their clever parameterization. The ACT app makes sure that the Named Selections of ANSYS are fixed and do not change, to be able to record and replay everything during automated studies.

Welcome to the PyAnsys metapackage repository. The pyansys metapackageprovides a single package of collected PyAnsys packages that ensures compatibilityof these packages amongst themselves and the Ansys product release that they are linked to.

If you lack an internet connection on your installation machine, the recommended way of installingthe pyansys metapackage is downloading the wheelhouse archive from theReleases Page for your corresponding machine architecture.

Each wheelhouse archive contains all the Python wheels necessary to install the pyansys metapackage fromscratch on Windows, Linux, and MacOS from Python 3.9 to 3.11. You can install this on an isolated system witha fresh Python installation or on a virtual environment.

PyAnsys libraries make no commercial claim over Ansys whatsoever.These libraries extend the functionality of Ansys products byadding Python interfaces to legally obtained software productswithout changing the core behaviors or licenses of the originalsoftware.

I would like to ask you about the possibilities to have a live interface between the model from KARAMBA 3D in Grasshopper and Dlubal-RFEM. With live Interface, I meant that when I change any parameter in Grasshopper this will change same time in RFEM. I do not want to bake the model every time and import it in RFEM.

I know that it is possible to have this live Interface only between the geometry from Grasshopper and RFEM, but I want this between the model in KARAMBA3D and RFEM, so that I do not need to define the material, cross-section, Loads, and boundary conditions again. In this way I can use RFEM to control the results in KARAMBA and apply a structural analysis after the Eurocode.

we currently do not have any live interface with RFEM and Karamba. The only method is to use the export component. However Dlubal did just release a plugin which allows interface between Grasshopper and RFEM so you could look into this.

Hello Mathew,

Thanks for your quick respond. It is a pity that there is no live Interface between Karamba3D and RFEM. I found out how to have interface between Grasshopper and RFEM.

SO could you please demonstrate exactly how to use the component Export Model to DStV(Karamba3D). The best way is to upload an example from Karamba3D itself with this component?

Many thanks in advance for your help.

Cheers,

Ihab

you simply need to export it as a .stp file to the RSTAB/RFEM version you are using. Then upon import you should select DSTV format in RFEM. Unfortunately there is no method to import shells from Karamba at the moment.

INTER202 is a 2-D 4-node linear interfaceelement used for 2-D structural assembly modeling. When used with2-D linear structural elements (such as PLANE182), INTER202 simulates the interface surfacesand the subsequent delamination process, where the separation is representedby an increasing displacement between nodes, within the interfaceelement itself, that are initially coincident. The element can beused as either a plane element (plane stress or plane strain) or asan axisymmetric element. It is defined by four nodes having two degreesof freedom at each node: translations in the nodal x and y directions.

The element geometry, node locations, connectivity, and thenodal coordinate system are shown in Figure 202.1: INTER202 Geometry. The element geometry is defined by 4 nodes, which form bottomand top lines of the element. The bottom line is defined by nodesI, J; and the top line is defined by nodes K, L. The element connectivityis defined as I, J, K, L. This element has 2 integration points. TheGauss integration scheme is used for the numerical integration.

INTER202 is used to simulate interfacialdecohesion with the cohesive zone model along an interface defined by this element.At the outset of the simulation, nodes I,L and J,K are coincident,both with each other and with the corresponding nodes in the adjacentstructural elements. The subsequent separation of the adjacent elements(usually defined contiguously as components) is represented by anincreasing displacement between the nodes within this element.

INTER202 can also be used to simulateinterfacial delamination of laminate composite and general crack growthwith VCCT. For more information, see VCCT-Based Crack-Growth Simulation in the Mechanical APDL Fracture Analysis Guide.

Temperatures may be input as element body loads at the nodes.The node I temperature T(I), defaults to TUNIF. If all other temperaturesare unspecified, they default to T(I). For any other input pattern,unspecified temperatures default to TUNIF.

The output directions for element items are parallel to thelocal element coordinate system based on the element midplane, asillustrated in Figure 202.2: INTER202 Stress Output. See Cohesive Zone Model in the Mechanical APDL Theory Reference for details.

A colon (:) in theName column indicates that the item can be accessed bythe Component Name method (ETABLE, ESOL). The O column indicates the availability of the items in the file Jobname.OUT. The R column indicates the availability ofthe items in the results file.

Parameters for geometry generation, meshing, and simulation can be prepared within CFturbo. Automated meshing and simulation in TCFD becomes possible. To evaluate results, special expressions are generated to perform turbomachinery post-processing.

The STEP-based interface to STAR-CCM + enables high-quality geometry transfer, whereas all domains and individual part names are transferred to the model tree. Thus, automated design exploration is easy.

As far as I know, for multi-physics simulations often software packages like Ansys or COMSOL are used. Can Julia also be used for this kind of simulations?

Or can Julia be used together with these commercial SW packages?

There is FMI support in Julia, not limited to JuliaSim: GitHub - ThummeTo/FMI.jl: FMI.jl is a free-to-use software library for the Julia programming language which integrates FMI (fmi-standard.org): load or create, parameterize, differentiate and simulate FMUs seamlessly inside the Julia programming language!

But not yet complete, for example export of FMIs for cosimulation is still missing: Support export of FMUs for cosimulation Issue #10 ThummeTo/FMIExport.jl GitHub

Yes, you can use Gridap for CFD if you are happy to use finite elements for this. You can also couple fluid with other physics as long as they are also modeled with PDEs. You can have both surface and volume couplings.

Activities regarding multi-physics simulations in Trixi.jl are to increase soon, since we have secured a research grant on bulk and interface coupling with Trixi.jl. The first PhD students and postdocs are starting in October and November, so we expect to start seeing feature updates in the next couple of months. Feel free to reach out to me personally if you have a specific question and whether it is (currently) viable to do in Trixi.

openfoam, code-saturne, and SU2 are Open-Source CFD Codes. but SU2 has a python wrapper.

so, instead of writing all code in Julia, it is better to write a wrapper for SU2 in Julia for immediate access to CFD. Julia language was also developed for numerical methods but no CFD toolbox is available yet.

Hi @fverdugo

Gridap.jl is awesome.

I hope that it can support some predefined models like in COMSOL.

Then, for ordinary usage, people can just choose a model and define the geometry, boundary conditions and meshes without touching the mathematical description on the model.

Is this out of the scope of Gridap.jl?

Salome-Meca using Salome as an open source preprocessor and Code Aster as the FEM engine, and integrating nicely with Code Saturn is one of the more polished open source projects for FEM & CFD for multi-physics and fluid structure interaction.

They use compiled Fortran Code for the number crunching with the glue code being Python. It would be neat to replace the Python part with Julia, which would then open the door to developing Julia modules to extend the capabilities and solving their two language problems.

It would be good that we just transform the examples in the tutorial to models, which can be easily included by users, making the tutorial become a high-level package based on Gridap.jl.

By adding some physical description to those models, we may deliver something that is comparable to COMSOL for ordinary usage.

3a8082e126