Sometimes the geometry consists of several parts which are arranged on different positions in space. This is called assembly. When cgx is started with the parameter ``-stepsplit'' instead of ``-step'' it will write the single parts to separate directories using their original coordinate systems. The user can prepare meshable geometry or meshes based on them. But he must use the filenames which he finds there. The final meshed assembly can be build afterwards by calling the fbl-file which was also written from cgx. This fbl-file contains commands to position and eventually duplicate the single geometries/meshes from the subdirectories.
For complicated models you should also consider to use a tet-mesher like NETGEN [4] which can read step and generates quite nice tet-meshes. You can read this meshes with cgx and combine them with cgx-geometry and meshes. Then create your boundary conditions etc. You might read the native-netgen format (.vol) instead of abaqus-format because this stores also the 2D meshing regions as separate sets which can be used to apply boundary conditions (``cgx -ng file.vol'').
But you can also create a so called stl-file based on your cgx-geometry and feed it to external meshers. The following section explains how to do that:
In general hexahedra-elements perform better than tets but if the mesh should be derived from a cad-geometry it is often more convenient to create a tetrahedra mesh as to modify or rebuild the geometry to make it meshable with hexahedra-elements. In this case the user can mesh the surfaces with structured (elty setname tr3) or unstructured triangles (elty setname tr3u) and export them in the stl-format (see ''send'') as a basis for an auto-mesher [4]. The following steps have to be done:
(ie: vda2fbd cad.vda > cad.fbd).Sometimes the header of the vda file causes some trouble and must be modified to make the program run.