• 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 SKILL
  3. somethings about panic file

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 145
  • Views 18854
  • 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

somethings about panic file

nidon
nidon over 13 years ago

Dear sir:

 I write a code to generate layout(about more than 80000 layouts),but when I run it,sometimes the CIW window will show the information:

CellView(test1 layout) from lib(test) is saved in the panic file(/path/test/test1/layout/layout.cd-)

To recover do:

dbOpenPanicCellView("test" "test1" "layout")

And then,the icfb will closed by itself,and I have to rerun the code again.

I guess the reason is I generated too more layouts one time,isn't it?

If it is,how shoud I do

Thank you!

  • Cancel
Parents
  • nidon
    nidon over 13 years ago

    Thanks for Quek and  marcelpreda

    I check my code,and I found I use dbOpenCellViewByType and don't use the dbClose to release the memory generated by dbOpenCellViewByType .

    So,I think it's the key reason.

    And for your suggestions to  improve the speed of script,I did a test for them.
    I use the command groups dbOpenCellViewByType(fileA) ,dbOpenCellViewByType + dbClose(fileB),dbOpenCellViewByType +dbClose+hiSetUndoLimit(0)(fileC) in three files(each file total generate 60000 layouts) .And run them at one time.

    And the result is running time of fileB > fileA  >= fileC.

    I feel very insteresting here,theoretically speaking I use dbClose to release the memory,so the time of file A should be the longest time in the three.But the result is the longest file is fileB(I run these files in three computer).

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • nidon
    nidon over 13 years ago

    Thanks for Quek and  marcelpreda

    I check my code,and I found I use dbOpenCellViewByType and don't use the dbClose to release the memory generated by dbOpenCellViewByType .

    So,I think it's the key reason.

    And for your suggestions to  improve the speed of script,I did a test for them.
    I use the command groups dbOpenCellViewByType(fileA) ,dbOpenCellViewByType + dbClose(fileB),dbOpenCellViewByType +dbClose+hiSetUndoLimit(0)(fileC) in three files(each file total generate 60000 layouts) .And run them at one time.

    And the result is running time of fileB > fileA  >= fileC.

    I feel very insteresting here,theoretically speaking I use dbClose to release the memory,so the time of file A should be the longest time in the three.But the result is the longest file is fileB(I run these files in three computer).

     

     

    • 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