• 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 16835
  • 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
  • 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
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    First of all, your example can't have worked - it had  a quoted list which had v("/enable") in it, and then you were doing getData on the v("/enable") - so it would have failed. I presume it was more like this:

    my_stripAssignment=list(
        list(v("net24") 1)
        list(v("net25") 2)
        list(v("net51") 3)
    )

    first=t
    foreach(signal_name my_stripAssignment
       wave=car(signal_name)
       plot(wave ?strip cadr(signal_name))
       when(first
           displayMode("strip")
           first=nil
       )
    )

    Anyway, a better approach might have been to do this:

    my_stripAssignment='(
        ("net24" 1)
        ("net25" 2)
        ("net51" 3)
    )

    first=t
    foreach(signal_name my_stripAssignment
       wave=getData(car(signal_name))
       plot(wave ?strip cadr(signal_name) ?expr list(car(signal_name)))
       when(first
           displayMode("strip")
           first=nil
       )
    )

    Or better still:

    my_stripAssignment='(
        ("net24" 1)
        ("net25" 2)
        ("net51" 3)
    )
    newWindow()
    displayMode('strip)
    awvPlotWaveform(currentWindow()
        foreach(mapcar sigInfo my_stripAssignment getData(car(sigInfo)))
        ?stripNumber mapcar('cadr my_stripAssignment)
        ?expr mapcar('car my_stripAssignment)
    )

    Regards,

    Andrew.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • SharksFan
    SharksFan over 14 years ago

    Lawrence,

    Thanks for the reply.  I had already done something very similar as my solution.

    I suggest that the documentation for getData be reviewed to explain its behavior in situations like mine. :)

    Regards,

    SharksFan

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • SharksFan
    SharksFan over 14 years ago

    Normally Andrew, you are spot on, but in this case, you are wrong about my example.  My example does indeed work, exactly as I have shown it.

    Thank you for providing the alternatives, especially the last one, however, none of these really address the issue that getData seems to be modifying the argument provided to it.

    Regards,

    SharksFan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    Well, I'm very surprised, because that would mean that your code was doing:

    getData('v("/enable"))

    and that should not work (and did not work when I tried it). Still, I'm happy to be wrong, but I certainly would not want  your code to depend upon this because it is not supposed to work, and is unlikely to be future-proof. It should be (of course):

    getData("/enable")

    Note that there is no bug here. When you call getData without the ?result or ?resultsDir argument, it picks those arguments up from the last openResults() call (or the results from the last completed simulation if you ran a simulation in the same session), and the ?result arg comes from your last call to selectResult(). The waveform object that it creates has the expression property set (on the y-vector) to the be the quoted function that created it. You can always override this by setting drGetWaveformYVec(waveObj)->expression=... 

    Regards,

    Andrew.

    • Cancel
    • Vote Up +1 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