Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13086
  • 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

ADEGXL global optimisation runs only 9 jobs in parallel

vamshiky

Hi,

 I am trying to use global optimsation for finding w/l of a mosfet while forcing the vgs-vth to be in some range like 100mv to 105mv.

In this setup I notice that only 9 sims are launched at a time, though the job policy which I use can take upto 100.(with adexl) and hence tales a lot of time to complete the optimisation.

 

Is there any other setting which will speed up this.

 

Thanks,

Vamshi

 

Parents
  • Hi Tom,

    Not really.  To elaborate this is what I have tried .

    I have 24 mosfets with Length defined  in the schematic with each of them having 'finger width' and 'number of fingers' as parameters. so total of 48 variables.

    In the global variables section each of them are given with a range like 2:2:20 etc.

    And when I launch global optimisation(with spec of vgs-vth in a range) I see that there is a huge design space ( about 4e+30 of runs)

    However I still notice only 9runs in parallel.


    I am looking  for an efficient way of optimising the sizes here, so that I can tabulate widths for different 'vgs-vth' of a device for a given length.

    Thanks,
    Vamshi
Reply
  • Hi Tom,

    Not really.  To elaborate this is what I have tried .

    I have 24 mosfets with Length defined  in the schematic with each of them having 'finger width' and 'number of fingers' as parameters. so total of 48 variables.

    In the global variables section each of them are given with a range like 2:2:20 etc.

    And when I launch global optimisation(with spec of vgs-vth in a range) I see that there is a huge design space ( about 4e+30 of runs)

    However I still notice only 9runs in parallel.


    I am looking  for an efficient way of optimising the sizes here, so that I can tabulate widths for different 'vgs-vth' of a device for a given length.

    Thanks,
    Vamshi
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.