Run Options of ADE Assembler in Cadence Virtuoso

Dear Senan,

Senan said:

Though I read the help but couldn't figure out the purpose of this option,

This option allows multiple Tests to run in parallel in lieu of series. Hence, if you have two tests defined as "Test_bench_test1" and "Test_bench_test2", with "Run in series" selected, test Test_bench_test1"  is simulated and, upon its completion, test Test_bench_test2"  is simulated. With the "Run in parallel" selected, both tests, Test_bench_test1" and Test_bench_test2" are simulated in parallel.

Does this make sense Senan?

Senan said:

Actually, I am interested in any option that accelerates my simulation especially when I run Montecarlo or corner simulations, not sure if this can help... I usually use Job Setup to run different corners in parallel depending on the Max Jobs I set

Did you happen to view the Help section at URL:

/tools/virtuoso/20.1.ISR21/doc/Explorer/chap8.html#MC_standard

where you can set the number of iterations to that required for your statistic limit and not for a fixed number of iterations? This might save you simulation time.

There are many other ways as well, but I am not familiar with the specifics of you simulation setup to provide any general comments - sorry!

Shawn

Most of the time people leave the Run options alone and solely control the number of jobs on the job options/policy forms. The series/parallel tends to be more useful when you are pressing the run button more than once. In series mode it will run through all the jobs of the previous submission first (at least until you have some job capacity free within the allowed number of parallel jobs on the job policy) and then start submitting the simulations from the second press of the run button. With "parallel" mode it will aim to run jobs from the first and second press of the run button in parallel, sharing the available number of jobs between them.

For Monte Carlo the job policy also affects the number of parallel simulations, and normally it will group the Monte Carlo points within those parallel simulations for efficiency (there is an option when using LSCS to specify the maximum number of sequential jobs run in a single invocation of spectre so that you can force separate runs to occur - can be useful if you have some points in the distribution that take much longer to simulate than others due to convergence difficulties for example).

Andrew

Most of the time people leave the Run options alone and solely control the number of jobs on the job options/policy forms. The series/parallel tends to be more useful when you are pressing the run button more than once. In series mode it will run through all the jobs of the previous submission first (at least until you have some job capacity free within the allowed number of parallel jobs on the job policy) and then start submitting the simulations from the second press of the run button. With "parallel" mode it will aim to run jobs from the first and second press of the run button in parallel, sharing the available number of jobs between them.

For Monte Carlo the job policy also affects the number of parallel simulations, and normally it will group the Monte Carlo points within those parallel simulations for efficiency (there is an option when using LSCS to specify the maximum number of sequential jobs run in a single invocation of spectre so that you can force separate runs to occur - can be useful if you have some points in the distribution that take much longer to simulate than others due to convergence difficulties for example).

Andrew

Thank you so much Andrew, it is now clear for me