Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 8547
  • 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

Automatic evaluation of custom functions in Assembler

W Volkaerts

Hi,

I have a follow-up question on https://community.cadence.com/cadence_technology_forums/f/custom-ic-skill/37507/how-to-avoid-to-re-evaluate-ade-xl-result-tab-when-a-custom-function-is-used-for-simulating-more-than-one-design-point-corners-sweep-parameter-or-mc-simulation

I have custom functions which I want to use in Assembler expressions. For example:


procedure(Rs_to_Rp(Zs)
let((Rs Xs)
Rs = real(Zs)
Xs = imag(Zs)
Rp = Rs*(1+(Xs/Rs)**2)
) ; let
) ; procedure

I load the file with my expressions in the .cdsinit file.But, when I run my simulation I still need to refresh manually to get the expression evaluated correctly.

I also tried defining the function directly in the .cdsinit instead of loading the expression file, but it gives the same behavior.

Does Assembler behaves differently as ADE-XL (as described in the previous post)? Anyone an idea of what I can try to do?

Many thanks.

  • Are you using LSCS rather than ICRP (on Job Options form)? If so, you need to load it from a ".vdsinit" file. The expression evaluation is different with LSCS.

    The other issue might also be that your function doesn't handle family data - there are lots of posts around this on this forum. I think it would need to be (I didn't test this, but this is a pretty standard pattern for calculator functions):

    procedure(Rs_to_Rp(Zs) 
  cond(
    (drIsWaveform(Zs)
      let((Rs Xs)
        Rs = real(Zs)
        Xs = imag(Zs)
        Rs*(1+(Xs/Rs)**2)
      )
    )
    (famIsFamily(Zs)
      famMap('Rs_to_Rp Zs)
    )
    (t
      error("Rs_to_Rp: can't handle %L\n" Zs)
    )
  )
)

    Then you could use the "fx" button in the function panel in the calculator, or "+" button in the expression editor to add the function to the calculator. If you do that, it will then appear in the UI, and you don't need to load it in the .cdsinit/.vdsinit

    Andrew

  • in reply to Andrew Beckett

    Thank you Andrew. It is clear now. This topic can be closed

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.