There could be many causes for this. Perhaps you do not have the best def.site file for your detector / beamline / hardware. What do your local HKL2000 experts tell you?
You could e-mail me an image and I can help you. Jim ________________________________________ From: CCP4 bulletin board [CCP4BB@JISCMAIL.AC.UK] on behalf of Peter Hsu [hsuu...@u.washington.edu] Sent: Monday, February 20, 2012 6:28 PM To: CCP4BB@JISCMAIL.AC.UK Subject: [ccp4bb] HKL2000 indexing problem Hi all, I recently collected a data set off a single crystal and have had problems with indexing it. Every time I go pick peaks for indexing it constantly picks peaks that are just slightly off the actual peak. After indexing, it would always be that 2 of the 3 cell dimensions would be fairly normal, while the 3rd would have some impossible value such as 1. On some other occasions if it manages to pick peaks properly, and every time I go to index it, it gives back an error that I don't have enough peaks picked to index (picked nearly 500). I've tried using a number of different images to index from and have run into the same problem. Has anyone else run into these problems? Does anyone have any idea what might be wrong w/my dataset and/or crystal? Thanks in advance for any insight, Peter
