Dear All, Just to understand more, the XDS_ASCII.HKL file generated after running XDS contains scaled and merged reflections?
Moreover, what happens exactly, if you use XDS_ASCII.HKL file in AIMLESS instead of INTEGRATE.HKL file?? I ran AIMLESS separately, one using already scaled XDS_ASCII.HKL and another using INTEGRATE.HKL and I found that in the run using XDS_ASCII.HKL little lesser total number of observation but marginally better statistics. Thanks Nishant On Thu, Nov 17, 2016 at 10:08 PM, Andreas Forster <docandr...@gmail.com> wrote: > Dear Wei, > > if you process your data with XDS, the best is probably to do the scaling > in XDS (CORRECT) and be done with it. If you want to use Aimless for > merging, you can turn off scaling with the ONLYMERGE keyword or use SCALES > CONSTANT. > > All best. > > > Andreas > > > > > On Thu, Nov 17, 2016 at 9:40 PM, Wei Wang <ww2...@columbia.edu> wrote: > >> Hi, >> >> Is there a way to let xds_par use less than all processors/threads on the >> machine? Sometimes I would like to process something else while XDS is >> running. >> >> Another question is related to the scaling procedure. My understanding is >> that the XDS already does the scaling during correction. So if I follow the >> XDS-Aimless route, then probably I should let Aimless do "skip scaling and >> only merge"? Please elucidate me on this issue. >> >> Regards, >> >> Wei >> > > -- Dr. Nishant Kumar Varshney, IISc-ICTP Fellow XRD2 Beamline, Elettra-Sincrotrone, In Area Science Park, Basovizza, S.S. 14, Km 163,5, 34012 Trieste, Italy +39-040-375 8737 (office ESP4 P1 031) +39-040-375-8435 (XRD2 beamline) +39 3318809798 (Mobile)
