• 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. Mixed-Signal Design
  3. Spectre distributed simulation using ssh

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 64
  • Views 15776
  • 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

Spectre distributed simulation using ssh

rsashwinkumar
rsashwinkumar over 7 years ago

I have a netlist (with parasitics extracted using calibre)  for an ADC and I need to run a long transient simulation. In order to reduce the simulation time, I am trying to run a distributed simulation using ssh.  I have the netlist in a network location. And I am running the command from a machine (sys1) with the simulation running in sys2 and sys3. I have done the following : 

1. Added the hostnames  and  disabled firewall in all the three machines.

2. Installed openssh in all three, synced their times to a NTP server

3. I run the following command in the terminal from sys1

    spectre -64 /home/input.scs +escchars +log /home/psf/spectre.out -format psfxl -raw /home/psf +aps +mt=8 +cktpreset=sampled +postlayout +lqtimeout 900 -maxw 5 -maxn 5 +dp=ssh +hosts "sys2:8 sys3:8"

It loads all the model files, compiles them and when the simulation is about to start I get the following error

DC simulation time: CPU = 35.1084 s, elapsed = 10.9721 s.

Opening the PSFXL file /home/psf/tran.tran.tran ...
Important parameter values:
    start = 0 s
    outputstart = 0 s
    stop = 820 us
    step = 820 ns
    maxstep = 500 ps
    ic = all
    useprevic = no
    skipdc = no
    reltol = 1e-06
    abstol(V) = 1 uV
    abstol(I) = 1 pA
    temp = 40 C
    tnom = 27 C
    tempeffects = all
    errpreset = conservative
    method = gear2only
    lteratio = 10
    relref = alllocal
    cmin = 0 F
    gmin = 1 pS
    rabsshort = 1 mOhm


===================================================================================
=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
=   EXIT CODE: 139
=   CLEANING UP REMAINING PROCESSES
=   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
[proxy:0:0@sys2] HYD_pmcd_pmip_control_cmd_cb (./pm/pmiserv/pmip_cb.c:883): assert (!closed) failed
[proxy:0:0@sys2] HYDT_dmxu_poll_wait_for_event (./tools/demux/demux_poll.c:77): callback returned error status
[proxy:0:0@sys2] main (./pm/pmiserv/pmip.c:210): demux engine error waiting for event

However when I use the same command to run it only in one sys2 with this command

spectre -64 /home/input.scs +escchars +log /home/psf/spectre.out -format psfxl -raw /home/psf +aps +mt=8 +cktpreset=sampled +postlayout +lqtimeout 900 -maxw 5 -maxn 5 +dp=ssh +hosts "sys2:8"

the simulation runs without any problem.

Kindly help me out with this problem.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    I tried an example using +dp=ssh and it worked fine - didn't hit this error (I was using multiple hosts, and with or without +mt=8).

    You didn't give any info on the spectre version being used, but either way I didn't see this reported (quite) before - there were some similar messages but not always from APS. The error is coming from within the OPENMPI code. The best thing would be to talk to customer support about this - there's potentially some debugging options that could be added (I don't want to advertise it in a public forum) to help understand this.

    Regards.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • rsashwinkumar
    rsashwinkumar over 7 years ago in reply to Andrew Beckett

    Thank you Andrew. I will contact the customer support.

    • 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