Thank you Boaz. So if CORRECT can do a fully corrected scaling, are there no corrections that XSCALE might apply to XDS_ASCII.HKL data that are beyond CORRECT's capabilities? Wolfram
On Tue, Nov 11, 2014 at 3:05 PM, Boaz Shaanan <bshaa...@bgu.ac.il> wrote: > Hi, > > I actually choose the option 'constant' further down in the aimless gui > but I guess the effect is similar to 'onlymege'. > > Boaz > > > > > > > > > > > > *Boaz Shaanan, Ph.D. Dept. of Life > Sciences Ben-Gurion University of the > Negev Beer-Sheva > 84105 > Israel > E-mail: > bshaa...@bgu.ac.il <bshaa...@bgu.ac.il> Phone: 972-8-647-2220 Skype: > boaz.shaanan Fax: 972-8-647-2992 or 972-8-646-1710 * > > > > > > ------------------------------ > *From:* CCP4 bulletin board [CCP4BB@JISCMAIL.AC.UK] on behalf of wtempel [ > wtem...@gmail.com] > *Sent:* Tuesday, November 11, 2014 9:50 PM > *To:* CCP4BB@JISCMAIL.AC.UK > *Subject:* [ccp4bb] To scale or not to scale: XDS_ASCII.HKL input to > POINTLESS/AIMLESS > > Hello all, > in a discussion > <https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1307&L=CCP4BB&H=1&P=186901> > on this board, Kay Diederichs questioned the effect of scaling data in > AIMLESS after prior scaling in XDS (CORRECT). I understand that the > available alternatives in this work flow are to specify the AIMLESS > ‘onlymerge’ command, or not. > Are there any arguments for the preference of one alternative over the > other? > Thank you for your insights, > Wolfram Tempel > >
