• 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. ADEXL: Making Dependent Tests

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 125
  • Views 23170
  • 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

ADEXL: Making Dependent Tests

BrJaWr
BrJaWr over 8 years ago

I've been looking over manuals and posts and can't seem to find an answer to this.  Can you make one test dependent on an expression generated from another test.

For Example:

Test1 : Find a DC Operating point and measure voltages/parameters.  The measured values could be anything you could calculate using the Output Setup and calculator functions.

Test2: Use the calculated results from the ADEXL Test1 Results for the second test.  

I know you can do some of this in spectre running multiple tests and saving states but I'd like a more generic/powerful solution.  When running across corners this should be done on a corner by corner basis (Test1/Corner 1 feeds Test2/Corner1).

Thanks

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    calcVal() is your friend here. The approach is as follows:

    1. In your first test, have an output which calculates the result you want to pass to the second test. Make sure it has a name. Let's call that "result1" and the first test is called "test1".
    2. For whatever you are hoping to control with the second test, ensure you have a design variable for that (and that the design variable is a global variable which is used by the second test but not the first test). Let's call that "variable2"
    3. Drag the output "result1" over to the value of the global variable variable2. You'll see it creates it with an expression calcVal("result1" "test1") (you could type it in, but drag and drop will do it too).

    That's it. Now it knows there's a dependency and test2 won't run until test1 is completed. You can also use calcVal in output expressions to calculate results which are a function of more than one test - again, this sets up the dependencies.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • BrJaWr
    BrJaWr over 8 years ago
    Thank! Worked great
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • BVT1
    BVT1 over 7 years ago in reply to Andrew Beckett

    Hi Andrew,

    How about if I want to use "result1" to define a variable for "test2" in the Corners Setup?

    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to BVT1

    I don't see what benefit having this as part of the corners set up would be. If you have the dependency in the variables, then you get the result from the corresponding corner anyway.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Billy T
    Billy T over 7 years ago in reply to Andrew Beckett

    You won't get the corners though, and it is a pain since ADE-XL sorts out the results differently when you sweep a variable instead of using the Corners Setup.

    I want to use "result1" and "result1a" from "test1" in "test2" to define min and max corner cases. I want the results to be part of one corner set, not 2 corner sets (one for min and one for max).

    Unfortunately, I haven't managed to get the variable sweep to work with "result1" and "result1a" either. I used the syntax you mentioned above: calcVal("result1" "test1") calcVal("result1a" "test1"). ADE-XL only takes "result1" and ignores "result1a". I used an inclusion list with no luck either.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to Billy T

    OK, so you're asking a different question from the one in the original post, and hadn't explained that what you were trying to do something different (this is precisely why the forum guidelines ask you not to post on old threads, especially when there's some difference in your question).

    If you want to use a previous result to define points in a sweep set either via swept variables or via corners, you can't do that.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Billy T
    Billy T over 7 years ago in reply to Andrew Beckett

    Thanks for your prompt response.

    What I am after is very similar to this thread; the only difference is the sweep/corner option. General forum guidelines often urge you to ensure, before you post a new thread, that the answer you are after is not closely related to something already posted.

    Anyway, I have now managed to sweep the dependent variable by using 2 inclusion lists (not both in one):

    {Inclusion List}calcVal("result1" "test1"){Inclusion List}{Inclusion List}calcVal("result1a" "test1"){Inclusion List}

    It'd be very beneficial if this worked in the corners. I know for a fact it used to work some time ago (not in the latest ADE-XL).

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to Billy T

    I wasn't talking about general forum guidelines (presumably for other forums), but the specific forum guidelines for this forum (pinned post at the top of each forum).

    Anyway, if this worked before (I haven't tested in old and new versions) and doesn't any more, then it's a regression and you should contact customer support to report it. That said, I think this may be an untested feature and it just happens to work in some situations and so we need to formalise its use so that it's documented and tested behaviour.

    Regards,

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • 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