Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 15981
  • 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

Running the worst case Monte-Carlo Run ( in ADE-XL)

RFStuff

Dear All,

I ran a Montecarlo-Simulation with 5000 runs.

I also found the two worst case runs ( run no # 3042 and # 267).

I then want to run only the same two worst runs.

Could anybody please tell how I can do that.

Kind Regards,

Parents

  • Dear Andrew,

    Thanks a lot for the nice explanation.

    Just for confirmations, could you please see my following queries:-

    1:-

    Without adding the envSetVal(....).

    I didn't add any new instance in the schematic. But I did change the connections. In other words, the instances are kept same.

    So I thinks it will NOT affect the MC parameter set ( i.e. the montecarlo process and mismatch parameters will remain same).

    2:-

    Without adding the envSetVal(....).

    Adding new instances for which no process and mismatch are enabled will not affect the previous MC parameter set.

    3:-

    So ISR6 onwards, adding envSetVal(....), will not affect the previous MC parameter set applied to the previous instances even if you add some more instances for which MC process and mismatch is applied.

Reply

  • Dear Andrew,

    Thanks a lot for the nice explanation.

    Just for confirmations, could you please see my following queries:-

    1:-

    Without adding the envSetVal(....).

    I didn't add any new instance in the schematic. But I did change the connections. In other words, the instances are kept same.

    So I thinks it will NOT affect the MC parameter set ( i.e. the montecarlo process and mismatch parameters will remain same).

    2:-

    Without adding the envSetVal(....).

    Adding new instances for which no process and mismatch are enabled will not affect the previous MC parameter set.

    3:-

    So ISR6 onwards, adding envSetVal(....), will not affect the previous MC parameter set applied to the previous instances even if you add some more instances for which MC process and mismatch is applied.

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.