*** For details on how to be removed from this list visit the *** *** CCP4 home page http://www.ccp4.ac.uk ***
Hmmm... Regarding x files, I don't think their format depends on the detector. If HKL2000 can't 'see' the files, there is usally a permission problem. Check again, e.g. by assigning to all directories and files the permission 'rwx' (even if it doesn't make much sense for x files to be executable). Likewise, if you say that HKL2000 can recognize the images just fine after you copied them to a new directory, then HKL2000 doesn't really have a problem. The problem must be somewhere else. Some data transfer protocols routinely assign permissions to directories that can make files unreadable for a user other than the one who transferred the files. Regarding files with four numbers (i.e. 12345.####), I remember that there were some HKL2000 versions that had problems with that. You could try renaming a few to 12345.### (three numbers). If that solves your problem, then you may have an outdated HKL2000 version. You never clearly said if you had the same problems at the beamline. If you didn't have any problems there, compare the versions. Hope that helps. Best - MM On Wed, 5 Jul 2006 18:28:02 -0400, Peng Xie wrote > Dear all, > > I am amazed and deeply touched by all of you guys who gave me all these > insightful suggestions, thank you all for all this! It feels so good to be > in this nice scientific community here at CCP4 board. > > Back to the problem I am having, I pretty much made sure of everything Nick > just mentioned, including the file permission, path and etc. but none of > them seemed to solve this problem. It happened a lot of times that the .osc > files are not accessible by HKL2000, but usually copying them to a whole new > folder solves this problem. But this time, we just brought back datasets > from this new beamline from APS 23ID D with the MAR300 detector. We have the > def.site file in place, and it could not even detect any of our image files > we took at the synchrontron (all these images files don't have usual file > extension like .img or .osc though, it is like 12345.####, every file > extension is defined by the frame number). As for the .x files, I checked > the header and format, made sure that they are identical to the ones we > processed at home source. I will try to scale the data by the scripts if the > problem persists, although that is gonna be quite tedious. > > I highly suspect that it is a problem with the HKL2000 GUI interface or > there is something wrong with our computer infastructure, though this might > be quite unlikely. > > Many thanks! > > Peng > <[email protected]> -------------------------------------------------------------------------------- Mischa Machius, PhD Associate Professor UT Southwestern Medical Center at Dallas 5323 Harry Hines Blvd.; ND10.214A Dallas, TX 75390-8816; U.S.A. Tel: +1 214 645 6381 Fax: +1 214 645 6353
