The boolw64f Boolean Engine

boolw64f (on Linux it is called boolmt because it is multi-threaded) is the underlying Boolean engine for QckBool and many other of Artwork's programs that require boolean operations. It performs the basic Boolean commands: union, and, or, XOR and minus. It also can size data up or down by a user specified amount.

Unlike some Boolean tools, boolw64f supports all angle data and extremely large and complex polygons and files.

All input and output is stream format. Input files may be hierarchical but output files are always flat.

boolw64f can be called from any other application or framework. When combined with Artwork's GDSFILT engine which can be used to combine and extract stream file data, a user can write a custom application that performs all sorts of advanced tasks on large mask files.

This note explains the correct syntax for using boolw32f.


The boolw64f Command Line Syntax

     boolw64f inputfile outputfile structure target_layer(s) opcode [optional arguments]


name of the executable. Generally you would use the full path unless you know that the location is in the PATH environment statement or you know that the executable is in the current directory.



name of the input GDSII stream file. Use the full path as needed i.e.

"C:\My Files\gdsii\test_case.gds" [Windows]
/home/steve/gdsii_files/test_case.gds [Linux]



name of the file that boolw64f will create. Use the full path as needed. If the file already exists it will be overwritten without prompting.



name of the structure to process in the input file. GDSII file are generally hierarchical. All data in that structure and on any referenced structures or arrays (SREF and AREF) belonging to your specified structure will be selected.

Structure names are case sensitive so that if the internal GDSII structure name is TESTMOSTST then you must use the same case on the command line. If you want to process the top cell in the file and you don't know its name, you can just put the = sign instead of the cell name.



the target layer or layers. For some operations this is a single layer. For other operations this may be a list of semicolon delimited layers. GDSII uses layer numbers from 0-63. boolw64f supports layer numbers from 0-1024.



Opcode describes which operation to perform and describes the source layer(s). If multiple jobs are required the opcode/layer arguments are delimited by semicolons.



The optional arguments are independent of each other and their order of appearance in the command line is interchangeable as long as they all appear after the required arguments.

Page     1  |   2  |   3  |   4  |   5  |   6