Stats

  • Locked Locked
  • Replies 7
  • Subscribers 143
  • Views 17408
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can I set preferences for the default operating point cdsParam definitions in my .cdsinit?

CADcasualty

When I turn on annotations to view transistor operating point information via the cdsParam(n) labels, I get a default set of assignments that don't work well for me (although they likely work for other people just fine). Is there a way that I can define my preferences for MOS operating point cdsParams that isn't tied to any given cell/schematic i.e. I want my settings to be *global* preferences - ideally defined in my .cdinit e.g.

cdsParam(1)=id, cdsParam(2)=vgt, cdsParam(3)=vdsat, cdsParam(4)=gm, cdsParam(5)=rout   etc.

Thanks.

Parents
  • Andrew Beckett

    You can either set the effective CDF in the .cdsinit for each device to change the label display information (the CDF is used to seed the annotation setup), or use the annLoadAnnotationData to load your annotation setup for each window (you can't do this in the .cdsinit because it needs a window id). So you could define a bind key to load it or use a trigger (e.g. deRegUserTriggers) to load the annotation setup when a schematic window is opened, say.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    You can either set the effective CDF in the .cdsinit for each device to change the label display information (the CDF is used to seed the annotation setup), or use the annLoadAnnotationData to load your annotation setup for each window (you can't do this in the .cdsinit because it needs a window id). So you could define a bind key to load it or use a trigger (e.g. deRegUserTriggers) to load the annotation setup when a schematic window is opened, say.

    Regards,

    Andrew.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.