2,684
edits
Finding out ORGX ORGY: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 3: | Line 3: | ||
There are different possibilities to find out where the direct beam would hit the detector: | There are different possibilities to find out where the direct beam would hit the detector: | ||
# visualize | # visualize BKGINIT.pck, or FRAME.pck (the FRAME.pck written by COLSPOT is very good for this purpose) with [[VIEW]], and click (left-mouse) into the middle of the beamstop shadow (or the attenuated direct beam itself, if it is recorded). Use the pixel coordinates displayed by VIEW as ORGX ORGY (in principle you should add 1 to both numbers, because for VIEW the pixels go from 0 to NX-1 whereas for XDS they go from 1 to NX).<br />Instead of these files written by XDS, one could directly use a measured frame. However this requires that one enters NX, NY, and the size of the header (which usually is <size of frame in bytes>, minus 2*NX*NY). | ||
# use adxv for visualization. Otherwise the same as with VIEW. (works for the PILATUS at SLS) | # use adxv for visualization. Otherwise the same as with VIEW. (works for the PILATUS at SLS) | ||
# use MOSFLM for visualization. It prints out X BEAM and Y BEAM from the frame header, and you may click on the hypothetical direct beam position. However, ''x and y are swapped in MOSFLM when compared to XDS'', and the coordinates are in mm, not in pixels. Sometimes the X BEAM and Y BEAM from the header are not reliable. | # use MOSFLM for visualization. It prints out X BEAM and Y BEAM from the frame header, and you may click on the hypothetical direct beam position. However, ''x and y are swapped in MOSFLM when compared to XDS'', and the coordinates are in mm, not in pixels. Sometimes the X BEAM and Y BEAM from the header are not reliable. | ||