|SHARP/autoSHARP User Manual||previous next|
|Copyright||© 2001-2006 by Global Phasing Limited|
|All rights reserved.|
|This software is proprietary to and embodies the confidential technology of Global Phasing Limited (GPhL). Possession, use, duplication or dissemination of the software is authorised only pursuant to a valid written licence from GPhL.|
|Documentation||(2001-2006) Clemens Vonrhein|
This is a probably a very incomplete list of possible problems - it just serves as a first point of reference. For additional information, please go directly to www.globalphasing.com where up-to-date information should be maintained.
Several of the pages are being updated while the programs are running. You may need to hit the "Reload" button from time to time (use e.g. "Shift-Reload" under Netscape to force a reload).
To view results (plots, maps and models) directly from the interface, the mime-type handling of the browser needs to be adjusted. However, the resulting maps and models can also be generated outside of this system - see Appendix One.
As a general rule:
% chmod g+rwx ~/sharpfiles % chmod g+rwx ~/sharpfiles/*files*
% chmod o+rwx ~/sharpfiles % chmod o+rwx ~/sharpfiles/*files*
Each new SHARP or autoSHARP job will create a new sub-directory in your sharpfiles/logfiles directory (actually, this will be only a link to the "local logfiles" directory sharpfiles/logfiles.<machine>, which itself is a link to the "real" directory on your machine). If this directory is not created there is a problem during job submission. Although this should have been reported through the interface, it might be a good idea to look in $BDG_home/sushi/logs/error_log - probably only the SHARP site administrator has access to this file.
All possible problems should be reported in the main log files produced by SHARP (LIST.html) or autoSHARP (LISTautoSHARP.html). Any additional problems are in the STDERR file.