Log FilesCAW & SRAM Finder generate a log file that is extremely useful in helping understand why a crash or problem occurs. Whenever reporting a crash or unexpected behavior the end user should email the log file(s) along with a short problem report. Where to Find The Log FileThe log file is always written to the working directory. This is the directory from which you launch either Qckvu3 (Expert Mode) or SRAM Finder or RPF Finder. This must be a directory where the user has read/write permissions. For example, if I start up CAW or SRAM Finder from the directory /home/stevedb/caw_test1 then I can expect to find several files there after running CAW ... -rw-r--r-- 82156 Nov 6 23:22 caw_auto_1_1.log <-- log file -rw-r--r-- 6838272 Nov 6 23:12 caw_auto_1_extract.gds -rw-r--r-- 0 Nov 6 23:12 caw_auto_1_nb_areas.txt -rw-r--r-- 0 Nov 6 23:12 caw_auto_1_rules2.txt -rw-r--r-- 140 Nov 6 23:12 caw_auto_1_rules.txt -rw-r--r-- 96256 Nov 6 23:22 caw_auto_1_sram_sel.caf -rw-r--r-- 0 Nov 6 23:12 caw_auto_1_windows2.txt -rw-r--r-- 0 Nov 6 23:12 caw_auto_1_windows3.txt -rw-r--r-- 5002 Nov 6 23:12 caw_auto_1_windows.txt -rw-r--r-- 1524334592 Sep 3 2009 caw_test1.gds Log File Naming ConventionThe log file when running CAW (in Auto mode or SRAM Finder production mode) is named: caw_auto_N_M.log where N = session number M = run number The first time you start CAW and proceed to click on Find SRAMs a log name caw_auto_1_1.log will be generated. If you run the SRAM finder a second time (not quitting CAW) then the log from that will be labeled caw_auto_1_2.log. If you then quit or close CAW or change the the input layout file and run again you would get caw_auto_2_1.log. This allows one to make multiple runs (perhaps adjusting settings ...) and have separate log files which can be examined or sent to Artwork for examination. What's In the CAW Log File?Version CA Wizard v1.33 - Auto SRAM ID Copyright © 2008-2011 Artwork Conversion Software, Inc. (831)426-6163 info@artwork.com www.artwork.com Input File Statistics GDSII File Name: /home/stevedb/caw_test1/caw_test1.gds (1.4 GB) User Unit: um Database Unit: 1000 (per um) Number of Structures: 8663 Structure References: 6778872 Array References: 197434 Boundaries: 25930 (3500,87,0) Boxes: 0 (0,0,0) Paths: 2 (0,2) Vertices: 345268 Texts: 0(0) Estimated Memory for Load Data: 219.3MB Total Memory for Load Data: 219.3MB Data Dropped: No Scan Time: 0 min 11 sec (elapsed time) 0 min 10 sec (CPU time) Load Time: 0 min 11 sec (elapsed time) 0 min 11 sec (CPU time) Layers Opened: 17:0,50:0 Bitmap and Extraction Statistics
Support Layer(s): 50 <-- user supplied SRAM support Layer
Poly Layer(s): 17:0 <-- user supplied Poly Layer
Feature Size: 200 nm (127000 dpi) (specified 200 nm) <-- feature size used to
RIP SRAM Support Layer
Cell: osprey_chip <-- top cell
Cell Extents: (71.670,0.850) (5344.150,5198.150) <-- cell extents
Bitmap Extents: (71.670,0.850) (5344.150,5198.150) <-- bitmap extents
Regions Extraction Time: 0 min 3 sec <-- time to convert bitmap to SRAM windows
SRAM Finder Version Sram Finder v1.18 rcs(1.155 2011/11/03) Build 11.11.03.15.41 on Linux 2.6.9-5.ELsmp [x86_64] Architecture x86_64 ArrayFinderDLL v1.137 (2011/11/01) SRAM Finder Command Line COMMAND-LINE: /home/cad/caw/bin/plugins/caw/sramfinder64.exe /home/stevedb/caw_test1/caw_auto_1_ extract.gds /home/stevedb/caw_test1/caw_auto_1_sram_sel.caf /home/stevedb/caw_test 1/caw_auto_1_windows.txt /home/stevedb/caw_test1/caw_auto_1_rules.txt -log:/home/s tevedb/caw_test1/caw_auto_1_2.log -opmode:sramid_expert -progress:18,19 -silent Workstation System Info SYSTEM-INFORMATION: Number of Processors: 1 Total Memory: 3396.32 MB Total Memory Available: 284.14 MB Total Swap Space: 1829.92 MB Extracted File Being Processed FILE: /home/stevedb/caw_test1/caw_auto_1_extract.gds (6.521 MB) SRAM Finder Computation SRAMFINDER MANAGER BEGIN: Fri Nov 4 05:38:12 2011 SRAMFINDER ENGINE CORES: 1 SRAM-FILTER-RULES: arrayfinder_jitter ANY max_x_pitch 6 max_y_pitch 6 min_rows 3 min_cols 3 min_percent_coverage ANY min_element_cnt ANY one_row_or_column OFF SRAM-REGIONS: 141 273.673,1487.679,628.478,2428.097 278.473,2691.302,565.077,2783.704 278.473,2489.098,565.077,2581.500 279.073,3083.309,752.080,3263.513 . . 5099.146,1968.088,5140.747,2034.689 5099.146,1849.286,5140.747,1915.887 4474.137,4494.736,4603.939,4586.138 SRAM Engine Info by Process ID ENGINE-LOG #0 [PID: 2308] COMMAND-LINE: /home/cad/caw/bin/plugins/caw/sramfinder64.exe /home/stevedb/caw_test1/ caw_auto_1_extract.gds /home/stevedb/caw_test1/caw_auto_1_sram_sel.caf.0 /tmp/fileUV10nW /home/stevedb/caw_test1/caw_auto_1_rules.txt -silent -engine -progress:5,6 -log:/home/stevedb/caw_test1/caw_auto_1_2.log.0 Input File Open Time: 0h:0m:0.21s User Unit: um <-- info on the "extracted file Database Unit: 1000 (per um) size and complexity Number of Structures: 1041 Structure References: 101784 Array References: 0 Boundaries: 12660 (97,0,0) Boxes: 0 (0,0,0) Paths: 0 (0,0) Vertices: 120940 Texts: 0(0) Estimated Memory for Load Data: 3.6MB (3738024 bytes) Total Memory for Load Data: 3.6MB (3738024 bytes) Data Dropped: No Scan Time: 0 min 0 sec (elapsed time) 0 min 0 sec (CPU time) Load Time: 0 min 0 sec (elapsed time) 0 min 0 sec (CPU time) SRAM-REGIONS: 141 <-- in this example we only have 1 CPU so all 2207.502,189.254,2270.503,230.654 141 regions are processed by this thread. 2335.304,189.654,2376.905,252.655 5099.146,1849.286,5140.747,1915.887 . . . 1757.896,4059.528,2406.105,4586.338 1757.896,3467.317,2406.105,3996.527 Details on Each Window Extraction By examining the detailed data for each window one can isolate windows that take a very long time to process and then determine why. ENGINE BEGIN: Fri Nov 4 05:38:12 2011 Processing Window : 2207.502,189.254,2270.503,230.654 Explosion Time: 0.006 (s) Ignored Polygon Count: 0 Candidate Polygon Count: 2960 Polygon Storage (capacity): 0Gb 4Mb 32Kb 0b Polygon Storage (size): 0Gb 0Mb 365Kb 320b Polygon Storage (efficiency): 9% Unionized Polygon Count: 1938 Unionizing Time: 0.042 (s) Care Areas Found : 13 (before rules) 4 (final) Care Area Rules Strength : 69 % Array Identification Time: 0.004 (s) Processing Time: 0h:0m:0.05s . . . Processing Window : 1525.892,854.066,1880.497,1268.674 Explosion Time: 0.301 (s) Ignored Polygon Count: 0 Candidate Polygon Count: 177690 <-- much larger SRAM block Polygon Storage (capacity): 0Gb 26Mb 0Kb 0b Polygon Storage (size): 0Gb 21Mb 420Kb 872b Polygon Storage (efficiency): 82% Unionized Polygon Count: 117128 Unionizing Time: 24.764 (s) Care Areas Found : 28 (before rules) 8 (final) Care Area Rules Strength : 71 % Array Identification Time: 0.356 (s) Processing Time: 0h:0m:25.43s <-- much longer processing time Summary Information
Candidate Regions without any Care Areas : 1 <- this is worth investigating to see
if rules excluded recognition of care
areas. Why don't we show the region coordinates?
SRAM Identification Time: 0h:0m:0.00s <- what does this mean?
Total SRAM Processing Time: 0h:9m:31.00s
ENGINE END: Fri Nov 4 05:47:43 2011
#### Box-In-Box Check Disabled
SRAMFINDER RESULTS SUMMARY
Number of SRAM Care-Areas found: 1480
OUTPUT FILES (Mode SramID-Expert):
(SIMPLE CAF): /home/stevedb/caw_test1/caw_auto_1_sram_sel.caf
SRAM GROUPS BY PITCH:
X-Pitch:1.33 Y-Pitch:3.65 Counts:248
X-Pitch:3.65 Y-Pitch:1.33 Counts:1216
X-Pitch:4.32 Y-Pitch:5.32 Counts:16
OUTPUT GDSII CELLS:
CAWSRAM_1.33_3.65: 248 boundaries
CAWSRAM_3.65_1.33: 1216 boundaries
CAWSRAM_4.32_5.32: 16 boundaries
Total Care-Areas Merge Time: 0h:0m:0.00s
SRAMFINDER MANAGER END: Fri Nov 4 05:47:43 2011
<END_OF_OPERATION> 0h:9m:31.26s
Bitmap Generation Time: 0 min 9 sec <-- this belongs at the beginning of the log file
Bitmap Threshold Time: 0 min 12 sec <-- this belongs at the beginning of the log file
Extraction/Cache Time: 0 min 3 sec <-- this belongs at the beginning of the log file
SRAM ID Time: 9 min 32 sec
|