[Artwork] / [QisMLib] / [Programmer's Corner]

Dbload2Gds

Command-line utility to recover GDSII data from a DBLOAD cache (disk image of a database created in QisMLib from a GDSII source)

Command-line reference

dbload2gds +dbload:{dbload_file_path} +gds:{output_gdsii_path} [OPTIONS]

Required

+dbload:{dbload_file_path}

• Specify the path of a valid and compatible .dbload.l64 file to be used as the source
• To check if a .dbload file is compatible, read the first FIVE bytes of the .dbload.l64 file and compare it with the major.minor revision number of dbload2gds. E.g A .dbload.l64 1.06 is compatible with dbload2gds v1.6.xx
• Both the .dbload.l64 and the accompanying .scan.l64 files MUST be present in the same directory

+gds:{output_gdsii_path}

• Specify the path (including file name) of the GDSII file to be created
• The directory component of this path MUST exist and have suitable write permissions

Optional

[-layers:{layer_list}]

• Specify a comma separated list of layer(s) or layer:datatype(s) to extract
• If not used (by default), all the layers present in the .dbload file will be extracted as-is
• If the datatype is omitted for a given layer, all datatypes for that layer are extracted
• E.g : -layers:1,2:10,3,4:20 will extract all datatypes for 1 and 3 and only datatypes 10 and 20 for layers 2 and 4 respectively

[-cell:{view_cell_name}]

• Specify the name of an existing cell to be extracted as the top cell in the output file
• If not used (by default), the deepest top cell is extracted as the top cell in the output
• The name of the output top cell is same as the .dbload file

[-notext]

• If specified, no text elements are extracted. By default, any text if present is extracted as-is

[-loadfrmdisk]

• If specified, the actual data in the .dbload file is accessed from the disk during database traversal and other operations
• If not used (by default), the .dbload file is loaded into memory
• Loading to memory improves execution speed at the cost of increased memory footprint. This option should be used when the .dbload file is significantly large relative to the available memory for the program

[-log:{log_file_path}] -OR- [-log+:{log_file_path}]

• Create an execution log at the specified path (including file name). The directory component of the path must exist with suitable write permissions
• By default, no log is created
• If -log+ is used, an existing file at that path will be appended. With -log, an exisiting file will be overwritten

[-silent]

• If used, no messages are written to stdout/stderr
• If not used (by default), the execution log is written to stdout and error/ warning messages are written to stderr