Stats

  • Locked Locked
  • Replies 8
  • Subscribers 127
  • Views 19379
  • 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

set up parametric simulation to utilize multiple cores

whlinfei

Hi,

 

I am using Cadence 6.1.5 and spectre to run transient simulations. I wish to run parametric simulations on a few variables in my design.

The workstation I have access to has 32 cores and typically more than half of them are free.

May I know how I can set the parametric simulations in a way that parallel transient simulations can be run simutaneously by different cores? Like each core runs a simulation in which the variables take on different values?

 Thank you in advance.

Regards,

Whlinfei 

Parents

  • Using ADE XL is the simplest approach, but another possibility is to set up distributed simulation in ADE L - doesn't need to be very distributed though ;-)

    For example, I do this sometimes on my machine (mainly for testing or demo purposes). Create a file, queue_config, with this contents:

    myqueue 1
    localhost 4

    In this file, the first line gives the name of the queue and the number of machines contained within that queue (I just used localhost, as that's always the local machine). Then the number after the localhost is the number of parallel jobs that can be run in that queue. You can define multiple queues if you want, or involve other machines - for that read the Distributed Processing guide in the documentation.

    Then run "cdsqmgr /path/to/queue_config".

    Then do:

    setenv LBS_CLUSTER_MASTER localhost

    or

    export LBS_CLUSTER_MASTER=localhost

    depending on the shell you're using (csh for the first, bash/ksh for the second).

    And then run virtuoso - and in ADE L, under Setup->Simulator/Dir/Host pick distributed simulation.

    That's it really - not too complicated. 

    That said, if you are sharing the compute resource with others, this should be set up more centrally because only one cdsqmgr can be run at once (see the docs for more detail, again). If you need to change the config file, you'll need to kill cdsqmgr and restart it.

    But the ADE XL approach is probably simpler!

    Regards,

    Andrew.

Reply

  • Using ADE XL is the simplest approach, but another possibility is to set up distributed simulation in ADE L - doesn't need to be very distributed though ;-)

    For example, I do this sometimes on my machine (mainly for testing or demo purposes). Create a file, queue_config, with this contents:

    myqueue 1
    localhost 4

    In this file, the first line gives the name of the queue and the number of machines contained within that queue (I just used localhost, as that's always the local machine). Then the number after the localhost is the number of parallel jobs that can be run in that queue. You can define multiple queues if you want, or involve other machines - for that read the Distributed Processing guide in the documentation.

    Then run "cdsqmgr /path/to/queue_config".

    Then do:

    setenv LBS_CLUSTER_MASTER localhost

    or

    export LBS_CLUSTER_MASTER=localhost

    depending on the shell you're using (csh for the first, bash/ksh for the second).

    And then run virtuoso - and in ADE L, under Setup->Simulator/Dir/Host pick distributed simulation.

    That's it really - not too complicated. 

    That said, if you are sharing the compute resource with others, this should be set up more centrally because only one cdsqmgr can be run at once (see the docs for more detail, again). If you need to change the config file, you'll need to kill cdsqmgr and restart it.

    But the ADE XL approach is probably simpler!

    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.