• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Monte Carlo simulations not proceedings for the last few...

Stats

  • Locked Locked
  • Replies 13
  • Subscribers 126
  • Views 3421
  • 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

Monte Carlo simulations not proceedings for the last few jobs/points

sidm
sidm over 1 year ago

Hello All, 

I have been observing my MC simulation which starts of completely fine with multiple jobs running in parallel but towards the end when only a few jobs are left it seems to get stagnated and not moving forward for hours and the number of running jobs reduces to one. 

The schematic simulates completes fast and fine but not the extracted view which halts as indicated in the below  screenshot. Suspending and resuming the job doesn't help. 

In some posts I see suggestion to use LSCS. In my case I am using the LBS job setup mode in IC618 ISR31. I don't see any specific option to select LSCS Vs ICRP. 

Any suggestions/tips will be very helpful. 

thanks 

  • Cancel
  • DomiHammerfall
    DomiHammerfall over 1 year ago

    That the number of running jobs reduces towards the end of a Monte Carlo simulation is normal. The reason is that each worker receives a chunk of grouped Monte Carlo Points, which do not necessarily complete at the same time. You can find an explanation here: https://community.cadence.com/cadence_technology_forums/f/custom-ic-design/55472/virtuoso---jobs

    The distribution method can be find in the Job Policy Setup.
    In ADE Assembler: Options -> Job Setup...
    In ADE Explorer: Setup -> Job Setup...

    Finally, what does the simulation log say about the last few runs? If you go to the Detail view in your result tab, you can rightclick on the runs that have not completed yet and select View Log Messages -> Simulator Log. There, you should be able to see if it is still running or not.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sidm
    sidm over 1 year ago in reply to DomiHammerfall

    thanks for the reply. In the Job Policy Setup I see the below which doesn't seem to give an option to switch between LSCS Vs ICRP. Any suggestions on that ?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sidm
    sidm over 1 year ago in reply to sidm

    As suggested I also checked the log file of the stagnant job which throws Memory report messages  stating Maximum memory size. 

    regards 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DomiHammerfall
    DomiHammerfall over 1 year ago in reply to sidm

    Regarding the job policy: Which tool version are you using? Maybe check the user manual for your version to see if this feature is available and if yes, how to access it through the GUI.

    Regarding the simulator log: There should be much more in it. Did the simulation start at some point? Did it finish? Did it return an error? Was netlisting successful?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sidm
    sidm over 1 year ago in reply to DomiHammerfall

    Thanks , I am using IC618 ISR31. As per my understanding it both  LSCS and ICRP should be part of IC618.

     The netlisting was successful and simulation started but it struggled in some of the job ids as shown below :

    \o *Info*    Run complete for Point ID (2 2572)

    \o
    \o
    \o
    \o
    \o
    \# Memory report: Maximum memory size now 554,625 MB
    \# Memory report: Maximum memory size now 543,715 MB
    \# Memory report: Maximum memory size now 533,016 MB
    \# Memory report: Maximum memory size now 522,527 MB
    \# Available memory: 513,935 MB
    \# Memory report: Maximum memory size now 512,213 MB
    \# Memory report: Maximum memory size now 541,431 MB
    \# Available memory: 597,396 MB
    \# Memory report: Maximum memory size now 598,070 MB
    \# Memory report: Maximum memory size now 637,920 MB
    \# Available memory: 659,927 MB
    \# Memory report: Maximum memory size now 660,601 MB
    \# Memory report: Maximum memory size now 647,584 MB
    \# Memory report: Maximum memory size now 634,880 MB
    \# Memory report: using 790 MB, process size 2,550 MB
    \o *Info* Client has finished evaluating ...
    \o
    \o
    \o *Info* Run complete for Point ID (2 2575)
    \o
    \o
    \o
    \o
    \o
    \# Memory report: Maximum memory size now 684,824 MB
    \o *Info* Client has finished evaluating ...
    \o
    \o
    \o *Info* Run complete for Point ID (2 2578)
    \o
    \o
    \o 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sidm
    sidm over 1 year ago in reply to DomiHammerfall

    thanks I am using IC618 ISR31 and I believe both LSCS & ICRP should be supported.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago in reply to sidm

    I suspect you have (for some strange reason) the CDS_LSCS_DISABLE environment variable set. I have never seen this recommended to anyone (I couldn't find any case/CCR suggesting this) - but that's the only mechanism I can see where the LSCS choice is missing from the UI.

    Can you check (in the CIW):

    getShellEnvVar("CDS_LSCS_DISABLE")

    and see what it returns? If it's anything other than nil, that suggests you have the env var set. Maybe it's set in your environment before starting "virtuoso" or maybe in a wrapper script around virtuoso? Either way, you should not set this, and I suggest you unset/unsetenv it.

    Maybe somebody didn't want the default to be LSCS in the early days of LSCS support, but that's long ago now - and there are other ways of achieving that without disabling it altogether.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sidm
    sidm over 1 year ago in reply to Andrew Beckett

    thanks for the reply. In terms of the log, the simulation starts fine but stagnates at a job id as shown below

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sidm
    sidm over 1 year ago in reply to sidm

    Also I checked the getShellEnvVar("CDS_LSCS_DISABLE") value and it returned  a "nil". Screenshot below for reference : 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sidm
    sidm over 1 year ago in reply to sidm

    One more observation is that I see the LSCS & ICRP options in the GUI when I switch to the ADE Explorer mode for the specific test but not when in the ADE Assembler mode.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
>

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information