ADEXL: Preloading Multiple Runs

Zakir,

I don't understand why you are making this so complicated. Why can't you just set up the 8 corners  you want and hit the run button. Depending on the Job Policy (Options->Job Setup) it will control how many jobs run at once, so I'm at a loss to understand what your problem is. I see no need to manually set up the runs one at a time as you describe.

Regards,

Andrew

Andrew, Under "corners" I can make up my corners. By default, there is one there, nominal. I make one more, calling it C1. C1 has 4 loops or cases built into it. I make another corner, calling it C2. C2 has 16 loops built in. If I select all 3 corners, nominal, C1 & C2 , then a total of 21 sims start running and they are all put together in one intercative session. When I look at the data, I see a column for nominal, another column for C1_0, C1_1, C1_2, C1_3, C2_0, C2_1  and so on until C2_15.

But that is not what I want to see. I want one session run with only nominal, another with C1 ( where i then get to see C1_0 , C1_1, C1_2 & C1_3) and another session with C2_0 through C2_15.

Not sure if I am explaining this well.

I don't really see why you want to do this in separate interactive runs, but currently you probably don't have much choice other than enabling them one at a time. There's something that is coming in the future which would make this automatable (if that's a word), but it's not there currently. You could sort of do it using setup states and then creating an OCEAN script from the setup states to script running through each of the corners in turn, but not sure that's really what you want.

Why do you want to run them separately?

Regards,

Andrew.

I do that to check the performance at different filter corner frequencies. At the top level the amplifier can handle different filter corners and it does this by having the rc settings different for different filter corners.

So when the design is all done I need to run a sanity check. For each filter corner, say C80 for 80MHz filter corner, I run process, voltage and temp variations. So C80 is a corner that iterates through 16 possibilities (of pvt).  I then can see/plot the data for this one filter corner, making sure  iip3 is good, stability is good, transients are good etc. There is a whole suite of things to check for at this one filter corner. I

Then I have to change some variables to program it for a different  filter corner. I save all this into a different corner case, say C40. Now I need to know when I program it for 40Mhz, how well the design holds for PVT. Overall  I have like 5 filter corners.

I can then kick off these "top level corners" one by one, so I can analyse the data within each top-level corner

Each time I tweak something, I need to go run all these again and view the pvt data for each top-level corner.

Or is a there a better way?

One other approach would be to copy the test for each filter "corner" and change the variables locally on each test.  This is a bit of a pain if the tests are changing, but would work fairly well if they are stable.  You could then run these tests over your 16 pvt corners and access the results separately, but in the same history item.