When Problems Occur

 

There are many, many things which can go wrong in this procedure, so if you have problems please send a note to vmd@ks.uiuc.edu describing exactly how things are set up (i.e. where VMD and NAMD and MDComm files are installed, what script is being used to start VMD, and what are the symptoms of the problem). Please note that a new version of this is being worked out and should be available very soon. Here are a couple quick notes about things that can go wrong:

• You connect to NAMD, NAMD starts up, but nothing ever gets displayed and VMD just sits there.
  Quite often this is because namd_consumer could not be started on the graphics workstation. Typical reasons for this are:
  • namd_consumer_ARCH was never installed.
  • MDC_CONSUMER was not set to the location of namd_consumer_ARCH.
  • the namd stdout and stderr information is saved in the files ~/rapp.stdout.$PID and ~/rapp.stderr.$PID -- you will have to delete these yourself when the simulation(s) finish. These files may also help to identify the problem since the occurring error message appears in one of them.

• You make a connection to rappd, but the lists of available programs and jobs are both empty.
  The configuration files were not set up properly, and when (or if) rappd was started it could not figure out where any of the applications are located.