*** For details on how to be removed from this list visit the *** *** CCP4 home page http://www.ccp4.ac.uk ***
Doing it automatically would be very simple to implement, since the scale is simply 9999.0/(I_max - I_min) Not much to test. And as George pointed out, the only use of this scale is indeed to avoid overflow of the fixed width output format. On Wed, 17 May 2006, Eleanor Dodson wrote: > I think they need to be on seperate lines > > FSQU > SCALE 0.5 > > At one stage I tried to make it scale automatically to keep a sensible > SHELX format.. Havent tested that for years.. > Eleanor > > > Patrick Polzer wrote: > > >*** For details on how to be removed from this list visit the *** > >*** CCP4 home page http://www.ccp4.ac.uk *** > > > > > > > > > >Hi, > > > >I have the following problem: > > > >I run mtz2various with the script: > > > >mtz2various HKLIN in.mtz HKLOUT out.hkl<<eof>mtz2var.log > >OUTPUT SHELX > >labin FP=FP SIGFP=SIGFP DP=DANDO SIGDP=SIGDANO > >resolution 134.840 2.853 > >fsquared scale 0.5 > >end > >eof > > > > > >... and get the following logfile-entries: > > > > ### CCP4 5.0: MTZ2VARIOUS version 5.0 : 04/08/04## > >... > > Data line--- OUTPUT SHELX > > Data line--- labin FP=FP SIGFP=SIGFP DP=DANDO SIGDP=SIGDANO > > Data line--- resolution 134.840 2.853 > > Data line--- fsquared scale 0.5 > >... > > *** You are inputting Fs and requesting Is to be output. > > *** The Fs will be squared and scaled by: 1.0000 > >... > > > >Scaling of my intensities is not possible. I have the same problem > >in the ccp4-interface. Is this a bug, or am I doing something wrong? > > > >Best regards > > > >Patrick Polzer > > > > > > > > > > > >
