Stats

  • Locked Locked
  • Replies 8
  • Subscribers 143
  • Views 20375
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Measures with spectre syntax (OCEAN measure)

AnnaS
Hello. Just wondering if someone could be able to help me to use FindWhen measure for DC analysis with spectre syntax.

Here is  corresponding hspice sample which I am trying to convert:

.MEASURE vtsat_sp find VTH(MN2) when v(vg1)=0.2

.MEASURE idsat    find i(vd3)   when V(Vg1)=0.2
 

Thanks in advance.

Anna

 
Parents

  • Hi Anna,

    Better late than never, but I ran your example (changing the models, and just sticking to one alter to keep it simple), and the expression was:

    value(v("MN2:vth" ?result "sweep1_srcSweep-sweep") 0.2   )

    Note I had to put:

    save *:vth sigtype=dev

    in the netlist. Exactly what the ?result name will be depends on how the sweep was done, but you should be able to see this in the ViVA/Wavescan results browser. Since the x-axis is pvar, which is the voltage on source Vg1, just taking the value at 0.2 is equivalent to your measurement. 

    For the current, it would be:

    value(i("Vd3:p" ?result "sweep1_srcSweep-sweep") 0.2   )

    Regards,

    Andrew.

Reply

  • Hi Anna,

    Better late than never, but I ran your example (changing the models, and just sticking to one alter to keep it simple), and the expression was:

    value(v("MN2:vth" ?result "sweep1_srcSweep-sweep") 0.2   )

    Note I had to put:

    save *:vth sigtype=dev

    in the netlist. Exactly what the ?result name will be depends on how the sweep was done, but you should be able to see this in the ViVA/Wavescan results browser. Since the x-axis is pvar, which is the voltage on source Vg1, just taking the value at 0.2 is equivalent to your measurement. 

    For the current, it would be:

    value(i("Vd3:p" ?result "sweep1_srcSweep-sweep") 0.2   )

    Regards,

    Andrew.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.