• 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. analysis

Stats

  • Locked Locked
  • Replies 29
  • Subscribers 125
  • Views 22347
  • 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

analysis

yeong
yeong over 12 years ago
hello
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Probably this is because you're not closing the file. In SKILL (as in many other languages), writing ASCII files is buffered (for efficiency reasons) so that it doesn't flush to disk until the buffer is full (or when the file is closed).

    So two choices:

    1. Call close(out) at the end (in fact you should do this anyway to avoid having lots of open file handles lying around)
    2. If you want the output to update more frequently (for example, so that you can see the file contents during a loop where running the simulations takes some time), you can flush the buffers by calling drain(out)

    Regards,

    Andrew.

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

    Probably this is because you're not closing the file. In SKILL (as in many other languages), writing ASCII files is buffered (for efficiency reasons) so that it doesn't flush to disk until the buffer is full (or when the file is closed).

    So two choices:

    1. Call close(out) at the end (in fact you should do this anyway to avoid having lots of open file handles lying around)
    2. If you want the output to update more frequently (for example, so that you can see the file contents during a loop where running the simulations takes some time), you can flush the buffers by calling drain(out)

    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