Stats

  • Locked Locked
  • Replies 6
  • Subscribers 126
  • Views 14336
  • 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

nmrd?

IAmAries

I'm seeing warnings like this

"*WARNING* nmr: nmrd did not respond on lab04"

in my log files while doing a drc with assura (version below).  I've not been able to track down what component "nmrd" actually is to troubleshoot.  Can someone perhaps point me in the right direction?  My runs commence (and successfully finish) after about 60 of these warnings.

Assura (tm) Physical Verification Version av4.1:Production:dfII6.1.5-64b:IC6.1.5-64b.500.5
Release 4.1_USR2_HF10

Parents

  • I will not post the entire nmrd FAQ here, but the key aspects are that it is really only needed for remote runs. However, for historical reasons, it also tries to be used whenever multiCPU is used.

    You should be able to suppress the problem by doing:

    setenv ASSURA_NO_NMRD 1  # if using csh
    export ASSURA_NO_NMRD=1  # if using bash/ksh

    before launching Virtuoso/Assura.

    Of course, if you are really running remote Assura jobs, then it is needed but presumably that's not the case. nmrd is used to deal with mapping file names when on remote systems.

    Regards,

    Andrew.

Reply

  • I will not post the entire nmrd FAQ here, but the key aspects are that it is really only needed for remote runs. However, for historical reasons, it also tries to be used whenever multiCPU is used.

    You should be able to suppress the problem by doing:

    setenv ASSURA_NO_NMRD 1  # if using csh
    export ASSURA_NO_NMRD=1  # if using bash/ksh

    before launching Virtuoso/Assura.

    Of course, if you are really running remote Assura jobs, then it is needed but presumably that's not the case. nmrd is used to deal with mapping file names when on remote systems.

    Regards,

    Andrew.

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.