I am trying to run multiple ADE XL runs from an ocean script, but each time I run simulations using the ocnxlRun command the script waits until that job is finished. Is there any way to setup the ocnxljob such that it doesn't wait on previous runs to finish before starting the next jobs?
Not at the moment (other than running in a separate ocean or virtuoso session). I filed CCR 548144 for this for another customer. Please contact customer support and request this. This way a duplicate CCR can be filed, which means there is a better indication to R&D of the level of demand for this.
Thanks for the reply. We will put in a support request. It is too bad that functunality has been removed when going from cadence 5 to cadence 6.
I was wondering if a possible work around would be to modify the wrapper that calles spectre. If the wrapper were to start the spectre job, and then report to the ocean script that the job had failed, could the job still run, and the script continue. I would loose the ability to have the script wait on all jobs to finish and process results, but at least I could get all the jobs going. Any thoughts?
Functionality has not been removed here. ocnxlRun() is new in IC61, to correspond to ADE XL functionality. You can still use a non-blocking run() function in an OCEAN simulation, so that functionality has not been removed. I agree that it would be very useful to be able to do a non-blocking ocnxlRun() though, which is why I filed the enhancement before.
Wrapping spectre and getting it to appear to exit might work, but it would rather destroy much of the benefit of ADE XL and OCEAN XL scripts, which allows you to set up measurements and specification limits - these would all fail. So I don't think that's a sensible solution.
What are you actually trying to achieve here? Understanding that might allow me (or someone else) to suggest alternative methodologies.
OK, fair enough. For the second we have a capability called "pre run scripts" which is in IC615 (it's in IC614 under an engineering release flag) which allows you to effectively run a bit of OCEAN before each iteration of the monte carlo. In fact you can run the monte carlo iteration, run a number of simulations (e.g. to "tune" the design), and then finally do you're measurements. This is supported in ADE XL, and also would work from OCEAN XL.
For the first, there's no good solution, except you can still use the monteExpr/monteCarlo/monteRun approach - this is still supported for legacy reasons.
What I would suggest is giving all this info in the service request you're filing, as it gives good justification as to why we should implement ocnxlRun sooner rather than later.
Note you could do it by using (say) ipcBeginProcess() to launch a background virtuoso (or ocean) session which is loading an OCEAN script, and that could run at the same time as the second run. But it's less convenient than being able to do a non-blocking run().
If you run from ADE XL itself, you can do this (submit both jobs simultaneously, without blocking), if you don't mind the UI being open.