4.1 Introduction

A Parasolid Fault Form should be submitted to Unigraphics Solutions at Parkers House, Cambridge, for all suspected faults, in Foreign Geometry or otherwise. In addition, Unigraphics Solutions requires access to the users foreign geometry code in order to reproduce and fix the fault.

[back to top]

4.2 Data files required

Unigraphics Solutions requests as much data as possible pertinent to the particular fault being reported. You should try to send us Parasolid journal files (.JNL_TXT) and KID command files (.JOU, .LSP).

However, none of these files contain any of the data about your foreign curves and surfaces except the arguments passed in through the interface via calls to PK_FCURVE_create and PK_FSURF_create. For Parasolid Customer Support to investigate the fault, we need access to your FG functions which demonstrate the faulty behavior. If your functions are so secure that you are unable to supply even data which is similar then Parasolid Technical Support is unlikely to be able to give more than simple advice.

To allow us access to your geometry you should send us, along with the transmit files containing the solids referencing the foreign geometry, the FG module functions FGCRCU/SU, FGPRCU/SU, FGEVCU/SU. For example an object library containing these functions plus whatever data files are required can be sent. Better still, if you are using simple evaluator functions to test this Parasolid functionality, you may be willing to send us the source code for the above functions.

If you cannot send us the evaluators you are working with, you may be able to write a simple evaluator which exhibits the same behavior.

[back to top]

<<< Modeling using Foreign Geometry

Chapters

Geometric Restrictions >>>

Contents

4.1 Introduction

4.2 Data files required