|March 7, 2012, 14:19||
Navigating filetypes in v13
Join Date: Mar 2012
Posts: 6Rep Power: 6
I am having trouble with navigating around CFX with certain filetypes. I have learned autonomously through WB. I am simulating with a cluster that my peers are using with v12, while I am using v13. They upload simply a .def (and create a .pbs as instruction for the cluster).
I have been unable to export as .def as the Pre module on WB doesn't have this option. However, .def export is an option in the stand alone version. Getting my information to that version is the problem. I have exported my mesh (from the WB mesher) in every allowed format (.meshdata, .msh, .cgns, .poly, .prj, .tgf), and there always seems to be 'version conflicts' when imported into standalone CFX.
Only the .msh imports, but without the same location information. All I can export from the WB Pre is a .ccl. When I import this into standalone Pre, it can't associated with existing geometries (for my boundaries). In fact, the imported .msh has no boundaries, and I cannot make them, I only have the 'solidbody' domain.
Why is Ansys so inconsistent when interfacing with itself? I couldn't imagine any program could be this difficult by design. All I need is this .def file. Any thoughts?
Last edited by Curran919; March 7, 2012 at 21:54.
|Thread||Thread Starter||Forum||Replies||Last Post|
|Patching Second Phase Region in Fluent V13 VOF Model||sda||FLUENT||15||February 15, 2017 07:44|
|[ANSYS Meshing] Fine meshing in ANSYS Meshing v13||shk12345||ANSYS Meshing & Geometry||1||December 1, 2011 11:41|
|FYI: Mixture Absorption Coefficient in V13||ronaldalau||FLUENT||0||December 1, 2011 10:23|
|Ansys V13 License Server problem||Gustavo||ANSYS||3||May 14, 2011 21:11|
|UDF problem when using FLUENT v13||vboris||FLUENT||1||February 21, 2011 13:35|