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)?

You might want to take a look at Solution 20467133 (https://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;DocumentType=tbshtng;solutionNumber=20467133). Also, the initial commands in your function might not really be necessary and might do more harm than good.

Have you tried removing the initial openResults() and selectResult() commands? They are a bit unusual in such a function and might not work properly within ADE-XL.

Hi,

Yes, I already removed the openResults() and selectResult(). Let's create a very basic test case (I know that average function already exists but this is a test):

/**************** TEST FUNCTION ****************
procedure( avg_func(clk)
   let( ()
      result=average(clk)
))
******************************************************/

If I use the avg_func in ADE-XL in the Output Setup tab as "avgfunc(VT("/clk_signal"))" it will say "eval err" in the Results tab just after the simulation finishes (a simulation with more than one design point), however If I re-evaluate the Results then I can see the expected result for all the design points.

Notice that avg_func works fine if you test it with a single design point, but if you select more than one corner, or you have a sweep for any variable or you perform a MC simulation you should re-evaluate in order to see the avg_func correctly evaluated over the different design points results.

Do you know how to make the avg_func work just after the simulation finishes when I have more than one design point?

Thanks in advance.

You probably haven't defined the function such that it's loaded from the .cdsinit. When the simulations are run, background processes (known as "ICRP") are started which take care of netlisting, simulation and results processing; if the function is not available in that background process (e.g. it wasn't loaded via your .cdsinit) then it will fail to evaluate.

When you re-evalate in ADE XL, then it re-evaluates in the foreground and hence would then see your function.

So, make sure any custom functions are automatically loaded at virtuoso start. In IC617 this can also be done for custom functions by using the fx function in the calculator functions panel to add your own function into the calculator - that makes sure it is registered and loaded at virtuoso start too.

By the way, if you have already got these ICRP processes running - e.g. they are "lingering" (the little terminal icons are showing in the run summary in ADE XL) and you then re-define the file containing the code, it won't get re-loaded. In that case, you'd have to go to the Options->Job Setup form and hit the "Stop All" button so that on the next simulation they get re-started.

I think this is almost certainly the reason - it's certainly consistent with the symptoms you describe!

Regards,

Andrew.