• 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. Mixed-Signal Design
  3. How to define a current measurement in ADEXL + Montecarlo...

Stats

  • Locked Locked
  • Replies 13
  • Subscribers 64
  • Views 13517
  • 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

How to define a current measurement in ADEXL + Montecarlo using AMS Designer

markris
markris over 3 years ago

Hi All,

I am facing the following issue:

  1. I am currently setting up some montecarlo simulations using AMS Designer in ADEXL.
  2. I need to define a current measurement to be performed during the Montecarlo runs (at 700 us), that I set up in the following way: value(i("/R15/MINUS") 0.0007)
  3. However, for whatever a reason, the measurement fail for each montecarlo run; following you see the error I get at each montecarlo run (this is an extract of the Job.log):

\o ERROR (ADE-2709): Evaluation of output 'test1' returned 'nil' for point:'1' test:'wk_test:test:1'

\o           Expression:'value(i("/R15/MINUS") 0.0007)'.

\o Ensure that the definition of output is correct.

Could it be that my syntax is wrong? If yes, could you please suggest me the correct one?

Thanks in advance!

  • Cancel
  • markris
    markris over 3 years ago

    Hi All,

    I am facing the following issue:

    1. I am currently setting up some montecarlo simulations using AMS Designer in ADEXL.
    2. I need to define a current measurement to be performed during the Montecarlo runs (at 700 us), that I set up in the following way: value(i("/R15/MINUS") 0.0007)
    3. However, for whatever a reason, the measurement fail for each montecarlo run; following you see the error I get at each montecarlo run (this is an extract of the Job.log):

    \o ERROR (ADE-2709): Evaluation of output 'test1' returned 'nil' for point:'1' test:'wk_kris:sim_test:1'

    \o           Expression:'value(i("/R15/MINUS") 0.0007)'.

    \o Ensure that the definition of output is correct.

    Could it be that my syntax is wrong? If yes, could you please suggest me the correct one?

    Thanks in advance!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to markris

    I combined your two posts (please read the forum guidelines (pinned post at the top of each forum) which ask you not to file the same question in more than one forum.

    Your expression needs to be either:

    value(i("/R15/MINUS" ?result "tran") 0.0007)

    or

    value(IT("/R15/MINUS") 0.0007)

    Otherwise it won't know which analysis to get the result from.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • markris
    markris over 3 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for replying me. I will try and let you know.

    By the way, regarding my double post, yes I read the forum guidelines and, in fact, I wanted to delete the one filed in the other community but, I don't know why, I was not able to perform the action (I was getting an error). But I see that you did it for me. Thanks a lot!


    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • markris
    markris over 3 years ago in reply to Andrew Beckett

    Hi Andrew,

    I tried your suggestions, but now the error changed in a new one:

    ERROR (ADE-2708): Evaluation of output 'test3' failed for point:'1' test:'wk_kris:test:1'
    \o Expression:'value(i("/R15/PLUS" ?result "tran") 0.0007)'
    \o because of the following error(s)
    \o *Error* strcat: argument #1 should be either a string or a symbol (type template = "S") at line 0 of file "*stdin*".
    \o Ensure that the definition of output is correct.

    Any idea?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to markris

    I found a report of an issue with identical symptoms - getting currents in AMS simulation with Monte Carlo, under CCR 2213678 (for my future reference). This was fixed in IC6.1.8-64b.500.10 (ISR10) and the same sub-version of ICADVM18.1 (all ICADVM20.1 versions would be OK since they are after this).

    You didn't mention which IC sub-version you're using (the forum guidelines ask you to provide that too, since it helps narrow down issues that may already have been solved). My guess is that it's earlier than the version with the fix, so you would need to move to a more recent hotfix.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • markris
    markris over 3 years ago in reply to Andrew Beckett

    Hi Andrew,

    The Xcelium version is: 19.09-s008

    The Spectre version is: 18.1.0.397.isr8 64bit 

    So it seems that I am in the buggy version or? If yes, then I have to look for a workaround... unfortunately.. :( 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to markris

    Neither of those version numbers is relevant here. it's the IC version that matters (i.e. the Virtuoso version) - what you see in Help->About in any of the Virtuoso windows.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • markris
    markris over 3 years ago in reply to Andrew Beckett

    Sorry, my mistake; here the version you ask for:

    IC6.1.8-64b.500.6.EHF7461

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to markris

    From the notes in the change request, this broke in ISR6 (I’m not 100% certain of that) and you’re using an engineering hot fix of ISR6. You should move to a later ISR version to solve this (ISR10 or later as I mentioned)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • markris
    markris over 3 years ago in reply to Andrew Beckett

    Ok. Unfortunately this cannot be done due to project rules. But, ok, if no workaround can be found, there is no other chance here. 

    Thanks a lot for your 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