Do license queueing for AMS

Richard,

Did you type in just '-licq -spectre_args "+lqt 0" ' in the additional options field, or did you include "irun" as part of the string. If so, that's your mistake. The irun is shown in the solution for users who are running for the command line. The ADE interface will use irun (assuming it's in OSS/irun mode) itself and so it doesn't make sense to put the command itself in the additional options - you'd end up with ADE submitting:

irun various options generated by ADE irun -licq -spectre_args "+lqt 0"

which would clearly be wrong...

Regards.

Andrew.

 Hello, Andrew

 Actually, I am running a simulation by using AMS with  APS as a solver.

AMS and APS both have additional options fields. I was wondering if I need

to fill in  '-licq -spectre_args "+lqt 0" ' for AMS and APS.

Plus, why does spectre take so long like 10 minutes to load state ?

Sometimes, it loads state quickly. I am talking about the same simulation file.

Best Regards,

Richard.

Richard,

You only need to fill it into the AMS additional options.

Which "load state" are you talking about? Is this loading state in ADE? If so, I can see no reason why this should take 10 minutes (in fact I can't think of any loading of state which should take that long). You should file a service request to get this investigated.

Regards,

Andrew.

 Hello, Andrew

 Actually , I filled it into APS additional options but it turned out to an error happened. 

Now, you already gave me the answer.

I was trying to say the loading state in ADE. I should make my description more clear.

Loading of state takes a long time when I start simulating with LPE results via config view.

If I run simulations with schematics only, it takes like 1 minute to load a state.

I am not sure it is normal for simulating with LPE.

Thanks

Richard.

Richard,

You didn't say which version you were using, but if it's IC5141, I know there were some issues with speed with large extracted views for various operations in ADE - the workaround was to make sure you explicitly opened the extracted view in a window first before working in ADE (otherwise it was repeatedly opening and closing the extracted view, and the closes were causing it to be purged from memory each time - having the window open prevents that from happening). This was particularly a problem if you have a lot of outputs from the extracted view being saved/plotted.

That said, I wouldn't have expected it to take a minute to load the state anyway in normal cases.

The issue above with extracted views was resolved in IC61.

Regards,

Andrew.