Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 2510
  • 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

Release of license from suspended Monte Carlo+APS

jehh

Hi,

We have a setup, where jobs are send to an LSF (running SGE). We then manage licenses for simulations on a priority based system. However, we are experiencing some troubles with Monte Carlo runs specifically.

We have tried and tested suspending APS aps++ jobs, Spectre X jobs and regular Spectre jobs just fine. The jobs are suspended, and licenses released. However, with MC runs, the job is effectively suspended, however it doesn't release the licenses?

Is there some option, like the lsuspend that needs to be set? I've tried debugging quite a bit, but unsucessful, and I am at a dead-end in terms of more debugging.

We are running IC6.1.8, and Spectre 20.1

BR,

Christian

Parents

  • Hi Christian,

    Are you seeing the +lsuspend or +lsusp argument in the command line if you look at the Spectre log file? In current versions, you have to set this via Setup->Environment on each test - we're adding the ability to override it centrally if preferred, but that's coming in a later IC6.1.8 ISR (ISR17). So for now, it's stored in the test setup, so you need to check that it's enabled.

    Regards,

    Andrew.

  • in reply to Andrew Beckett

    Hi Andrew,

    I've tried to figure out the exact spectre call MonteCarlo makes, I assume it is found under **/path/to/maestro/result/test_name/**/groupRunDataDir/psf/spectre.out? In the beginning I do see the +lsusp, as I would expect (we've set it from an environmental variable).

    C+P from the log file:

    Command line:
        /usr/pack/spectre-20.10.068-cgh/tools.lnx86/bin/spectre -64  \
            input.scs +escchars +log ../psf/spectre.out -format psfxl -raw  \
            ../psf +aps +lqtimeout 0 +lqmmtoken -maxw 5 -maxn 5 +lorder  \
            MMSIM +lsusp -env ade -ahdllibdir  \
            /**savepath redacted**/maestro/results/maestro/MonteCarlo.11/sharedData/lscsJob120/ahdl/input.ahdlSimDB  \
            +logstatus

  • in reply to jehh

    That's odd then. I can't think why this wouldn't work - I would suggest you contact customer support. There are sometimes some DRM-related settings to ensure that suspending a job in your DRM system (SGE in this case) uses SIGTSTP rather than SIGSTOP to suspend the job, but I'd expect that to be the same for all jobs, not just Monte Carlo.

    Regards,

    Andrew

Reply
  • in reply to jehh

    That's odd then. I can't think why this wouldn't work - I would suggest you contact customer support. There are sometimes some DRM-related settings to ensure that suspending a job in your DRM system (SGE in this case) uses SIGTSTP rather than SIGSTOP to suspend the job, but I'd expect that to be the same for all jobs, not just Monte Carlo.

    Regards,

    Andrew

Children

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.