Home > Community > Forums > Digital Implementation > Abort current Command in Encounter-Console

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 Abort current Command in Encounter-Console 

Last post Mon, Aug 7 2006 8:46 AM by archive. 3 replies.
Started by archive 07 Aug 2006 08:46 AM. Topic has 3 replies and 1579 views
Page 1 of 1 (4 items)
Sort Posts:
  • Mon, Aug 7 2006 8:46 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    Abort current Command in Encounter-Console Reply

    Hi Everyone,

    can anybody tell me, if there is a keyboard shortcut or anything to tell cadence encounter to abort execution of the current command and switch back to idle?
    I am aware of ctrl+c, but I want to leave encounter running and just have the possiblity to check, what's going wrong at the moment (especially during routing) by executing other commands or checking the gui.
    I'd appreciate your help.

    Bye


    Originally posted in cdnusers.org by PNR
    • Post Points: 0
  • Mon, Aug 7 2006 12:46 PM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: Abort current Command in Encounter-Console Reply

    Hello,

    There is no way to suspend a running command to check the status of a run.

    Perhaps you could use commands in prototyping mode to understand/guage your design status before launching a more detailed job.

    What command would you like to suspend?

    Regards,
    Elvis


    Originally posted in cdnusers.org by elvis
    • Post Points: 0
  • Tue, Aug 8 2006 2:36 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: Abort current Command in Encounter-Console Reply

    Hi,

    Thanks for the quick reply.

    It's mostly NanoRoute. For example, when the numer of drc-violations stays constant over 6-7 iterations or when you changed your floorplanning and thought you had made room for routing and suddendly, the drc-violations tripple or something like that.

    I know, that I can tell NanoRoute to brake the routing, when it encounters too many violations or tell it the exact number of iterartions to run. But to do it that way is very inconvenient and time-consuming. It would really like to have the opportunity to let NanoRoute run with 'full force' and then just interrupt it, when I see, that it is hardly making any progress.

    You already answered my question, so this is rather a hint for the developpers ;-)

    Bye


    Originally posted in cdnusers.org by PNR
    • Post Points: 0
  • Tue, Aug 8 2006 8:18 PM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: Abort current Command in Encounter-Console Reply

    Hi PNR,

    If you are not already doing the following, it can help:

    generateTracks
    globalRoute
    setNanoRouteMode -drouteStartIteration 0
    setNanoRouteMode -drouteEndIteration 1
    detailRoute
    saveDesgin dr1.enc
    setNanoRouteMode -drouteStartation 2
    setNanoRouteMode -drouteEndIteration 19
    detailRoute
    saveDesign dr19.enc
    setNanoRouteMode -drouteStartIteration 20
    setNanoRouteMode -drouteEndIteration default
    detailRoute

    #set back to default, if not eco route (e.g. in Celtic flow) will not work!
    setNanoRouteMode drouteStartIteration default


    After saying this, I ready miss the little program that companion Silicon Ensemble. Siliocn Ensemble can write out a db every few minutes, and that little program can view these results (with congestion map). I find this very useful as the "area that cause the congestion" can be in a very different location as the final congestion map. For example, somewhere in the layout has congestion. During search-and-repair, the congestion can "drift/Expand". When the congestion drift toward some macros (esp at the corner), the congestion become worse, and that is what you get at the end of routing. Instead of resolving the congestion at the corner of the macro, it is more effective to solve it at the root cause; but this is possible if you can see the root cause in the first place. A pity that SOC does not provide users this useful methodology to resolve congestion.

    However, note that we can throw out intermediate db during optDesign, so if final congestion map and global congestion map are matching, it is a way to detech root cause of congestino.


    Regards,
    Eng Han


    Originally posted in cdnusers.org by EngHan
    • Post Points: 0
Page 1 of 1 (4 items)
Sort Posts:
Started by archive at 07 Aug 2006 08:46 AM. Topic has 3 replies.