• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. asiAddSimOption question

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 13310
  • 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

asiAddSimOption question

polo
polo over 15 years ago
Hey, Does any one have experience with using the asiAddSimOption method. More precisely, I would like to use the ?editable field. My understanding is that each time the user click in the simulator option, the expression is evaluated. It the evaluated expression is true, then the sim option is enable. If the evaluated expression is false, then the sim option is disable. The Cadence doc write: ?editable s_editable I have no idea how to write in SKILL the s_editable. Any help will be appreciated.
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    For a start, this is not really intended for end-user customisation - it's there for adding simulator integrations. It is possible to add a new entry, but you generally would need to modify the .cdsenv for the simulator you're using in <ICinstDir>/tools/dfII/etc/tools/<simName>/.cdsenv to add a new .cdsenv entry. For example:

     simulatorName.opts    MYOPT  string  ""       nil

    Then you'd do something like:

    asiAddSimOption(tool ?name 'VAOPTS ?type 'string ?sendMethod 'string ?value "" ?editable '(hiGetCurrentForm()->SPICE->value==t))

    In other words, it's either t or nil, or a quoted SKILL expression - in this case checking whether a boolean flag SPICE on the same form is true or not.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    For a start, this is not really intended for end-user customisation - it's there for adding simulator integrations. It is possible to add a new entry, but you generally would need to modify the .cdsenv for the simulator you're using in <ICinstDir>/tools/dfII/etc/tools/<simName>/.cdsenv to add a new .cdsenv entry. For example:

     simulatorName.opts    MYOPT  string  ""       nil

    Then you'd do something like:

    asiAddSimOption(tool ?name 'VAOPTS ?type 'string ?sendMethod 'string ?value "" ?editable '(hiGetCurrentForm()->SPICE->value==t))

    In other words, it's either t or nil, or a quoted SKILL expression - in this case checking whether a boolean flag SPICE on the same form is true or not.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information