Changes

From XDSwiki
Jump to navigationJump to search
538 bytes added ,  10:52, 18 July 2013
Line 68: Line 68:  
== Indexing failures ==
 
== Indexing failures ==
   −
In case of IDXREF problems, you should definitively inspect FRAME.cbf, using [[XDS-viewer]] or [[adxv]].
+
In case of IDXREF problems, you should definitively inspect, using [[XDS-viewer]] or [[adxv]], the FRAME.cbf file which is written by COLSPOT. This file shows the first frame of the SPOT_RANGE, together with strong pixels that COLSPOT found on this frame, marked with white pixels. IDXREF will use those spot positions which have at least as many strong pixels as MINIMUM_NUMBER_OF_PIXELS_IN_A_SPOT specifies.  
   −
FRAME.cbf is written by COLSPOT. It shows the last frame of the SPOT_RANGE, together with spot positions that COLSPOT found, marked with white pixels.
+
You will only be able to look at this file if you prevent XDS from running INTEGRATE. This can be achieved e.g. by
   −
FRAME.cbf is also written by INTEGRATE (this overwrites the FRAME.cbf written by COLSPOT). It shows the last frame of the DATA_RANGE, and you should make sure that the predictions (circles) match the observed reflections.
+
JOB= XYCORR INIT COLSPOT IDXREF DEFPIX ! INTEGRATE CORRECT
 +
 
 +
since FRAME.cbf is overwritten by INTEGRATE. When FRAME.cbf is written by INTEGRATE, it shows the ''last'' frame of the DATA_RANGE, and you should make sure that the predictions (circles) match the observed reflections.
 +
 
 +
To look at '''all''' spot positions found by COLSPOT, you could try
 +
echo "set yrange [] reverse ; plot 'SPOT.XDS' us 1:2 w dots" | gnuplot -persist
 +
This may also help to find shaded regions on the detector.
    
=== IDXREF ends with !!! ERROR !!! message ===
 
=== IDXREF ends with !!! ERROR !!! message ===
2,527

edits

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

Navigation menu