Running the Program
- Last UpdatedOct 24, 2023
- 2 minute read
The GPP is run either from Nesting PPI or from within the verify function in nesting. The specification of default file and if needed the kerf file are done through the following nesting defaults
GPP_CTRL_ FILE = < file name>
GPP_KERF_FILE = < file name>
The files specified above has to be in directory pointed out by SB_SHIP.
If the postprocessor is run from Nesting PPI, a dialog for specifying generic files to postprocessors will be shown. Select desired files and press OK and postprocessing will start.
If run from within the verify command the following nesting defaults has to be given:
GPP_RUN
GPP_CHECK
GPP_RUN=YES will run the postprocessor after the verify process is completed and if GPP_CHECK =YES the postprocessor check is run directly after postprocessing is finished.
In this way only the active nesting will be post processed and checked.
The GPP may also be run by the command:
sf001 < arguments >
where the arguments are as follows:
|
-k <kerf file> |
argument specifying the Kerf data file (optional) |
|
-d <default file> |
argument specifying the default data file |
|
-g <generic file> |
argument specifying the generic data file |
|
-f <list file> |
argument specifying a file containing a list of generic data file names |
|
-3 <restriction file> |
argument specifying the 3-axis restriction file |
|
-c <check file> |
argument specifying the output file to be checked |
|
-t <list file> |
argument specifying a file containing a list of output data file names |
|
-h |
giving a list of the options above |
When the postprocessor is run, the result is an output file with the name <generic file>.<tape_file_extension> for each input generic file. The output file will be stored in the SB_TAPE directory. A log file (containing any error messages) is also produced in the SB_SHIPPRINT directory. This log file has the same name as the generic file or the List file with the extension .log.