Stats

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

 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?

Parents
  • SharksFan

    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

Reply
  • SharksFan

    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

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.