• 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. how is the input.scs generated?

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 144
  • Views 15054
  • 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

how is the input.scs generated?

imagesensor123
imagesensor123 over 13 years ago

Hi,

  i wonder how to generate the cadence "input.scs", as i know, it is composed by several parts, such as, netlist header, netlist, and netlist footer, but i want to modify the netlist and without changing the schematic, for example, adding a capacitor in a circuit node. who has done such works? certainly, we can modify the netlist manually, but i would like to do this by some skill function, is it pratical and possible?

  • Cancel
Parents
  • berndf
    berndf over 13 years ago

     Check for the 'asi' functions.
    Something like this could return you the run directory:

    o_session = asiGetCurrentSession(  )
    asiGetAnalogRunDir( o_session )

    I don't know exactly if this is what you are looking for.
    Probably OCEAN function can also support your task.

    Bernd

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • berndf
    berndf over 13 years ago

     Check for the 'asi' functions.
    Something like this could return you the run directory:

    o_session = asiGetCurrentSession(  )
    asiGetAnalogRunDir( o_session )

    I don't know exactly if this is what you are looking for.
    Probably OCEAN function can also support your task.

    Bernd

    • 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