Importing Problem in Acusolve.

Sankarsan

Hello experts,

 

I am trying to import a parasolid file, to Acusolve. The parasolid file was generated after deleting the solid and enclosing the fluid volume in Hypermesh. 

 

But, while importing to acusolve... It is showing error as  attached picture..

 

Kindly tell me, why it is showing error and how to get rid of it.

<?xml version="1.0" encoding="UTF-8"?>

ydigit

HyperMesh Parasolid export is not always compatible with AcuConsole.

 

Have you tried to setup the case in HyperMesh. With HyperMesh 2019 or 2019.1 you should be able to do most setups in HyperMesh. The latest release also has new tutorials based on HyperMesh interface.

 

Junta_20361

Hi,

You can try using HyperMesh 2019 with AcuSolve user profile. It supported a lot of functions for AcuSolve and it much easier to use than AcuConsole.

Also, in 2019.1 version, Altair released HyperWorks CFD X - very good software. It has GUI like Inspire platform and the way to manage data similar like AcuConsole (use surface group, not like traditional HyperMesh using component).

 

<?xml version="1.0" encoding="UTF-8"?>

MADA

Hello Users, 

I am trying to import my HyperMesh model to Acuconsole. After opening the exported mesh in Acuconsole, All of the boundary surfaces and Control Volume mesh has been separated by the element (Pyr5-tet4-wedge6). While exporting from Hypermesh, I have disable the option to create the exterior faces. Is there any way to avoid element separation?

acupro

Internally, the sets in AcuConsole are all topologically separated by default - quad vs tri as well as parent element set.  You can still place different 'topology' entities into the same set, but they will again be separated when writing the input file.  AcuSolve now does support mixed-topology mesh sets, but I believe AcuConsole does not.  So be careful.

 

MADA

Altair Forum User said:

Internally, the sets in AcuConsole are all topologically separated by default - quad vs tri as well as parent element set.  You can still place different 'topology' entities into the same set, but they will again be separated when writing the input file.  AcuSolve now does support mixed-topology mesh sets, but I believe AcuConsole does not.  So be careful.

 

Thanks for your info. 

If Acuconsole does not support the mixed-topology mesh set, which strategy needs to be taken apart redoing the mesh?

acupro

If you've already meshed the model in HyperMesh, you can continue setting up the model there, as I believe the up-to-date releases of HyperMesh support and write out the input files taking into account the mixed topologies.  Is there a reason you wish to bring the mesh to AcuConsole rather than setting up the model in HyperMesh?

 

Other than hand-editing the model to incorporate the new commands that would take into account mixed topologies/elements, you could also convert all elements to tets.  In AcuConsole, that would be Mesh Op > Mesh to Tet.  That leaves you with all tets and tris.

MADA

The main reason of exporting the mesh to Acuconsole is to use the integrated/element  BC options available under advanced BC .

acupro

I do see Integrated BC available for Inflow / Outflow SBC types.  But I can't seem to get Element BC anywhere.  (This is with HM 2019.1)  What specifically do you need through Integrated and/or Element BCs?  Have you contacted Altair Support about this yet?  They may be able to give better answers regarding what's available in HM.