• 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 Design
  3. Hierarchy delimiter and path suddenly changes in PSF

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 15393
  • 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

Hierarchy delimiter and path suddenly changes in PSF

BradW
BradW over 15 years ago
Hey all, I'm still stuck running in the 5.1 stream and using WaveView. Recently all my ocean scripts stopped working when trying to plot/access certain device currents. When I looked into it, it appears that the paths have changed in the psf file. For example, I was using i(“/Iload/L0/PLUS”) and now the same data is accessed i(“Iload:L0:1”) I've seen this in the past but I've never figured out what I did or what happened to make the paths changed. Anyone have an idea? Right now I'm using aps as my simulator but I've used spectre and seen the same thing. When I use the "outputs" command it still lists the "/Iload/L0/PLUS" node as being available but when I go use the waveform it can't find it. Thanks for any help
  • Cancel
Parents
  • BradW
    BradW over 15 years ago
    Thanks for the reply Andrew, Bad slip there, I meant WaveScan. I haven't been moving data around and the amap directory is just where the runObjFile says it should be. Your description sounds just like whats happening so it definitely sounds like a name mapping issue.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • BradW
    BradW over 15 years ago
    Thanks for the reply Andrew, Bad slip there, I meant WaveScan. I haven't been moving data around and the amap directory is just where the runObjFile says it should be. Your description sounds just like whats happening so it definitely sounds like a name mapping issue.
    • 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