skill to detect ADEXL options

 Ive switch everthing over to public calls and it does work but I get an error when ultrasim is selected so how can I query the ADEXL simulator option so I can bypass this routine if ultrasim is selected?

 
p, li { white-space: pre-wrap

ERROR (ADE-5021): asiEnvGetVar: Variable 'turboOpts mtOption' is not declared for tool 'UltraSim21'.

ERROR (ADE-5021): asiEnvGetVar: Variable 'turboOpts uniMode' is not declared for tool 'UltraSim21'.

ERROR (ADE-5021): asiEnvGetVar: Variable 'turboOpts psrSwitch' is not declared for tool 'UltraSim21'.

 My wild guess without trying it (just from a quick scan of the documentation would be):

asiGetSimName(asiSession)

and then have a conditional statement using that:

when(asiGetSimName(asiSession)=="spectre"
  ...
)

Regards,

Andrew.

There is also asiGetToolName, both work but with different results shown below. Not sure if the quotes mean that ones a string the other is not?? Do you recommend using a when instead of an if/then? Is there a whenNot or something. I was thinking about doing if toolName=! "UltraSim" then

simName=asiGetSimName(asiSession)
println(simName)

==> "UltraSim"

toolName=asiGetToolName(asiSession)
println(toolName)

==> UltraSim

asiGetToolName is not public (it's not documented). So use asiGetSimName. The difference is that one returns a string (asiGetSimName), and one returns a symbol - for details on the difference, I suggest either reading the SKILL Language User Guide, or better still attending some SKILL Language training.

when() is fractionally more efficient (and more readable) than if() with a then part only. The opposite is unless(). I wouldn't have thought using toolName!="UltraSim" makes sense, because your code is specific to spectre - so if the simulator is hspiceD, ams, or anything else, it will also fail... surely it's best to use when(simName=="spectre" ...)

Regards,

Andrew.

 asiGetSImName works.   There are actually quite a few simulators that need to addressed, specrtre and aps.   Can a when(   use an   "OR" funciton   when(  spectre || aps )?

 Thanks

Aside from the fact that "aps" as a simulator choice in ADE is obsolete and should not be used any more (it even tells you this), you really should read the SKILL Language User Guide, which covers absolute basics like this.

It doesn't matter whether you're using when() or if(), or unless() - they all take a conditional expression. You could do:

simName=asiGetSimName(asiSession)
when(simName=="spectre" || simName="somethingElse" ...
)

or

when(member(simName '("spectre" "somethingElse" "yetAnotherMatch"))
  ...
)

The second checks to see whether the value is the member of a list.

Regards,

Andrew.

This script is only triggered by ADEXL so APS should be valid.   For ADE, we use the HPO form for the simulator settings.

Huh? "aps" is an obsolete simulator choice, regardless of where you pick it - it is equally obsolete in ADE XL as it is in ADE L. In ADE XL you would also use "spectre" as the simulator, and the High Performance Options form to pick aps as the simulation mode.

Regards,

Andrew.

Lets backup a bit.....are you saying that APS is no longer valid as a executable or as an enhancer   spectre +aps   ?   I thought the APS option was faster than Turbo but used the same tokens count.    You can select the APS two ways:

1)  ADEXL-->test-->simulator

2)  ADEXL-->test editor which pops the ADE panel then either the simulator or the HPO form.

Is this still correct?

What I'm saying is that you should not use ADE L->Setup->Simulator/Dir/Host and set the simulator to "aps", nor should you do ADE XL->test->simulator and set that to "aps". The reason being that this interface was added initially to avoid breaking anything in spectre, but it does not support anything other than DC or transient analyses. It will be removed at some point in the future.

The way to do it is to set the simulator to "spectre", and then set the "high performance options" form to "aps". The APS option on this form is definitely worth using - you'll get good speed improvement. Since APS (this way) supports all spectre analyses, having it as a separate simulator choice made no sense - better to be an option to spectre - hence the "High Performance Options" form.

The plan is also to drop "Turbo" ultimately. With MMSIM101, APS on a single core takes the same number of tokens as "Turbo".

The "aps" executable is essentially equivalent  to "spectre +aps" from the command line - it's kept for legacy for anyone with existing scripts.

So given this, asiGetSimName() should never return "aps" unless you've used obsolete settings in ADE L or XL.

Regards,

Andrew.