Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 4002
  • 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

Simulation crashed - Killed by user

BaaB

This simulation suddenly crashed and there was a line saying that "Killed by user". 
I didn't kill it myself. Does this mean that someone actively killed it?

Parents
  • Dimitra Papazoglou

    If you use ADE-XL or Assembler, The "Killed by user" errors might also appear in case you are firing up more than 1 runs with "Reassign immediately for new run" option enabled in 'Job Policy Setup' form and have set "Run in" option from Series to Parallel in 'Run Options' form.

    In this case, once the second run is fired up then some of the already running jobs in the first run are getting killed forcing spectre to get killed as well (spectre.out reports "Killed by user") and then are reassigned to the new(second) run. When those jobs become available again, then the sim for the "incomplete" points of the first run (where spectre was killed) re-starts again.

    To avoid such cases you need to enable "Wait until currently running points complete" instead of "Reassign immediately for new run" in 'Job Policy Setup' form.

    Not sure if your case is the same but thought it's worth checking.

    Regards

    Dimitra

Reply
  • Dimitra Papazoglou

    If you use ADE-XL or Assembler, The "Killed by user" errors might also appear in case you are firing up more than 1 runs with "Reassign immediately for new run" option enabled in 'Job Policy Setup' form and have set "Run in" option from Series to Parallel in 'Run Options' form.

    In this case, once the second run is fired up then some of the already running jobs in the first run are getting killed forcing spectre to get killed as well (spectre.out reports "Killed by user") and then are reassigned to the new(second) run. When those jobs become available again, then the sim for the "incomplete" points of the first run (where spectre was killed) re-starts again.

    To avoid such cases you need to enable "Wait until currently running points complete" instead of "Reassign immediately for new run" in 'Job Policy Setup' form.

    Not sure if your case is the same but thought it's worth checking.

    Regards

    Dimitra

Children
  • BaaB
    in reply to Dimitra Papazoglou

    Thanks. I am using version  IC6.16-64b.101 and not aware of 'Job Policy Setup' form. I did a quick search and saw that it is in ADE XL. Where can I change it in ADE L? 

  • Dimitra Papazoglou
    in reply to BaaB

    What I'm describing above is for ADE-XL and ADE Assembler. The idea of reassigning job for new runs is not implemented in ADE-L as far as I know.

    So your issue is not the case I'm describing. 

    If the error is seen often without user killing simulation then I'll suggest you to contact Cadence Support (support.cadence.com) so someone can take a closer look. If you are from university then you should ask your professor how you can get support, usually it's through Europractice.

    Regards,
    Dimitra

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.