2VB1: Difference between revisions

279 bytes added ,  20 February 2011
no edit summary
No edit summary
Line 2: Line 2:


== XDS processing ==
== XDS processing ==


* use [[generate_XDS.INP]] to obtain a good starting point
* use [[generate_XDS.INP]] to obtain a good starting point
Line 85: Line 84:
  MAXIMUM_NUMBER_OF_JOBS=6
  MAXIMUM_NUMBER_OF_JOBS=6
performs best for a 2-Xeon X5570 machine with 24GB of memory and a RAID1 consisting of 2 1TB SATA disks. It should be noted that the dataset has 27GB, and in 296 seconds this means 92 MB/s continuous reading. The processing time is thus limited by the disk access, not by the CPU. And no, the data are not simply read from RAM (tested by "echo 3 > /proc/sys/vm/drop_caches before the XDS run).
performs best for a 2-Xeon X5570 machine with 24GB of memory and a RAID1 consisting of 2 1TB SATA disks. It should be noted that the dataset has 27GB, and in 296 seconds this means 92 MB/s continuous reading. The processing time is thus limited by the disk access, not by the CPU. And no, the data are not simply read from RAM (tested by "echo 3 > /proc/sys/vm/drop_caches before the XDS run).
== Example: sweep e ==
=== XDS.INP ===
=== CORRECT.LP main table; 1st pass ===
=== CORRECT.LP main table; optimization pass ===
== XSCALE results ==
a few sweeps were optimized by copying the two lines containing mosaicity and beam divergence values from
=== main table ===


  SUBSET OF INTENSITY DATA WITH SIGNAL/NOISE >= -3.0 AS FUNCTION OF RESOLUTION
  SUBSET OF INTENSITY DATA WITH SIGNAL/NOISE >= -3.0 AS FUNCTION OF RESOLUTION
2,652

edits