Annotating Operating Point in Cadence

Discussion in 'Cadence' started by ajay.balan, Feb 5, 2006.

  1. ajay.balan

    ajay.balan Guest

    I am using ic5033 (on Linux 2.6.9) and when I annotate DC operating
    point, the number of significant digits is huge (for example, instead
    of 19.245u, it would annotate 19.24523484374937257u). Does anyone know
    which option to set/unset or what the reason for this is? This doesn't
    happen every time. If I close icfb, and reopen, run the same simulation
    and annotate DC operating point, I get what I expect to see.

    Also, I have trouble saving artist states. When I try to load states,
    some of the previously saved states will not be visible. Moreover, if I
    overwrite an existing state, most of the files get wiped out, and the
    new state would have only one of the files
    (variables/outputs/modelSetup/...) in it.

    Thanks,
    Ajay
     
    ajay.balan, Feb 5, 2006
    #1
  2. From the docs:

    aelPushSignifDigits(x_digs) => x_digs

    Places (pushes) a given value onto the stack of values for the number of
    significant digits the aelEngNotation function uses to create engineering
    notation strnums.


    I don't know what's the reason for the behaviour you see,
    but might be that aelPushSignifDigits is somewhere hidden in a
    Calculator function that you have used before in your
    session and that causes the issue.


    Bernd
     
    Bernd Fischer, Feb 6, 2006
    #2
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.