Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 11674
  • 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

ADE output calculation from other expression not working

Jin W Kwak

Hi Cadence,

I recently moved from using IC 6.1.6 to IC 6.1.8.

In IC 6.1.6, I always calculated my efficiency by first calculating PIN,POUT, and PGATE from expression and re-used the names of expression to calculate the efficiency (EFF).

However, when I try the same steps in IC 6.1.8, PIN, POUT, PGATE are successfully calculated, but EFF is not outputing anything in ADE as shown below:

The expression for EFF is set as below:

When I try to calculate EFF from ADE, it returns the following message:

However, when I copy the exact same expression to calculator and calculate it there, it returns the correct value.

I want the expression EFF to be calculated under ADE automatically at the completion of simulation. (Which was possible in ic 6.1.6)

Is there a workaround for this issue?

Thank you,

Jin

Parents

  • Jin,

    There's a bit of inconsistency in your outputs - with one output being called PGATE, yet your expression being (POUT / (PIN + GATE)) (i.e. using "GATE" not "PGATE"), yet the error message is referring to PGATE, and the calculator expression is using GATE. I used the expression (POUT / (PIN + PGATE)) and it worked fine in ADE L (I see you're using the end-of-sale product ADE L) in IC6.1.8-64b.500.23 (the latest hotfix). Which sub-version are you using? (Help->About will tell you).

    Andrew

  • in reply to Andrew Beckett

    Hi Andrew,

    I accidentally deleted P in front of GATE before I took the screenshot. 

    You can see that the expression is correct in the error message.

    The correct expression below still experiences the same issue reported above:

    A screenshot is attached for the sub-version.

    Jin

  • in reply to Jin W Kwak

    It works for me in that sub-version too. I'm a bit surprised that it would fail - it's a pretty basic capability that has worked for many years.

    Ah, it's probably this - which was fixed in the version I tried this in originally, and so when I then went back to ISR5, all my variables were consistent. It's the fact that you got the variable names wrong that's probably the problem - and then renaming them didn't help. See this article: Renaming expressions in ADE gives ERROR (ADE-1057) (it has a bit of SKILL code which should fix the expressions).

    Andrew

Reply
  • in reply to Jin W Kwak

    It works for me in that sub-version too. I'm a bit surprised that it would fail - it's a pretty basic capability that has worked for many years.

    Ah, it's probably this - which was fixed in the version I tried this in originally, and so when I then went back to ISR5, all my variables were consistent. It's the fact that you got the variable names wrong that's probably the problem - and then renaming them didn't help. See this article: Renaming expressions in ADE gives ERROR (ADE-1057) (it has a bit of SKILL code which should fix the expressions).

    Andrew

Children

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.