Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 15080
  • 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

how to observe the transistor dimension variation in monte carlo simulation

imagesensor123

 Hello,

      I know that people can observe some transistor parameter changes during the monte carlo simulation, but there is no options to let user choose width or length of a transistor as a observed parameter, what's your method?

by the way, my approach is to build an expression including some parameters picked up by "opt" in calculator, but the transistor size is not there.

generally, are all the transistors in a circuit applied the same variation in a simulation? or each transistor has its own variation in the simulation? I noticed that some people mentioned one model card and multiple model card, is this related to the transistor dimension variation?

regards,

zfeng 

Parents

  • Zfeng,

    You can access the size of the transistor using pv("/I7/M5" "w" ?result 'instance) (same for "l"). That's the parameter as define in the netlist. If you want the effective width and length, that would be pv("/I7/M5" "weff" ?result 'output) (and "leff" for length) The parameters that are output are in the Output Parameters section of "spectre -h bsim4" (or whatever model you're using). For example:

    ================= 
    Output Parameters
    =================

    1       weff (m)          Effective channel width (alias=lx62).
    2       leff (m)          Effective channel length (alias=lx63).
    3       weffcv (m)        Effective channel width for CV (alias=lx64).
    4       leffcv (m)        Effective channel length for CV (alias=lx65).
    5       vfbsd (V)         Flat band Voltage between the gate and Drain/source diffusions (alias=lx75).
    6       rgbi (Ohm)        Gate bias-independent resistance.
    7       adeff (m^2)       Effective drain area.
    8       aseff (m^2)       Effective source area.
    9       pdeff (m)         Effective drain perimeter.
    10      pseff (m)         Effective source perimeter.

    However, it's quite likely that your monte carlo models are not varying the weff/leff of the device, but instead varying the vt or some other parameter of the model. So you might not see anything nevertheless.

    Regards,

    Andrew.

Reply

  • Zfeng,

    You can access the size of the transistor using pv("/I7/M5" "w" ?result 'instance) (same for "l"). That's the parameter as define in the netlist. If you want the effective width and length, that would be pv("/I7/M5" "weff" ?result 'output) (and "leff" for length) The parameters that are output are in the Output Parameters section of "spectre -h bsim4" (or whatever model you're using). For example:

    ================= 
    Output Parameters
    =================

    1       weff (m)          Effective channel width (alias=lx62).
    2       leff (m)          Effective channel length (alias=lx63).
    3       weffcv (m)        Effective channel width for CV (alias=lx64).
    4       leffcv (m)        Effective channel length for CV (alias=lx65).
    5       vfbsd (V)         Flat band Voltage between the gate and Drain/source diffusions (alias=lx75).
    6       rgbi (Ohm)        Gate bias-independent resistance.
    7       adeff (m^2)       Effective drain area.
    8       aseff (m^2)       Effective source area.
    9       pdeff (m)         Effective drain perimeter.
    10      pseff (m)         Effective source perimeter.

    However, it's quite likely that your monte carlo models are not varying the weff/leff of the device, but instead varying the vt or some other parameter of the model. So you might not see anything nevertheless.

    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.