ANSYS to ASTER model and boudary condition translator

Nikon6260 · 2014-08-21 10:11:20

Hello everybody.

I strongly need a ANSYS to ASTER model and boundary condition translator. Anybody has it?

Thaks

Denis

Last edited by Nikon6260 (2014-08-21 19:31:37)

reiteres · 2014-08-22 09:52:41

Hi!

You won't will have luck with that. If you have FEMAP there is the possibility for an Code_Aster <-> FEMAP translator http://nesys.pagesperso-orange.fr/Aster.htm
FEMAP can then produce/read ansys files

Jacopo · 2014-08-22 13:54:20

Hi Denis,
there is a plug-in in Hypermesh too.
Look this:

http://www.altairuniversity.com/wp-cont … 062012.pdf

Best Regards
Jacopo

Nikon6260 · 2014-08-23 05:19:55

Thanks for the information.
But I not have FEMAP or Hypermesh.
I'll write a macro on APDL.

mcoyne · 2014-08-23 12:57:03

Some time back i wrote a similar translator for Abaqus to Code Aster which you may be able to use/tweek directly or as a "go by" . Note Ansys will output/translate to Abaqus in their "Work Bench" although be it abit clumsy in my opinion. I used a Translator Construction Tool kit called http://eli-project.sourceforge.net/ to generate the translator. My intent was to translate both the bulk data and get the loads and boundary conditions translated as well a template for the complete comm file. Attached is the complete source spec file the format of which being a sort of hand written "tar" file. It is a flat text file including a some what terse instructions on how to generate the executable from this input spec. Note i made some use of in memory hashing "uthash" as a linked lists were to slow with the size of the input decks being used "acouple of million dof + ". The templating for the Pattern-Based Text Generator PTG i mentioned is toward the bottom of the file, you may want to adjust for your needs or taste. It is a fairly straight forward Lexial analysis is toward the top, the Syntax and Parse tree and rules are in the middle , and the unparser "ptg" is toward the bottom of the file.

This was a work in progress up to about a year and half ago , I know of some problems with the generated comm file with respect to the current code aster. Originally i decided i would make a copy of the mesh when i needed to "say add mid-face nodes" on shells etc "CREA_MAILLAGE" but the syntax has changed since so that part need to be fixed with eficas as well as some of the options for solver call outs i know that are dated. I also didn't format the python tabs very well in my output as i always used eficas to view/adjust the run and it reformatted it for me. One other thing of note is naming conventions aster as a short, length limited , python centric naming criteria where the Abaqus names from the ".inp" files were not so limited. So created a hashed name translation for longer names coming from abaqus which doesnt help with readability but it was all i could come up with at the time.

Attachments:
abq2aster.fw, Size: 194.22 KiB, Downloads: 365

keeswouters · 2014-08-24 14:51:50

Hoi Nikon

you can try Femap for 45 days now.
http://www.plm.automation.siemens.com/n … liia400030
in dutch ;-), but German is available as well (and probably French and if you are in luck, english).

Nikon6260 · 2014-08-24 15:14:39

keeswouters

It's just FEMAP
For translation ANSYS <-> ASTER need a special plugin from Nesys

Nikon6260 · 2014-09-13 18:39:21

Hello!

I wrote a ANSYS to ASTER converter.

It's alpha version of macros.

Macro in the attached file.

Macro, not all can.

Close-up still has some limitations.

Limitations: -
- Export mesh only to *.msh-file;
- Only the static linear analysis and only the elastic properties of materials;
- Only 3D models boundary conditions (can not create thickness for shell elements, the cross sections for the beam elements and the mass for mass elements), but can write mesh of any dimension (1D, 2D, 3D);
- Can not create a contact interaction.

Using a macro:
- Copy the macro to the working ANSYS directory;
- Enter text to command line: ans2ast, ARG1, ARG2
where:
ARG1 = 0 - EXPORT MESH ONLY - DEFAULT (ONLY *.MSH - FILE)
ARG1 = 1 - EXPORT MESH AND BOUNDARY CONDITIONS (LOADS, THEMPERATURES, DISPACEMENTS,... - *.COMM - FILE)

OPTION ARG2 is only available when ARG1 = 1
ARG2 = 0 - do not export the COMPONENTS NAMES - DEFAULT
ARG2 = 1 - EXPORT COMPONENTS NAMES

Some of the comments in the macro to the Russian language

Maybe someone needs.
I will be glad vyshim comments and observations.

Denis

Last edited by Nikon6260 (2014-09-13 18:49:44)

Attachments:
ANS2AST.MAC, Size: 33.31 KiB, Downloads: 424

#1 2014-08-21 10:11:20

ANSYS to ASTER model and boudary condition translator

#2 2014-08-22 09:52:41

Re: ANSYS to ASTER model and boudary condition translator

#3 2014-08-22 13:54:20

Re: ANSYS to ASTER model and boudary condition translator

#4 2014-08-23 05:19:55

Re: ANSYS to ASTER model and boudary condition translator

#5 2014-08-23 12:57:03

Re: ANSYS to ASTER model and boudary condition translator

#6 2014-08-24 14:51:50

Re: ANSYS to ASTER model and boudary condition translator

#7 2014-08-24 15:14:39

Re: ANSYS to ASTER model and boudary condition translator

#8 2014-09-13 18:39:21

Re: ANSYS to ASTER model and boudary condition translator

Board footer