|
[Sponsors] |
December 4, 2017, 02:35 |
Import Geometry :: Naming Convention
|
#1 |
Member
Peter
Join Date: Sep 2011
Location: Germany
Posts: 39
Rep Power: 14 |
Hey Guys,
I am planning to script a meshing process via Glyph. However when I import the geometry with the native format (UG NX - .prt file) I got a wild mix of different names (LineXX, stat03_lineX [where "stat03" is my file name] and LineXX_0). Even with a (non-preferred) native format (ie iges) the same problem occurs. This will make the scripting procedure quite complex. Is there any way to control the names or a preferred import method? Thanks for your help. |
|
December 5, 2017, 11:29 |
|
#2 |
Senior Member
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 14 |
When available, Pointwise will use the names provided in the CAD file.
When a name is not provided, Pointwise will assign a default name along the lines of "basename-n" where basename is the entity type and n is a numeric suffix that makes the name unique. For example, con-1, dom-1, blk-1, plane-1, etc. From looking at the names in the attached images, I deduce that the names came from the CAD file. Probably the default names assigned by UG/NX. I do not know much about UG/NX. However, from working with others that use UG/NX, I know that there is a way for you to assign names to entities and have these names import into Pointwise. I suggest that you experiment. If you find a name NOT being imported and used by Pointwise, please post a (preferably small) example file so I can take a look. Also, be sure to look at hidden entities (View, Show Hidden). Sometimes the names are on support ents. Support ents such as base surfaces, trim curves, etc are not displayed in Pointwise by default. See attached images. See glyph calls: pw:: DatabaseEntity instance actions: * $entity getImportedAttribute attribute_name * $entity getImportedAttributeNames ?-regex? ?pattern? |
|
December 19, 2017, 12:11 |
|
#3 |
Member
Peter
Join Date: Sep 2011
Location: Germany
Posts: 39
Rep Power: 14 |
Ok, thank you David for the information.
However I was not able to fully resolve my issue. For V18R2 it is definitly not possible to import the names, because with an upgrade to V18R4 I can now see part of the defined faces, with some really ugly names (i.e. Sheet Body "Extrude (4) "side"". However Lines of the Sketch are displayed as supposed (LINEBOTTOM...). I am not allowed to upload test cases but as you see for my very simple model this seems to be a fundamental problem of the NX-import. |
|
December 19, 2017, 17:26 |
|
#4 |
Senior Member
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 14 |
Sorry, but the images of UG/NX don't mean anything to me. I have never used it.
If you zip the test case file, you might be able to attach it to this site. If not, you can try dropbox.com or some other file sharing site. Otherwise, without a file to examine, there is not much I can do. |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[DesignModeler] Unable to Import Geometry | Alan212 | ANSYS Meshing & Geometry | 3 | March 17, 2015 11:26 |
[OpenFOAM] Annoying issue of automatic "Rescale to Data Range " with paraFoam/paraview 3.12 | keepfit | ParaView | 60 | September 18, 2013 03:23 |
[DesignModeler] Import external geometry problem | Houman | ANSYS Meshing & Geometry | 0 | May 16, 2012 04:24 |
Errors running allwmake in OpenFOAM141dev with WM_COMPILE_OPTION%3ddebug | unoder | OpenFOAM Installation | 11 | January 30, 2008 20:30 |
vitual _ real | deneb | FLUENT | 3 | January 22, 2007 04:31 |