• 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. No Waveform Data When Using psf Command

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 16443
  • 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

No Waveform Data When Using psf Command

mckeen
mckeen over 10 years ago

Hi,

I'm trying to use the psf command to convert the tran.tran file to ascii format.  I'm pretty sure the tran.tran file is in psfxl format. The syntax I'm using is...

psf -i tran.tran -o tran.dat

However, the tran.dat file that is created doesn't contain any waveform data.  The header info is there, but in the trace section of the file, I only see a single data point at time t = 0

Am I missing something or not calling the function properly?

TRACE
"group" GROUP 11
"ibb_0" "V"
"ibb_1" "V"
"ibb_2" "V"
"ibb_3" "V"
"VBB_0" "V"
"VBB_1" "V"
"VBB_2" "V"
"VBB_3" "V"
"RF_REF" "V"
"RFP" "V"
"RFN" "V"
VALUE
"time" 0.00000
"group" 0.00000
0.00000
0.00000
0.00000
0.00000
0.00000
0.00000
0.00000
0.00000
0.00000
0.00000
END

Thanks

Trent

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    Shawn is right that the most likely explanation is that the data is PSF XL not PSF. With PSF XL there is a header which is there for compatibility, but the actual waveform data is in a different format, and there's no ASCII equivalent, so you can't convert PSF XL to ASCII using the "psf" utility.

    Shawn is not correct about it only storing the data when it changes though - normally the entire waveform is saved with PSF XL (and with PSF); the behaviour of only saving data when it changes (enough) is enabled by using the "compress" option of the tran analysis - this is regardless of the output format though (and has been supported for as long as I can remember).

    Regards,

    Andrew.

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

    Shawn is right that the most likely explanation is that the data is PSF XL not PSF. With PSF XL there is a header which is there for compatibility, but the actual waveform data is in a different format, and there's no ASCII equivalent, so you can't convert PSF XL to ASCII using the "psf" utility.

    Shawn is not correct about it only storing the data when it changes though - normally the entire waveform is saved with PSF XL (and with PSF); the behaviour of only saving data when it changes (enough) is enabled by using the "compress" option of the tran analysis - this is regardless of the output format though (and has been supported for as long as I can remember).

    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