Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13571
  • 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

Assembler mistaking (automatic) evaluation order of matlab-dependent expressions

dontpanic

I have in my test several expressions that depend on the outputs of matlab scripts. For instance, a figure-of-merit "FoM" is defined as:

(Power_DUT / ((2**calcVal(ENOBcal)) * VAR("Fclock"))))

where ENOBcal is defined as "Matlab script" output (calculates the effective number of bits after calibration).

The problem is that, after the simulations finish, Assembler fails to automatically evaluate these outputs in the correct order, and all the expressions dependent on matlab scripts fail. For ex. the FoM output evaluates to "eval err", and in the CIW I get the following message:

*Error* ("expt" 1 t nil ("*Error* expt: can't handle (2**nil)"))

If I press the re-evaluate button, Assembler does figure out the right evaluation order and everything evaluates correctly. However, this is not a convenient solution for e.g. when doing long Monte Carlo runs with thousands of points: in this case the re-evaluation of all points can take long (and also consume lots of CPU resources and matlab licenses). Instead, it would be ideal if the outputs for each Monte Carlo point were correctly evaluated as the points finish simulating.

Is there anyway to enforce the correct automatic evaluation of matlab-dependent expressions in Assembler?

Thanks and regards, Jorge.

P.S. I tried removing the calcVal(), but then I get the error:

*Error* ("expt" 1 t nil ("*Error* expt: can't handle (2**unbound)"))

  • Andrew Beckett

    Please report this to customer support. It should happen automatically and if it doesn't, that's a bug.

    Andrew.

  • dontpanic
    in reply to Andrew Beckett

    OK Andrew, I'll create a test case and submit it.

    Thanks and regards, Jorge.

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.