• 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. RF Design
  3. Use of calcVal function & sequential simulations where the...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 63
  • Views 2587
  • 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

Use of calcVal function & sequential simulations where the source simulation has a design variable sweep

DKaraca
DKaraca over 2 years ago

Hi,

My question is as follows:

I have two tests: "dc1" & "dc2"

For "dc1", I have a local variable sweep ("vdc"):

And the second test "dc2" uses a calcVal function dependent on "dc1":

"vdc_at_3mA" is an output expression calculated using "sweeps" EvalType in test "dc1":

Then I run these two tests for multiple corners, for example, typical, slow & fast.

For each corner, "vdc_at_3mA" output is calculated in test "dc1" & then fed to "dc2" as expected. No issues so far.

However, for whatever reason, if one of the corners take long to converge in test "dc1", "dc2" test does not initiate also for the corners which have converged & finished, until "dc1" is completed for all corners.

For example, say "dc1" test finishes in:

a) 2 minutes for typical corner,

b) 3 minutes for slow corner,

c) 75 minutes for fast corner,

the "dc2" simulation will start only after 75mins also for typical corner, although all the required data for "dc2" test to start in typical corner is available after 2 minutes.

Could you please advice me on this problem? Is there a way to let "dc2" start as soon as "dc1" simulation of a given corner is finished, rather than waiting for all corners to finish.

Please note that I've given a simplified example here. In the actual scenario, I use a transient simulations and therefore using an internal sweep parameter within the test itself is not an option (which could be a potential solution for dc simulations).

Thanks in advance!

My Cadence version is: ICADVM20.1-64b.500.29

  • Cancel
Parents
  • DKaraca
    DKaraca over 2 years ago

    Still hoping for some help Slight smile

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to DKaraca

    This would be best handled via customer support. There were some specific situations where it behaved as you described, and there are some fixes for these coming in IC23.1 ISR1 (IC23.1 is already released, but ISR1 is due middle of August 2023). It would be worth checking via customer support to ensure that your specific scenario is addressed by this fix (a CCR to reference when reporting this is 2102243), because if the fix doesn't handle your scenario then another change request (CCR) can be filed on your behalf.

    I'm afraid I don't have the bandwidth at the moment to create a test case myself to test this myself.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to DKaraca

    This would be best handled via customer support. There were some specific situations where it behaved as you described, and there are some fixes for these coming in IC23.1 ISR1 (IC23.1 is already released, but ISR1 is due middle of August 2023). It would be worth checking via customer support to ensure that your specific scenario is addressed by this fix (a CCR to reference when reporting this is 2102243), because if the fix doesn't handle your scenario then another change request (CCR) can be filed on your behalf.

    I'm afraid I don't have the bandwidth at the moment to create a test case myself to test this myself.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • DKaraca
    DKaraca over 2 years ago in reply to Andrew Beckett

    Thanks for your reply. I'll contact customer support.

    • Cancel
    • Vote Up 0 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