• 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. Issue with DRC - "run is invalid"

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 126
  • Views 4520
  • 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

Issue with DRC - "run is invalid"

apaj
apaj over 11 years ago

Hello,

when I try to run BEOL DRC everything seems to be in order. I don't get any errors, Assura successfully loads .rul and .rsf files, and .log file keeps feeling up normaly. I see all the errorchecks being performed and in the end I get "Assura terminated successfully!" message.

Nevertheless, it asks me whether I want to see the output and when I click Yes (or Ok, or whatever is there) it starts a window with a message (the same appears in CIW):

"The run "nameOfMyRun" in "myFolder" is invalid!"

and it offers me to click Ok. When I do - nothing else happens.

Please, would anybody have an idea what is going on?

Thank you very much.

  • Cancel
Parents
  • apaj
    apaj over 11 years ago

     Hm... Somehow I completely neglected your last sentence... I just saw that you are telling me to open the run manually in the end.

    And yes... I do get the Error Layer Window - thank you very much!

    But, since we are already here - what do you think, why does any of this happen? I mean, why not open it normally?

    Also, rereading my post, I noticed one more thing. When Assura is printing some path within <ASSURAHOME> it puts two slashes one after another, e.g.:

    <ASSURAHOME>/assura//tools/assura/bin/avcallproc

    What is that?

    Regards.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • apaj
    apaj over 11 years ago

     Hm... Somehow I completely neglected your last sentence... I just saw that you are telling me to open the run manually in the end.

    And yes... I do get the Error Layer Window - thank you very much!

    But, since we are already here - what do you think, why does any of this happen? I mean, why not open it normally?

    Also, rereading my post, I noticed one more thing. When Assura is printing some path within <ASSURAHOME> it puts two slashes one after another, e.g.:

    <ASSURAHOME>/assura//tools/assura/bin/avcallproc

    What is that?

    Regards.

    • 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