• 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. OceanScript Postsim Net Name

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 145
  • Views 16782
  • 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

OceanScript Postsim Net Name

Freddyyyyyyy
Freddyyyyyyy over 6 years ago

Hi all,

I encounter a problem when using Ocean Script run post transient simulation.

As in the extraction file, some nets have format like "XI33<2>/abc/net5" and "X12/net1"

I can check the net waveform in VIVA. But once I try use OceanScript to get its value, as v("/XI33<2>/abc/net5"), a warning comes up,

"The output '/XI33<2>/abc/net5' you selected does not exist. ".

But for net "X12/net1", all functions work. No warning or errors.

I guess its the name syntax causing this issue.

Could anybody tell me the right syntax? 

  • Cancel
Parents
  • drdanmc
    drdanmc over 6 years ago

    you can use

    outputs()

    to get a list of all outputs and see what your net turned into.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Freddyyyyyyy
    Freddyyyyyyy over 6 years ago in reply to drdanmc

    Thanks for your reply. I have check the net return in outputs(). The net name is exactly "/XI33<2>/abc/net5". But v("/XI33<2>/abc/net5") still cannot work. Any other suggestions?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Freddyyyyyyy
    Freddyyyyyyy over 6 years ago in reply to drdanmc

    Thanks for your reply. I have check the net return in outputs(). The net name is exactly "/XI33<2>/abc/net5". But v("/XI33<2>/abc/net5") still cannot work. Any other suggestions?

    • 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