• 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. How to prevent parameter updates for pending simulations...

Stats

  • Replies 10
  • Subscribers 124
  • Views 1414
  • Members are here 0

How to prevent parameter updates for pending simulations during ADEXL simulation

dogman4
dogman4 2 months ago

Hi,friends

Adexl generates the interactive.0 session after initiating simulation. How can I configure it so that when I later modify parameters in settings such as Tests, Global Variables, Corners, schematics, and config, the pending simulations in interactive.0 continue to use the pre-modified parameters rather than the updated ones?

thanks in advance

  • Sign in to reply
  • Cancel
  • Andrew Beckett
    Andrew Beckett 2 months ago

    Changing Tests, Global Variables and Corners will not affect already submitted runs. Changing the schematic (in ADE XL) will though, if the netlisting has not happened yet.

    This is best solved in ADE Assembler when using "LSCS" as the job submission type (from other posts you are using IC6.1.7 and LSCS didn't exist then - you should switch to IC23.1). That aims to get netlisting done at the beginning which avoids the problem.

    With ADE XL, the workaround is to set this in your .cdsinit :

    envSetVal("adexl.simulation" "ignoreDesignChangesDuringRun" 'boolean  t)

    You should restart ADE after setting this in the .cdsinit and in the CIW (or restart Virtuoso). The downside of the above is that it will do netlisting at the beginning in the foreground and block the UI whilst it is doing that. LSCS handles this better as the netlisting is still done in the background.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • dogman4
    dogman4 2 months ago in reply to Andrew Beckett

    Hi,Andrew

    Thank you for your explanation. If I use config in adexl, and then I modify the config configuration halfway through, is there a way to achieve the above effect?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 2 months ago in reply to dogman4

    ignoreDesignChangesDuringRun solves that problem too. I should have explained that - sorry. It affects both the schematics and the config.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • dogman4
    dogman4 2 months ago in reply to Andrew Beckett

    Hi,Andrew

    I used ignoreDesignChangesDuringRun.

    When using config, the config is changed halfway through, and the pending simulation is also changed.I checked the netlist.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 2 months ago in reply to dogman4

    I'd be rather surprised, since it creates all the netlists up front and is blocked whilst it is doing so.

    Did you get a popup at the beginning of the simulation showing that it was netlisting. Something like this:

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • dogman4
    dogman4 2 months ago in reply to Andrew Beckett

    yes,it popuped.

    My test method is: I use config to simulate a comp, the comp contains two views, schematic and schematic_test, max jobs is set to 1.the comp is initially set to schematic, when I click on run simulationb after two minutes, then I change the comp to schematic_test.I looked in netlist and found that all simulations since then have used schematic_test.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 2 months ago in reply to dogman4

    Which IC sub-version are you using? getVersion(t) in the CIW will tell you this.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • dogman4
    dogman4 2 months ago in reply to Andrew Beckett

    "@(#)$CDS: virtuoso version 6.1.7-64b 11/09/2015 12:45 (sjfnl165) $"

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 2 months ago in reply to dogman4

    I tried with that version, and it works fine for me. I changed the config mid-run and all sweep points used the original config (I did something in the view I switched to make the simulation fail, so it would have been very obvious).

    However, is there a good reason why you're using the base IC6.1.7 release (not even a hotfix) which is almost 10 years old?

    I would strongly advise moving to using ADE Assembler in the latest version and use LSCS. I'd be surprised if you see this issue then. Pursuing why this doesn't work in a really old, long-unsupported version is not something I can realistically spend time on.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • dogman4
    dogman4 2 months ago in reply to Andrew Beckett

    Hi,Andrew

    Thank you very much for your assistance.

    You are correct. I tested the assembler using version 617, and it works properly. However, because I have written a significant number of bindkeys for ADE XL, migrating them to the assembler feels quite cumbersome, which is why I have continued using ADE XL out of habit. Additionally, I also tried version "@(#)$CDS:virtuoso version 6.1.8-64b 09/03/2024 19:11 (sjfhw316) $" on the same computer and encountered the same issue as with 617. For now, I plan to gradually update the bindkeys to the assembler when I have free time in the future.

    Thank you again for your help.

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

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

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