• 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. Modify Assembler Max Jobs on Frozen Virtuoso

Stats

  • Replies 2
  • Subscribers 131
  • Views 35
  • Members are here 0

Modify Assembler Max Jobs on Frozen Virtuoso

dogman4
dogman4 1 day ago

Hi,friends My Virtuoso has been completely frozen for several days, yet the simulations launched via Assembler are still running.
Now I want to increase the max jobs limit; is there any feasible solution?
In addition, can I adjust the max jobs if Virtuoso crashes while simulations keep running?
My virtuoso version: "@(#)$CDS: virtuoso version 6.1.8-64b 09/03/2024 19:11 (sjfhw316) $"
My spectre version: Version19.1.0.063 64bit--10 Aug 2019
thx in advance

  • Cancel
  • Sign in to reply
Parents
  • Andrew Beckett
    Andrew Beckett 1 day ago

    This is something that is available in IC23.1 and later if you have the "ADE Simulation Manager" capability (included in the ADE Artist tier in IC25.1). You can submit simulations and then these are managed by a background process, and you can exit the main Virtuoso session (or it could be killed/crash) and the simulations keep running and even unstarted simulations in the pool to be simulated will continue starting. You can then reconnect to the running session to update and modify settings, look at results and so on.

    There was some very limited support for keeping simulations running in IC6.1.8 via the:

    adexl.distribute  continueICRPRunOnAbruptGUIExit boolean t

    cdsenv var, but this needs to have been set (in .cdsenv or via .cdsinit) before ADE started. Even then, all this does is keep the simulations that have already started running even if the Virtuoso that launched them is killed; any unstarted simulations will not be started. You can't reconnect and observe simulations still running - all it would allow you to do is open the maestro/adexl view again later and view the history once the simulations have finished. This is nowhere near as smart a feature as the newer ADE Simulation Manager.

    So I think your options are quite limited, sorry!

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett 1 day ago

    This is something that is available in IC23.1 and later if you have the "ADE Simulation Manager" capability (included in the ADE Artist tier in IC25.1). You can submit simulations and then these are managed by a background process, and you can exit the main Virtuoso session (or it could be killed/crash) and the simulations keep running and even unstarted simulations in the pool to be simulated will continue starting. You can then reconnect to the running session to update and modify settings, look at results and so on.

    There was some very limited support for keeping simulations running in IC6.1.8 via the:

    adexl.distribute  continueICRPRunOnAbruptGUIExit boolean t

    cdsenv var, but this needs to have been set (in .cdsenv or via .cdsinit) before ADE started. Even then, all this does is keep the simulations that have already started running even if the Virtuoso that launched them is killed; any unstarted simulations will not be started. You can't reconnect and observe simulations still running - all it would allow you to do is open the maestro/adexl view again later and view the history once the simulations have finished. This is nowhere near as smart a feature as the newer ADE Simulation Manager.

    So I think your options are quite limited, sorry!

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
  • dogman4
    dogman4 1 day ago in reply to Andrew Beckett

    I'm pleased to see these upgrades in IC23.1, though unfortunately I don’t have access to it yet.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel

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.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information