Symptom:

Thordbfix451 (actually its auxilliary script, thordbfix451_rebuild) complains that it cannot open the thorserverXXXXX.log file, then thorchange fails to connect. However, the specified log file is indeed present.

The Cause:

The Thorserver may take several seconds to start up and create the log file on a busy system. The log file is not created in time for the script to read it.

The Fix:

A slight change forces thordbfix451_rebuild to wait until the Thorserver log file is created before proceeding. Download this new version here:

Please note that all database-passwords must be removed before using Thordbfix451.

Symptom:

An error results when trying to link to the default Daylight toolkit libraries (in $DY_ROOT/lib).

The error message will resemble:

ld32: FATAL 112: cannot link old 32-bit object with -n32 link:

The Cause:

The default cc options on IRIX 6.4 include "-n32" which specify the use of "new-format" 32-bit objects. The 4.51 libraries in $DY_ROOT/lib are linked on IRIX 5.3, and are "old-format" 32-bit objects.

The Fix:

Set the environment variable SGI_ABI to "-32" (Application Binary Interface) as follows:

setenv SGI_ABI "-32"   (csh)

SGI_ABI="-32"
export SGI_ABI   (sh)

Symptom:

Similarity searching doesn't work in some databases. You'll get an error message:

ERROR: This database has no fingerprints, can't do similarity search (dy_mp_similar_setup)

although this is not exactly true, they're just not loaded.

Another symptom is that sub- and super-structure searching are slow with these databases, since they're not using fingerprints.

This is known to be true for the following databases:

1. ic97_datatypes

The "FP" (Fingerprint) datatype is defined incorrectly. The _P specification does not instruct the Merlinserver to load the bitmap (first field).

The Fix:

Change the _P<> dataitem in the $D<FP> datatype definition TDT to: _P<*;*;*;*;*;> One simple way to do this is to overwrite the entire FP datatype. Save the following to a file, say "FP.tdt":

$D<FP>
_V<"Fingerprint;Orig nbits;Orig nbits set;Nbits;Nbits set;Version;ID">
_B<"FP;FP/obits;FP/oset;FP/nbits;FP/nset;FP/ver;FP/id">
_N<"BINARY;NUMERIC;NUMERIC;NUMERIC;NUMERIC;;">
_P<"*;*;*;*;*;*;*">
_S<"Fingerprint of molecule, used for high-speed screening and similarity;Original size;Original number of bits set;Folded size;Number of bitsset">
_D<"Bitmap of structural features for screening;Number of bits in bitmap before folding;Number of 1's in bitmap before folding;Number of bits in folded bitmap;Number of 1's in folded bitmap">
_M<System>
_O<Daylight Chemical Information Systems, Inc.>
|


Symptom:

ClogP calculations are missing LogP-star values (P1 data).

Cause:

The file "logpstar97.smi" was not included in $DY_ROOT/data. This file contains 9853 high confidence "LogP-star" values which should be output for their associated SMILES with the ClogP calculation. This will not be true with 4.51 as released.

Fix:

Symptom:

The Ruby test program (http:/dayhtml/test-ruby.html) does not work.

Cause/Fix:

The file $DY_ROOT/daycgi/dcgi_env.sh incorrectly defines CX_ROOT. Change this line to:

CX_ROOT=$DY_ROOT/exotic/cex/cex033

(i.e., put the exotic back in cex).

Thorserver Patch Available

A Thorserver bug was discovered which can corrupt a database when writing to it. Corruption occurs when a newly added record is subsequently reduced in size by more than 32 bytes. One fortunate fact is that no data is lost due to this bug. The corrupt portion of the .DP file is separate from the correctly overwritten TDT, and thordump skips these corrupt bytes successfully. Thus, a database can be rebuilt without loss with a thordump/thormake/thorload procedure. Corruption in the database is indicated by inability to load the database with the Merlinserver, and errors reported by thordump.

A fix has been made to the Thorserver which corrects this bug. This fixed Thorserver should be installed and replace the 4.51 Thorserver as a patch.

To obtain this new thorserver:

    % ftp daylight.daylight.com                 <<--- Or: 207.225.60.130
    Name (...): anonymous                       <<--- log in as "anonymous"
    Password:                                   <<--- Use your email address
    ftp> cd outgoing/tp22                       <<--- Note: dir isn't readable!
    ftp> bin                                    <<--- Don't forget this step!!
    ftp> get thorserver.sun5.patch.gz           <<--- ...or...
    ftp> get thorserver.sgi5.patch.gz
    ftp> quit

Thank you to WRAIR, Novartis, and Roche for showing us this.

Symptom:

The file $DY_ROOT/data/fragdb451.dat contains 607 fragments. However, "clogp +PCMODELS_DUMPFRAGDB" only dumps definitions for 600 fragments. Any fragments put in a fragdb.del file or appended to the end of fragdb451.dat are ignored.

Cause/Fix:

Clogp (a Fortran program) only allocates space for 600 fragment definitions in the 4.51 version. This will be fixed in 4.52.

Workaround:

Since there can only be 600 fragments, if you wish to add fragments to the fragment database, some other fragments must be removed or placed at the end of fragdb451.dat.

Symptom:

When writing the output from nearneighbors to standard output, it is possible for semaphores to not be available. The semaphore key is incorrectly calculated to be (-1) in all cases, which can cause collisions. Nearneighbors will typically default to single-process mode when semaphores are not available.

Another possible symptom is truncated or corrupted output files when one nearneighbors (or another) job interferes with another by using the same semaphore (-1).

Cause/Fix:

This is fixed for 4.52.

Workaround:

The work-around for 4.4 and 4.51 is to always specify the output filename for nearneighbors (rather than directing stdout with the '>' character). It is also recommended to always use the -NUM_PROCESSES option (with 1 or greater).

For example, use:

nearneighbors -NUM_PROCESSES 2 foobar.tdt foobar.nn.tdt

nearneighbors -NUM_PROCESSES 2 foobar.tdt > foobar.nn.tdt