Guest
Hi, all,
Sometimes I just don't quite understand why Cadence creates so many
tools/language for the simulaton task. For Star-hspice, basically there
are only two components, simulator and aWaves. In the hspice netlst,
you can include circuit netlist (data statements), model,
analysis/command statement and output statements all together, then
plot the data using aWaves. However, for Cadence simulaton, why do we
need so many tools, and why can't we put something like
phaseMargin(VF("/Vo")) or the voltage difference etc all in the spectre
netlist? Why we have to use OCEAN script to invoke these SKILL
functons?
Seems to me hspice is a more easy, well organized simulation enviroment
than Cadence Spectre (plut ocean, SpectreMDL, ADE......). Can anyone
comment on this?
thank you,
Jay
p.s.: BTW, Cadence's documentation is also hard to use. With hspice
manual, users can easily find and learn how to do different
simulation/characterizaton...
Sometimes I just don't quite understand why Cadence creates so many
tools/language for the simulaton task. For Star-hspice, basically there
are only two components, simulator and aWaves. In the hspice netlst,
you can include circuit netlist (data statements), model,
analysis/command statement and output statements all together, then
plot the data using aWaves. However, for Cadence simulaton, why do we
need so many tools, and why can't we put something like
phaseMargin(VF("/Vo")) or the voltage difference etc all in the spectre
netlist? Why we have to use OCEAN script to invoke these SKILL
functons?
Seems to me hspice is a more easy, well organized simulation enviroment
than Cadence Spectre (plut ocean, SpectreMDL, ADE......). Can anyone
comment on this?
thank you,
Jay
p.s.: BTW, Cadence's documentation is also hard to use. With hspice
manual, users can easily find and learn how to do different
simulation/characterizaton...