Stats

  • Locked Locked
  • Replies 6
  • Subscribers 129
  • Views 3070
  • 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

Exporting/plotting data w/ constant time step in IC6.1.5

Rob Gregoire

 Hello - I am looking to save to a file (or even plot) some simulation results with a constant time step in IC 6.1.5. I am having problems finding something equivalent to the "printvs" command that was available with the old calculator (AWD I think).

1) When I use the "table" in the new calculator Iget an error that the waveform is too big (and the resulting waveform is a fraction of what I need)

2) When I use the sample function in the calculator (e.g.  sample(VT("q") 1u 11.52m "linear" 10u) I get a "too many arguments (0 expected, 2 given)..." Error.

3) When I use ocnPrint(VT("q") ?output "./myOutFile" ?numberNotation 'none) command the timestep in the file is not constant, plus the file is huge.

4) When I  ocnPrint(?step 10e-6 VT("q") ?output "./myOutFile" ?numberNotation 'none) I get the same error as I get when I attempt to use the Sample() function.

 

Help! I'm stuck in the improved Cadence environment ;)

 

Parents
  • Andrew Beckett

    Rob,

    I've figured out what the problem is. Somebody has defined a SKILL function called value() in your environment, and that is being used instead of the standard Cadence value() function.

    I can reproduce the same problem if I do:

    procedure(value() t)

    The message about value in your screenshot is the clue - it says too many arguments, 0 expected. If I do arglist('value) it should show:

    (wave \@key scale period xName
        histoDisplay
        (noOfHistoBins 1) \@rest args
    )

    So you need to find where this local value() function is being defined, and remove that. Maybe running with "virtuoso -nocdsinit" as a short term solution might help. If you have the SKILL development environment available, you could start with -nocdsinit, then do:

    installDebugger()
    load(".cdsinit")  ; you might need to give the right path to the .cdsinit to make sure you pick up the right one

    Then afterwards  (assuming it's all loaded OK and the problem remains), type whereIs(value) - it should tell you which file the modified value() function came from (it has to be done with the debugger enabled).

    This is precisely the reason why we advise that customer SKILL code should be written using a unique prefix for each function, ideally starting with uppercase to avoid clashing with Cadence-supplied functions.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Rob,

    I've figured out what the problem is. Somebody has defined a SKILL function called value() in your environment, and that is being used instead of the standard Cadence value() function.

    I can reproduce the same problem if I do:

    procedure(value() t)

    The message about value in your screenshot is the clue - it says too many arguments, 0 expected. If I do arglist('value) it should show:

    (wave \@key scale period xName
        histoDisplay
        (noOfHistoBins 1) \@rest args
    )

    So you need to find where this local value() function is being defined, and remove that. Maybe running with "virtuoso -nocdsinit" as a short term solution might help. If you have the SKILL development environment available, you could start with -nocdsinit, then do:

    installDebugger()
    load(".cdsinit")  ; you might need to give the right path to the .cdsinit to make sure you pick up the right one

    Then afterwards  (assuming it's all loaded OK and the problem remains), type whereIs(value) - it should tell you which file the modified value() function came from (it has to be done with the debugger enabled).

    This is precisely the reason why we advise that customer SKILL code should be written using a unique prefix for each function, ideally starting with uppercase to avoid clashing with Cadence-supplied functions.

    Regards,

    Andrew.

Children
No Data

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.