Good ADC link

http://www.maxim-ic.com/appnotes10.cfm/ac_pk/2

Some useful unix commands to monitor process

ps -ef | grep user

ps -ef | grep icfb

restarting cadence license server

/CMC/tools/cadence/IC/tools/bin/lmgrd -c /CMC/tools/licenses/cds.license

Measuring capacitance and Q factor from s parameters

Cin
value((imag((YP 1 1)) / (xval((YP 1 1)) * 2 * pi)) 5.426e+09)
cap_Q
value((imag((YP 1 1)) / real((YP 1 1))) 5.426e+09)

Cadence crash of the day...

Like usual.. without warnign or reason... "floating integer error" boom... erasing the cadence cds.lib file with it... why???

ASSURA Tutorials

Some of the best tutorials I found floating around on the interweb, note that one of them is in spanish but since it's a cadence tutorial it's comprehensible enough.

EMG TUTORIAL
English Tutorial

QRC (ASSURA) How to fill the forms for extraction

Assura QRC (Filtering Menu)



Assura Extraction (Setup Menu)



Assura QRC (Setup Menu)

Setting the command for extraction with QRC

In order to allow for QRC extractiont o proceed smoothly with ASSURA (proceed at all) the following shell environmental variable must be entered into the icfb window:

setShellEnvVar("QRC_ENABLE_EXTRACTION=t")

You can also achieve the same task by placing it in the .cdsenv file located in the cadence run directory....

Assura configuration menu for DRC

The following is a screenshot of the typica configuration I employ when running ASSURA DRC... Make sure you run assura from the IBM_PDK menu which configures the appropriate kit specific files...

Calirbe license file for extraction...

As far as I'm aware there is no Calibre extraction capability on the DOE system. Thus the only other options left are DIVA and ASSURA with DIVA no longer being supported ASSURA is the only complete package to performed DRC/LVS/QRC(extraction). Since the sign off tool is Calibre any design must ultimately meet the Calibre DRC test.

Removing cadence locks

First I found the clsAdminTool using the locate command but it should typically be in the technology folder. I then ran clsAdminTool to see if there were any locks on the project I was working on. I got some output along the following lines:

clsAdminTool exiting with status 0
tunis(stelescu): ~ $./CMC/tools/cadence/ASSURA-5141.3.20.022/tools.lnx86/bin/clsAdminTool -ale ostelesc/cadence
bash: ./CMC/tools/cadence/ASSURA-5141.3.20.022/tools.lnx86/bin/clsAdminTool: No such file or directory
tunis(stelescu): ~ $
tunis(stelescu): ~ $/CMC/tools/cadence/ASSURA-5141.3.20.022/tools.lnx86/bin/clsAdminTool -ale ostelesc/cadence
BEGIN: Edit Locks List
ostelesc/cadence/libManager.log.21300 bigshot.omic.carleton.ca 21300 1298070979
ostelesc/cadence/libManager.log.12926 bigshot.omic.carleton.ca 12926 1278702057
ostelesc/cadence/ass/superass/schematic/sch.cdb bigshot.omic.carleton.ca 29149 1275521699
ostelesc/cadence/libManager.log.32320 tunis.doe.carleton.ca 32320 1302741992
ostelesc/cadence/libManager.log.22129 bigshot.omic.carleton.ca 22129 1279648545
….
END: Edit Locks List

SUMMARY: A total of 131 Edit Locks were found in the directory hierarchy: ostelesc/cadence

To remove the locks simply use:

clsAdminTool -are FOLDER

END: Release Edit Locks.
SUMMARY: A total of 131 Edit Locks were released in the directory hierarchy: ostelesc/cadence
tunis(stelescu): ~ $