Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 14368
  • 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

drIsWaveform Function

Driss

Hello,

I am trying to find out if the evaluation of a expression is a waveform or a scalar type.

For example:

  myExpression = "dB20(VF(\"/sig_out\"))"

  eval = car(errsetstring(myExpression))

I would like to have a function that returns t or nil depending on whether eval is a waveform or a scalar. 

I read from the following post, that the drIsWaveform should do exactly what I want:

  www.designers-guide.org/.../YaBB.pl



However unlike in this post, the evaluation of my expression returns: srrWave: =XXX instead drwave=XXX

so that  drIsWavefirm(eval) returns the wrong value (nil in this case)

My question:

1) Why do I get a srrWaveform instead of a drWaveform?

2) What is the difference between both types?

3) is there any documentation related to the different data structures used in ADE? 

Many Thanks for your help.

Driss

Parents
  • Andrew Beckett
    Cedric, waveform objects simply changed between IC5141 and IC61X from drWave to srrWave. This is just an internal representation detail that there's no need to worry about. The same APIs work, including the one you mention- drIsWaveform. This only tells you if it is a simple waveform - you'd need to call famIsFamily to check if it is a family waveform. So maybe that is the reason why it is returning nil? Regards, Andrew
Reply
  • Andrew Beckett
    Cedric, waveform objects simply changed between IC5141 and IC61X from drWave to srrWave. This is just an internal representation detail that there's no need to worry about. The same APIs work, including the one you mention- drIsWaveform. This only tells you if it is a simple waveform - you'd need to call famIsFamily to check if it is a family waveform. So maybe that is the reason why it is returning nil? 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.