[Curran919]

-SOLVED- ...somehow

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?

Thanks,
Curran