Calculating the std deviation and mean along the y axis on a family of waveform

I can't quite see what the sweep variable is in the legend, but if you plot swapSweep(inlEndpoint(Iout_sink) "mcp") does it plot the 10 points across the x-axis and separate traces for each vcode? If so, you should be able to then do stddev() or average() over the result to get what you want.

I'm assuming inlEndpoint is some custom function anyway - I don't think it's something we provide as far as I can tell.

Andrew.

Hi Andrew:

Sorry, maybe I should give more background. I'm new to skill programming so please bear with me if I make any mistake.

I wrote the inlEndpoint with the help on examples in the custom skill library. The code is shown here.

(defglobalfun inlEndpoint (wave)
        (cond
             ((drIsWaveform wave)
             /* get the x,y axis vector of the waveform*/
             (setq xVec (drGetWaveformXVec wave))
             (setq yVec (drGetWaveformYVec wave))
             /*get length of the vector, error shows up if I put extra parenthesis at the outside?*/
             setq(len (drVectorLength xVec))

             /*get first element*/
             setq(firstEle (drGetElem yVec 0))
             setq(adjustedOffset firstEle)
             /*get last element*/
             setq(lastEle (drGetElem yVec len-1))
             adjustedLsb = (lastEle - firstEle) / (len - 1)

             (setq newY (drCreateVec (drGetWaveformYType wave) len))

             (for pos 0 (sub1 len)
                 (drAddElem newY ( drGetElem(yVec pos) - (adjustedOffset + adjustedLsb * pos)) / adjustedLsb )
             )
             (drCreateWaveform xVec newY)
         )
        ((famIsFamily wave)
             (famMap 'inlEndpoint wave)
             )
             (t
             (error "inlEndpoint: cannot handle %L\n" wave)
             )
)
)

I'm running monte carlo run with multiple corners and the setup is shown in the figure

When I plot the inlEndpoint(iout_sink) it's like the figure in the main post. 

I tried the swapSweep(inlEndpoint(Iout_sink) "mcparamset" 10), and I noticed it changes the x axis to mcparamset, but I want to maintain the x axis the same.

What i'm trying to do is I have 4 corner runs with 10 monte carlo samples, where I have a total of 40 waveforms (10 waveform for a single corner run)

In the end I want to combine the 10 waveform for a single corner into 1 waveform, so total I want to output 4 waveforms.

I'm trying to use a single corner for example. I want to do calculations along the y axis for the mean and variance.

waveform0Yvec [0a,0b,0c]

waveform1Yvec [1a,1b,1c]

waveform2Yvec [2a,2b,2c]

..

...

waveform9Yvec [9a,9b,9c]

-> output to 

waveformOutputYVec[mean of (0a, 1a...9a), mean of (0b,1b...9b ), mean of (0c, 1c...2c)] while mantaining the x-axis

I hope i'm clear in my explanations what i'm trying to do... I don't know if there is any other ways to do this 

The pesudo code I can think of is the following (Not sure if it helps...)

Function definition : OutputMeanAndVaiance (takes familywaveform with multiple corners(4) and multiple monte carlo runs(10)) -> output a familywaveform with multiple corners(4)

for every corner {

    take the corresponding 10 monte carlo waveform

             create meanSigmaYVec with length of the XVec of waveform

             for(index = 0; i < xVector.length; i++) {

                    sum = 0;

                    square = 0;

                    for(monteNumber = 0; monteNumber < 10; pos++) {

                             sum += waveformof[monteNumber]Yvec[index];

                             square += waveformof[monteNumber]Yvec[index] ^ 2;

                    }//end monteNumber

              mean = sum / 10;

              sigma = square/10 - mean^2;

              meanSigmaYVec[index] = mean + sigma;

              }//end traversing the xVec

             plot a waveform with meanSigmaYVec and original XVec

}//end for every corner

Thanks

I know that you don't want to have mcparamset as the x-axis in your plots, but the reason for my suggestion is that if you have a set of curves, then the average or stddev functions will give you the mean or standard deviation across the x-axis. You'll then get one value for each y curve, so I think you'll then get a curve of the mean across the mcparamset with the x-axis being vcode again. Hopefully if all is OK, it will also give you one of these curves for each corner. I don't have something similar to you to test with, but I think it should work.

So I don't believe any custom code is needed. The swapSweep is just to allow you to change around the axes so that you can pick which is the x-axis to find the mean or standard deviation across, and then that number will be plotted against the next outer sweep variable. Worst case you might need to swapSweep the result of the average/stddev to change the axis back to vcode again (if it happens to plot versus corner instead, say), but hopefully that's not necessary.

If this doesn't make sense or you can't make it work, please contact customer support. Point the application engineer to this thread if you do that, and mention that I'd be happy to help on this (by the way, many fo the examples in the calculator function code library come from me!)

Regards,

Andrew

Hi Andrew:

The steps i'm following is like the follow,

1. plot the inlEndpoint(iout_sink), I'm running a DC simulation with vcode sweeping from 0 to 1023, and don't see it available in the Sweep Variable

2. plot swapSweep(inlEndpoint(iout_sink) "mcparamset" 500 )

3. plot stddev(swapSweep(inlEndpoint(iout_sink) "mcparamset" 500 )), The x-axis changed to temperature when I plot it, but the values are correct as it's taking the std deviation of code 500 for the 4 corners. I couldn't chage the x-axis back to vcode with the swapSweep as it seems like this variable doesn't exist.

Not sure if i'm doing it correctly, I don't understand the structure of the familywaveforms at the start, seems like there are a lot of parameters going on with corner simulation with monte carlo run.
For now henker's solution works ok with me so I'll use that solution for now, I'll go through the materials online to try and understand the various data structures for skill.

Thanks

Thanks for the reply. I wouldn't expect to see vcode in the sweep variables when you do the swapSweep, because vcode already is the x-axis and so there's no point changing it to what it already is. What's a bit strange though is that it's not showing up in the legend after that, so something seems awry.

Anyway, glad you've got a way forward with henker's solution (I didn't check henker's code in detail due to lack of time at the moment). Writing something specific in SKILL was always an option here - I was just trying to see if there was a way of doing this with built-in functionality. I'm always happy writing SKILL, but since I always say that you should check first if something exists already in the tools, I was trying to practice what I preach!

Andrew.

Thanks for the reply. I wouldn't expect to see vcode in the sweep variables when you do the swapSweep, because vcode already is the x-axis and so there's no point changing it to what it already is. What's a bit strange though is that it's not showing up in the legend after that, so something seems awry.

Anyway, glad you've got a way forward with henker's solution (I didn't check henker's code in detail due to lack of time at the moment). Writing something specific in SKILL was always an option here - I was just trying to see if there was a way of doing this with built-in functionality. I'm always happy writing SKILL, but since I always say that you should check first if something exists already in the tools, I was trying to practice what I preach!

Andrew.