subgold
|
let’s say I do a 1000-run MonteCarlo simulation to check the performance of a circuit, and find some malfunctions, which occur at only very few runs (maybe in 1 or 2). then I rerun the simulation at that specific run to figure out what the problem is, and find out a solution.
It could often happen that the solution is inadequate, or I didn't understand the problem completely, the error could disappear in that run number but appear at another one, after the netlist change. therefore, in order to check if the solution works, I need to do again 1000 runs of MonteCarlo simulation, or even repeatedly.
Furthermore, more often than not, I don't expect to solve the problem all in once, but have to do some debugging instead, i.e. to exclude all the potential errors one by one. In this case, I also have to run many times of 1000-run MonteCarlo.
in either case, the MonteCarlo verification becomes very time consuming and inefficient, owing to the iteration of the 1000 runs. so I am wondering if anybody has encountered the similar situation, and has some constructive suggestion to improve the efficiency of the MonteCarlo verification, either from a general design methodology view, or from a technical point of view (e.g. are there any tricks to maneuver in the simulator, etc.) and would appreciate any advise.
thanks in advance.
|