Problems with Import/Export from Discovery to Fluent #1070
-
Hello PyPrimeMesh Developers, we're using the example provided here: to automate our DCB meshing procedure. We're facing some issues with the import and export during this script. Right now, we're using So for now, we need an own fluent preprocessing program, to rename every part and to resize the model. This takes a lot of time, so I would like to get rid of it. An alternative might be the import with
And then continue with the step of the example, but then, the export of the cas file fails. I am looking forward to your answer. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
If you are importing to enable shared topology and for your model to be connected you will need to use the WORKBENCH cad reader route and import as a single part the connected bodies. Volumes can only be connected if they are all in the same part. If you had shared topology and are not importing with Workbench then the CAD bodies will not be connected. It is likely why you are seeing issues with the export later. CAD bodies that are adjacent and not connected should be kept in separate parts. If you have not specified any named selections on the CAD then the only label you will see will be a default label generated for all volumes coming through the Workbench reader route. I am not clear what is meant when you state it is causing issue with the part names as this should have no impact on the parts. The volume zones will be named as per the CAD body names. At 25R2 there are additional APIs that will allow you to obtain topo volumes by volume zone name and label them if needed but for meshing operations you should just be able to scope to these volume zones as you need to. I would recommend the following:
This should fix the issues you are seeing. Thanks (Cc @prajaktmahajan ) |
Beta Was this translation helpful? Give feedback.
-
create_zones_from_labels only works on face zones at present. Starting in 25R2 and 0.9.0 you will be able to do the following for volumes:
Until then you would need to manage these with zone names. Thanks |
Beta Was this translation helpful? Give feedback.
Hi,
@waltersma proposed to me the solution to leave out
part.remove_labels_from_topo_entities
. And instead ofmesh_util.create_zones_from_labels()
I should usemesh_util.create_zones_from_labels("* !__*")
And I stick with
CadReaderRoute.WORKBENCH
for the CAD import, because the Discovery route will destroy my shared topology.This solved the problem for me.