• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. output setup shows a yellow row

Stats

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

output setup shows a yellow row

sjwprcker
sjwprcker over 3 years ago

Hi,

When i edit the output setup in maestro/output setup, i got a yellow row and CIW reports: hiCreateListBoxField: Requested numRows does not fit in given field space. List resized to fit.

What does this warning mean? What I need to resize?

When this happens, i can't edit the output setup anymore, e.g., i can't delete, add or even move any row in the output setup. I have to close the maestro and restart again...

BR

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 3 years ago

    I can't find any reports of this specifically to do with the "maestro" output setup (is this Explorer or Assembler? a screenshot might help). Have you adjusted the fonts or font sizes?

    I'm not really sure what you are referring to.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sjwprcker
    sjwprcker over 3 years ago in reply to Andrew Beckett

    Hi Andrew,

    This is screenshot of output setup in assembler. 

    and the report in CIW as below. 

    BR

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to sjwprcker

    I'm not sure that the hiCreateListBoxField messages are really related to the yellow highlights. I must admit I was trying to remember what produces these yellow highlights (I've forgotten, and it's a Friday afternoon...). Which IC sub-version are you using?

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sjwprcker
    sjwprcker over 3 years ago in reply to Andrew Beckett

    Hi, the virtuoso version is IC618-64b.500.24. 

    BR

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ShawnLogan
    ShawnLogan over 3 years ago in reply to sjwprcker

    Dear sjwprcker,

    In reviewing your outputs setup screenshot, it appears the "yellow shaded rows" all contain or define your output name "Nout_PSD". This output is defined as getData("out" ?result "noise"). However, I also noticed this output is listed under (perhaps, my guess) outputs associated with a Transient Noise simulation. However, a Transient Noise simulation will not produce a results of type "noise". Therefore, unless you are also including a small-signal noise simulation, you will not find an analysis of type "noise" and your output Nout_PSD should produce an evaluation error in the results tab. Since it can not be evaluated, your outputs that depend on it (which are also in yellow shaded rows) cannot be evaluated.

    Are you also performing a small-signal noise analysis?

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • ShawnLogan
    ShawnLogan over 3 years ago in reply to sjwprcker

    Dear sjwprcker,

    In reviewing your outputs setup screenshot, it appears the "yellow shaded rows" all contain or define your output name "Nout_PSD". This output is defined as getData("out" ?result "noise"). However, I also noticed this output is listed under (perhaps, my guess) outputs associated with a Transient Noise simulation. However, a Transient Noise simulation will not produce a results of type "noise". Therefore, unless you are also including a small-signal noise simulation, you will not find an analysis of type "noise" and your output Nout_PSD should produce an evaluation error in the results tab. Since it can not be evaluated, your outputs that depend on it (which are also in yellow shaded rows) cannot be evaluated.

    Are you also performing a small-signal noise analysis?

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to ShawnLogan

    The expressions aren't related to transient noise, but instead using a noise analysis in the actimes in a tran analysis. Each of the expressions is retrieving the noise results from a specific time during the transient.

    I can reproduce the problem (the hiCreateListBoxField messages are for something else). The yellow highlights indicate that there's a signal referenced in the output which does not exist - which isn't surprising, since out is the name of the output noise, not a signal. The dependent expressions get similarly tagged yellow.

    Attempting to edit the expressions afterwards gets very messed up. I'll check to see if there's a CCR on this, and if not, I'll file one.

    A workaround I found was to delete the Nout_PSD output, save the maestro view, close it, and then re-open and add Nout_PSD with the expression VN2() which will retrieve the output noise in V^2/Hz. 

    Andrew

    • Cancel
    • Vote Up +3 Vote Down
    • Cancel
  • sjwprcker
    sjwprcker over 3 years ago in reply to Andrew Beckett

    Hi Andrew,

    I understand the yellow highlights coming from the non-signal output. Just be curious that if this is a new feature? I do remember not see such phenomenon before. And why it doesn't display when we run normal noise sim? In that case, out is still not physical output signal, right? Why it is only shown in actime based noise simulation?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information