Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 1782
  • 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

Using 'temperature' as a design variable breaks calcVal functionality

Kevin Buck

I'm using the calcVal function to use a found trim value from my first test in a second and third test and it works as expected. I've added a fourth test that creates a design variable called temperature and I'd like to set it using the calcVal function output of my second test. For some reason though this breaks the calcVal function in the second two tests. If I disable the fourth test everything works again as expected.

If I enter a hard coded value for temperature in the fourth test then it still breaks the calcVal functionality in the second and third test.

Is this a bug or am I missing something?

I'm using Cadence version IC6.1.8-64b.500.9.

  • The issue with my fourth test is now clear, there was a mismatch in the number of parameters and the ?matchParams argument helped to clear it up.

    I still don't understand why this broke the second and third test which were only dependent on the first, I resolved that error by adding the ?getFirstSweepPoint t argument.

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.