VIEW: Difference between revisions

Jump to navigation Jump to search
280 bytes added ,  7 February 2008
m
no edit summary
mNo edit summary
mNo edit summary
Line 1: Line 1:
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). The most important file to look at is FRAME.pck (written by the [[INTEGRATE]] processing step).
VIEW is the visualisation program of the XDS suite.  


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.
All .pck files written by XDS or XSCALE can be viewed with VIEW (e.g. ABS.pck, BKGINIT.pck, MODPIX.pck). VIEW can also be used to look at 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
<framesize in bytes> - 2 * NX * NY .  


If the integration has worked as it should, the following should be true:
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.
 
If the integration has worked as it should, the following should be true for FRAME.pck:
* most (if not all) observed reflections are encircled by thin lines (corresponding to integration areas)
* most (if not all) observed reflections are encircled by thin lines (corresponding to integration areas)
* empty integration areas belong to weak reflections
* empty integration areas belong to weak reflections
2,684

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.

Navigation menu