QmRTCR can be run via a command line and a configuration file which contains arguments and directives. This is much "cleaner" than attempting to put a large number of arguments on the command line.
qmrtcrclient64.exe @config_file -log:log_file where qmrtcrclient64.exe full path to the RTCR client @config_file the @ indicates to read from a config_file specify the full path and name of the configuration file -log:log_file full path and name of the log file
The configuration file will contain at least one job directive. The job directive will point to the input file and the output directory; following the job directive will be all of the arguments associated with this job (One line per argument.).
Input File and Output Directory
+job:{input_file_path},{output_dir_path}
[-dpi:{dpix}[,{dpiy}] | -pixelsize:{sizex}[,{sizey}]]
[-correction:{correction_file_path}[,{tolerance}]
[-annotation:{annotation_file_path}]
[-invertimage]
[-shift:INS_WHITE | -shift:INS_BLACK | -shift:REMOVE]
[-colshift:{col_px},...{col_px}]*
[-rowshift:{row_px},...{row_px}]*
[-graylayers:{grey_level},{layer_list}]
[-tiff:packbits | -tiff:bmp | -tiff:raw | -tiff:none]
[-right-to-left]
[-mask:{minx},{miny},{maxx},{maxy}]
[-thrnum:{n_threads}]
[-tile:{minx},{miny},maxpt:{maxx},{maxy}]*
[-tile:{minx},{miny},tilesz:{width},{height}]*
[-tile:{minx},{miny},tilebuf:{size_mb}]*
[-autotiles:{roi_minx},{roi_miny},{roi_maxx},{roi_maxy},ntiles:{nx},{ny}]
[-autotiles:{roi_minx},{roi_miny},{roi_maxx},{roi_maxy},tilesz:{width},{height}]
[-origin:LL | -origin:LR | -origin:UL | -origin:UR]
[-direction:up | -direction:down | -direction:left | -direction:right]
[-only:{tile_num}[,{tile_num}]*
[-keep:{tile_num}[,{tile_num}]*
[-dbg]
Consider the case where we have installed QmRTCR in the following location:
C:\WCAD\QmRTCR64
The client software, QmRTCRclient64.exe will be found in the directory:
C:\WCAD\QmRTCR64\artwork
Let's also say that our GDSII file and our config file is located in the directory: D:\cad_data\raster
and that we have created a subdirectory callled output
to hold our bitmaps.
Then our command line will look like this: (carriage returns added for clarity)
C:\WCAD\QmRTCR64\artwork\QmRTCRclient64.exe full path to client software @D:\cad_data\raster\p1.cfg full path to config file -log:D:\cad_data\raster\p1.log full path to log file
Our config file, p1.cfg
, might contain the following job directives and associated arguments. (We have three separate rasterization jobs embedded into a single config file.
## notice that this job uses DPI instead of pixel size +job:D:\cad_data\raster\p1.gds,D:\cad_data\raster\output\p1_job_1 -dpi:2540 -tiff:packbits -autotiles:-6350.000,-6350.000,552450.000,615950.000,ntiles:4,4 -origin:LL -direction:right ## Notice that this job has correction and annotation turned on +job:D:\cad_data\raster\p1.gds,D:\cad_data\raster\output\p1_job_2 -annotation:D:\cad_data\raster\p1_annotations.txt -correction:D:\cad_data\raster\p1_correction.txt -pixelsize:10 -tiff:packbits -autotiles:-6350.000,-6350.000,552450.000,615950.000,ntiles:4,4 -origin:LL -direction:right -keep:4,13 +job:D:\cad_data\raster\p1.gds,D:\cad_data\raster\output\p1_job_3 -pixelsize:10 -tiff:packbits -autotiles:-6350.000,-6350.000,552450.000,615950.000,ntiles:4,4 -origin:LL -direction:right -invertimage -mask:0,0,400000,400000 -only:1,2,3,5,6,7,9,10,11