Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 12890
  • 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

How to use stimulus files as parameters in paramAnalysis

vanderpollator

If I have two stimulus files, AC_1.scs and AC_2.scs and I use "AC_stimulus" as a parameter.  How do I sweep these two stimulus files in paramAnalysis?    I know the following oceanscript will NOT work (But syntax is OK)   

stimulusFile( ?xlate nil  strcat(pre_path design_name post_path  AC_stimulus) )

paramAnalysis("AC_stimulus" ?values '("AC_1.scs" "AC_2.scs" ) )

paramRun()

If this scheme of "ASCII inputs as values in paramAnalysis is not working", what I actually want is "How to place two simulation results on the same plot?"   (paramAnalysis should be the most convenient way to do it but I think it may have the other smart way to do it.)

Parents
  • Andrew Beckett

    I don't think it's possible to do a parametric analysis of string names.

    You'd probably have to have a foreach loop, and change the stimulusFile each time - note that each call to stimulusFile() is cumulative (unless you re-initialize the OCEAN session by calling simulator() again), and you can't currently do delete('stimulusFile). See this solution of mine as an alternative.

    Within the loop, you can do your plotting - and then the plots can be on the same graph.

    Kind Regards,

    Andrew.

Reply
  • Andrew Beckett

    I don't think it's possible to do a parametric analysis of string names.

    You'd probably have to have a foreach loop, and change the stimulusFile each time - note that each call to stimulusFile() is cumulative (unless you re-initialize the OCEAN session by calling simulator() again), and you can't currently do delete('stimulusFile). See this solution of mine as an alternative.

    Within the loop, you can do your plotting - and then the plots can be on the same graph.

    Kind 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.