• 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. PWL filename

Stats

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

PWL filename

Tobben24
Tobben24 over 12 years ago

Hi,

I'm wondering in what folder you are when you specify PWL file name for a ipwlf symbol? Cannot find any info on this in documentation.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    If you specify a "relative" filename (i.e. one not beginning with /) then it will be resolved using spectre's include path. The include path can be setup via Setup->Simulation Files, and if not set, it will look in the netlist directory (which is the working directory for the simulator) - so probably not what you want.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Tobben24
    Tobben24 over 12 years ago
    Okay. Can you use enviroment variables there?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Where?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Tobben24
    Tobben24 over 12 years ago
    Where you specify the PWL filename, in Edit Object Properties in schematic editor:)
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    That should work. You can't use UNIX env vars in the Include Path in ADE though (I've not re-tested this, but there's a CCR on that).

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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