Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 12938
  • 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

reading sens1 values from dcOpSens is very slow

Marcel Preda

Hi *,

I'm trying to read some data from a dc sensitivity analysis.

For now I have two nested foreach loops something like

foreach(refSig refSigList
   foreach(instName instDataTable

      // some code
       sensVal = getData(strcat("sens1:" refSigSim "," instName ":dc") ?result "dcOpSens")
      // some code  
  )
 )

But it is very slow, for 2 X 1838 combinations it takes ~22seconds shown in profiler. And most of it > 21seconds is spent in getData().

Is there other faster method to get this data?

What I've noticed is that from VIVA results browser if I'm generating the table with all signals and associated values it is much faster , less than 14 seconds.

Best Regards,

Marcel

  • Hi Marcel,

    I'm not sure this will be any quicker, but I'd do it as follows:

    selectResult('dcOpSens)
    dataType=car(dataTypes()) ; probably just "sens1Req")
    foreach(output outputParams(dataType)
      pv("sens1" output)
    )

    However, this seems fairly slow for me too, and I only have a tiny example (that said, there were 1135 outputs in my case and it was less than a couple of seconds). You probably will need to contact customer support. Unfortunately PSF is not fantastic for the case when you have a lot of such scalar values - so it may need work to update the result format to better handle this, or it might be possible with some further code optimisation on our side.

    Regards,

    Andrew.

  • in reply to Andrew Beckett

    Hi Andrew,

    It is perfect for now: run-time decreased 3 times.

    I have to run it on a bigger testcase. 

    Best Regards,

    Marcel

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.