• 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. OCEAN getData behavior

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 124
  • Views 16842
  • 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

OCEAN getData behavior

SharksFan
SharksFan over 14 years ago

 Hi,

I have a list of signals and corresponding strip numbers that I want to plot them on in a form like:

 my_stripAssignment = list( '(v("/enable")       1)

                                              '(v("/disable")       2) )

I have a foreach loop that grabs the signals and their strip number assignment one-by-one:

foreach( signal_name my_stripAssignment

 plot( getData(car(signal_name)) ?strip cadr(signal_name) ) )

I noticed that if I query the signal_name during the loop that it no longer just returns the assigned value out of the list, but instead also has the resultsDir and result data along with it.  In other words, I expected signal_name to return v("/enable") , but instead it returns v("/enable" ?resultsDir "/home/user/CDS/OCEAN/test/psf" ?result "tran").

So it seems this change happens after I use the getData command.  Am I doing something wrong?  Is there a better approach?  Or is getData messing me up?

  • Cancel
Parents
  • skillUser
    skillUser over 14 years ago

    Hi,

    I don't think you are doing anything wrong; I think you are right that it is getData that changes the name.  It is a pity that you cannot do this in a single call to plot, but unfortunately you need to expand the list of variables and so you cannot use the apply function to build the call to plot (in other words, you'd like to be able to do this: apply('plot `(,@listOfVariablesToPlot ?expr ,listOfNames ?strip ,listOfStripNums) - I think I've got the syntax right there, but I have not tested this, and it won't work anyway).

    I think that you just need to add the ?expr argument to the call to the plot function so that the name is as you'd like to see it, here's an example:

    
      foreach((sig num name)
                             list(v("/enable") v("/disable"))
                             list(1 2)
                             list("enable" "disable")
        plot(sig ?strip num ?expr list(name))
      )
    

    I have not tested this! You might need to rework it, and possibly use getData again?

    Anyway, I hope that this helps you.

    Regards,
    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 14 years ago

    Hi,

    I don't think you are doing anything wrong; I think you are right that it is getData that changes the name.  It is a pity that you cannot do this in a single call to plot, but unfortunately you need to expand the list of variables and so you cannot use the apply function to build the call to plot (in other words, you'd like to be able to do this: apply('plot `(,@listOfVariablesToPlot ?expr ,listOfNames ?strip ,listOfStripNums) - I think I've got the syntax right there, but I have not tested this, and it won't work anyway).

    I think that you just need to add the ?expr argument to the call to the plot function so that the name is as you'd like to see it, here's an example:

    
      foreach((sig num name)
                             list(v("/enable") v("/disable"))
                             list(1 2)
                             list("enable" "disable")
        plot(sig ?strip num ?expr list(name))
      )
    

    I have not tested this! You might need to rework it, and possibly use getData again?

    Anyway, I hope that this helps you.

    Regards,
    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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