Hi Huw, Well spotted! We originally gave structure factors to SHELXE in our testing as for most of our test cases we only had F/SIGF available. We were advised to change to intensities but somehow in the released version the "-f" flag remained. I'll make the change and put it in a CCP4 update. Ideally we should be using the original intensities rather than converting the structure factors so we'll look to adding that as an input option.
Thanks again for spotting this. Best wishes, Ronan -----Original Message----- From: CCP4 bulletin board [mailto:[email protected]] On Behalf Of Huw Jenkins Sent: 28 January 2013 10:14 To: ccp4bb Subject: [ccp4bb] Ample, shelxe-beta and F to I conversion confusion Hi, I've been running Ample and I'm a bit confused about the input for the shelxe-beta auto-tracing. The input mtz for Ample has F, SIGF and FreeR and it appears that Ample converts the structure factor amplitudes to intensities using mtz2various with the FSQUARED keyword as the log file contains the following: Data line--- LABIN FP=F SIGFP=SIGF FREE=FreeR_flag Data line--- OUTPUT SHELX Data line--- FSQUARED Fs are squared on output - better to use original Is from TRUNCATE output Data line--- END However then shelxe is run with the command: shelxe shelxe-input.pda -a15 -q -s0.4779 -o -f -n -t3 I thought that the -f flag tells shelxe that the input hkl file contains Fs not Is so this should not be present? When I run shelxe with the phaser/molrep solutions and a hkl file generated either from the merged intensities with mtz2hkl or unmerged intensities with xdsconv I get much lower CCs for the autotracing which makes sense as all of the solutions so far are rubbish! The Ample logs contain CCs >30 for all solutions which doesn't seem correct. Any information would be greatly appreciated! Thanks, Huw -- Scanned by iCritical.
