Find Instances That Used a Design Variable

Gilbert,

I was just looking up how I'd done this in some code I wrote last year to do this - but it turns out there was no direct function, and I was using some private SKILL function to do it. Please contact Cadence Customer Support, to ask for an enhancement for a public function to retrieve this information.

Otherwise, you'd have to visit all the instances in the design, looking at the CDF properties on each instance, and then using the ael.* functions to parse any expressions to pull out any variables found.

Regards,

Andrew.

 Hello,

I have project about migrating our simulation tools from IC5141 to IC6.1. I have problem on extraction of design variable from schematic.

In IC5141, we can extract the design variable list using the the following command:

----------------------------------------------------------------------------------

simulator('spectreS)

design(LIB CELL VIEW)

session = asiGetCurrentSession()

lstDesignVariable = asiGetDesignVarList(session)

-----------------------------------------------------------------------------------

I know socket simulation is no longer supported in IC6.1 but when i changed the simulator to 'spectre.

The return of asiGetDesignVarList is always nil.

I found the hidden file of design variable from netlistDir() but our tools used many schematic and it's inconvinience to user if everytime he/she input the schematic temporary netlist is created. This idea is not a good idea.

Is there anyone know what the SKILL command for extracting design variable in IC6.1?

Thanks in advance.

Regards,

AMALAYER

Amalayer,

That would work if there were design variables defined for the cell (i.e. if the "Copy to cellView" has been used in ADE). I don't think that's any different between spectre and spectreS.

There's also artGetCellViewDesignVarList(cvId) which will tell you the saved design variables (actually stored on the cell's property bag).

The functions for finding and searching for design variables down the hierarchy are unfortunately private SKILL functions, so I won't "out" them here... (because they'd be liable to change, and I don't want your code to break if we change or remove the functions, which is why they're private).

Regards,

Andrew.