Solution

If you get a message similar to:

   Could not find database files : dir home
   child process exited abnormally

then IsoStar can not find the Cambridge Structural Database. This message will typically appear when you are trying to Hyperlink.

IsoStar tries to find the database in several different ways.

  1. First it checks the environment variable CSDNAME. Typically this will not be set and is reserved for times of desperation.
  2. Next, IsoStar checks CSDHOME. This should point to the location of your installation of the CSD System. The database files should be located in $CSDHOME/csd.
  3. If CSDHOME is not set, or appears to be set incorrectly, then IsoStar checks CSDDIR. This variable will typically be set by the IsoStar helper startup script. It should point to a directory containing the database.

 

To solve the problem:

1. Check whether CSDHOME is set. Type 

  echo $CSDHOME

If CSDHOME is not set then move to the next section.

If CSDHOME is set and you are reading this then it is probably set incorrectly.

CSDHOME should point to a directory containing your installation of the CSD System. This directory should contain a subdirectory called csd. The subdirectory csd should contain three files:

   asXYZbe.ind   asXYZbe.msk   asXYZbe.tcd

where XYZ is the version number of the CSD System.

If CSDHOME is set incorrectly then set it correctly, restart your Web browser and try hyperlinking from a CSD Scatterplot.

2. Check whether CSDDIR is set. Type 

   echo $CSDDIR

If CSDDIR is not set then move to the next section.

If CSDDIR is set and you are reading this then it is probably set incorrectly.

CSDDIR should point to a directory containing three files:

   asXYZbe.ind   asXYZbe.msk   asXYZbe.tcd

where XYZ is the version number of the CSD System.

If CSDDIR is set incorrectly then set it correctly, restart your Web browser and try hyperlinking from a CSD Scatterplot.

3. Look for a file in your home directory called .isostar_header. This file may contain a line of the form:

   csddir=<csdpath>

If the file does not exist or does not contain the line described above then move to the next section.

If the file does exist and does contain the line described above and you are reading this then csddir is probably set incorrectly.

csddir should point to a directory containing three files:

   asXYZbe.ind   asXYZbe.msk   asXYZbe.tcd

where XYZ is the version number of the CSD System.

If csddir is set incorrectly then set it correctly and try hyperlinking from a CSD Scatterplot.

4. Look in the file <path>/isostar/d_<mach>/lib/isostar_header where <path> contains your isostar software directory and <mach> is the type of your machine. Determine <mach> by typing:

   sh <path>/isostar/bin/csdmach.sh

The file <path>/isostar/d_<mach>/lib/isostar_header will contain a line of the form:

   csddir=<csdpath>

If you have got this far then csddir is probably set incorrectly.

csddir should point to a directory containing three files:

   asXYZbe.ind   asXYZbe.msk   asXYZbe.tcd

where XYZ is the version number of the CSD System.

Before correcting csddir in this file, you must consider whether a change will impact on use of IsoStar from machines other than your own. <path>/isostar/d_<mach>/lib/isostar_header may be referenced from other machines for which the current setting may be correct. If this is not an issue, then correct csddir and try hyperlinking from a CSD Scatterplot.

If changing csddir in <path>/isostar/d_<mach>/lib/isostar_header is inappropriate then try one of the following:

Override settings in <path>/isostar/d_<mach>/lib/isostar_header by putting a file called .isostar_header in the home directory of the account from which you are running IsoStar. In this file, put the line: 

   csddir=<csdpath>

where <csdpath> indicates correctly the directory containing the three database files.


Note however that if you are using the same account from different machines, doing this may mess up IsoStar on other machines.

Override settings in <path>/isostar/d_<mach>/lib/isostar_header and $HOME/.isostar_header by setting the environment variable CSDDIR to point to the directory containing the three database files before starting your Web browser and the IsoStar software.

Unless you set CSDDIR in your personal or global cshrc, profile or login files then they will only persist within your current shell.

5. If all of this fails to solve your problem then either:

Try setting CSDNAME to be the name of your master CSD file, before starting your Web browser. For example:

   setenv CSDNAME /usr/local/cambridge/csd/as513be

Contact User Support with details of your problem.​


« Return to search results