• 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. psfascii format

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 127
  • Views 8236
  • 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

psfascii format

shaarawy2023
shaarawy2023 over 3 years ago

when i write a netlist for the noise analysis, the output file noise.noise includes the following data :

"freq" 1.00000
"M0" (
0.00000
0.00000
1.42844e-15
4.95885e-11
4.95900e-11
)
"R0" (
1.22664e-16
1.22664e-16
)
"out" 7.04202e-06
"in" 5.74384e-07
"gain" 12.2601
"freq" 1.25893

how can i know which is the thermal noise and which is the flicker noise?

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

    You might want to read the forum guidelines. The title of your post is pretty vague (this is nothing to do with a spectre netlist - it's the format of psfascii output from the simulator), and you didn't say that you'd saved the data in psfascii format (I only know that by recognising the format). Or you could have shared what you've got in the netlist and how you ran spectre. Or you could just leave us to try to fill in the gaps and hope that we can read your mind? Maybe I'm being a bit crabby on a Sunday afternoon, but you're much more likely to get a good answer with well-formed questions with sufficient information.

    What you've done is ignore all the useful stuff at the top of the PSF file which describes the structure. This is just the VALUE section; there's the TRACE section which describes what data type each instance is - so there will be a mapping of M0 and R0 to the corresponding model type, and then above that there is a STRUCT definition for each model type which lists (in order) what each entry means. That will list in turn the 5 noise elements for the MOS devices that is M0 (most likely R0 is a simple resistor with thermal noise and total noise).

    Andrew

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

    You might want to read the forum guidelines. The title of your post is pretty vague (this is nothing to do with a spectre netlist - it's the format of psfascii output from the simulator), and you didn't say that you'd saved the data in psfascii format (I only know that by recognising the format). Or you could have shared what you've got in the netlist and how you ran spectre. Or you could just leave us to try to fill in the gaps and hope that we can read your mind? Maybe I'm being a bit crabby on a Sunday afternoon, but you're much more likely to get a good answer with well-formed questions with sufficient information.

    What you've done is ignore all the useful stuff at the top of the PSF file which describes the structure. This is just the VALUE section; there's the TRACE section which describes what data type each instance is - so there will be a mapping of M0 and R0 to the corresponding model type, and then above that there is a STRUCT definition for each model type which lists (in order) what each entry means. That will list in turn the 5 noise elements for the MOS devices that is M0 (most likely R0 is a simple resistor with thermal noise and total noise).

    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