Do you have to specify the <antype> when using the .probe statement in HSPICE?

[klouie741984]

The manual for hspice specifies the format of the .probe statement to be:
.PROBE antype ov1 … <ov32>

The antype is specifying the type of analysis like DC or TRAN. I have seen HSPICE scripts with
.probe tran v(*)
and statements like
.probe v(*)
where the antype is not specified. Do we need to specify the antype? What is the difference if we include it or not? This question may also apply to the other commands like .print which follows the same format in the manual.

 

[pancho_hideboo]

Re: Do you have to specify the <antype> when using the .probe statement in HSPICE?

.probe tran v(*)
.probe v(*)
..........................................................
What is the difference if we include it or not?

Assume that you have multiple analysis statements such as ".dc", ".ac" and ".tran" in one netlist.

Former is valid for results of ".tran".
Latter is valid for results of .dc", ".ac" and ".tran".

 

[klouie741984]

Re: Do you have to specify the <antype> when using the .probe statement in HSPICE?

So if I don't include <antype>, so .probe (v*), then it will probe all the analysis statements like .dc, .ac, .tran if you have all 3?
So in other words, if you have multiple analysis statements, designers use a single .probe statement like
.probe v(*),
instead of 3 lines
.probe ac v(*)
.probe dc v(*)
.probe tran v(*)

in order to save lines.

 

[pancho_hideboo]

Re: Do you have to specify the <antype> when using the .probe statement in HSPICE?

So if I don't include <antype>, so .probe (v*), then it will probe all the analysis statements like .dc, .ac, .tran if you have all 3?

Yes.

Consider followings.

.ac
.tran
.probe v(net1) v(net2) v(net3)
.probe ac v(net4) v(net5)
.probe tran v(net6) v(net7)

 

[klouie741984]

Re: Do you have to specify the <antype> when using the .probe statement in HSPICE?

That makes sense. Thanks a lot!