Simple Way to get QTrek techfile from CDS Techfile??

Is there any simple way to get QTrek techfile??

 

The information in the DFII techfile is not necessarily the same
information that is in the Virtuoso Layout Migrate technology file. In
fact, most of the information in the qtt file isn't even in the DFII
techfile (yet).

Just like you wouldn't necessarily derive an Assura or Calibre rule
deck from the DFII technology file, you don't necessarily have all the
data points you need for a layout migration or optimization or eco in
the DFII technology file.

However, there is a simple AE ware (undocumented unsupported) 300-line
PERL script, tf2qtt, that creates a boilerplate qtt file from an ASCII
dump of the DFII techfile.

In addition, Customers should press their CDK vendor to supply the qtt
file (for now) in the CDK pdk vlm directory. For example, I just
looked in the latest Cadence generic 90nm CDK (CDK090_v1p0p7) which
contains the following directory tree:
CDK090 / pdk090 / vlm090 / gpdk090.qtt & gpdk090_migratemap.il

John Gianni
---
Nothing I say on the USENET is sanctioned by my employer.

CDK === Complete Design Kit (everything to run all desired tools)
pdk === process design kit (enough to run all desired custom
tools)
vlm === Virtuoso Layout Migrate (the desired tool in question on this
thread)

 

Thanks for the info. I belong vendor side!! Is tf2qtt script available
in the installation tree?

 

John,

Aki Fujimura mentioned during DATE that a foundry database standard not quite unlike OA was on it's way.
Do you have news about that ?
Will that help share process/physical/electrical data among P&R, layout edit, retargetting, verification, tutti quanti ?

It is true that those tools don t necessarily need the same values, so there must be a mechanism to let the PDK maker declare tool-specific values. But it is not AFAICS contradictory with those tools using tech data from the same source by default.
Tech data is needed by icc, fastcap/RCX, VXL, cell3, Qtrek, .... and too little integration to my taste. Wouldn t you see a unified database that contains enough info LPE, EM solvers, and can be extended for complete TCAD, as a step in the right direction ?