2,684
edits
mNo edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
VIEW is the visualisation program of the XDS suite. | VIEW is the visualisation program of the XDS suite. | ||
All .pck files written by XDS or XSCALE can be viewed with VIEW (e.g. ABS.pck, BKGINIT.pck, MODPIX.pck). VIEW | VIEW -h gives a short help output with options, VIEW -hv shows a short manual. | ||
All .pck files written by XDS or XSCALE can be viewed with VIEW (e.g. ABS.pck, BKGINIT.pck, MODPIX.pck). E.g., | |||
VIEW BKGINIT.pck | |||
could be run to look at the smoothed background image obtained from the INIT step. | |||
The most important file to look at is FRAME.pck (written by the [[INTEGRATE]] processing step). The Logo of this wiki (upper left) shows part of FRAME.pck as visualized with VIEW. Here we see the "pixel labelling method" of [[XDS]] at work: the thin lines around the reflections demarcate the limits of the integration area (which is used to calculate the intensity of the reflection). The size of the integration area is calculated from BEAM_DIVERGENCE, but in case two such integration areas overlap, then each pixel in the overlap region is assigned to the nearest reflection in reciprocal space. | The most important file to look at is FRAME.pck (written by the [[INTEGRATE]] processing step). The Logo of this wiki (upper left) shows part of FRAME.pck as visualized with VIEW. Here we see the "pixel labelling method" of [[XDS]] at work: the thin lines around the reflections demarcate the limits of the integration area (which is used to calculate the intensity of the reflection). The size of the integration area is calculated from BEAM_DIVERGENCE, but in case two such integration areas overlap, then each pixel in the overlap region is assigned to the nearest reflection in reciprocal space. | ||
Line 11: | Line 14: | ||
* reflections without integration area are partial reflections, whose center is on an adjacent frame | * reflections without integration area are partial reflections, whose center is on an adjacent frame | ||
VIEW can also be used to look at data frames (with a header). In that case, the user is prompted for the required information. Usually the numbers NX and NY are the answers to the first two questions, and the header size is given by the formula | |||
<framesize in bytes> - 2 * NX * NY . | |||
VIEW - | Note for experts: the pixel numbering in VIEW goes from 0 to NX-1 (similar for y), whereas XDS using a numbering of 1 to NX (NY). Thus, if you find out a position on the detector (e.g. the direct beam) by using VIEW, you should in principle add 1 in both x and y if you want to put the numbers into [[XDS.INP]]. In practice, the 1-pixel-offset does not matter. |