diff options
| author | Thomas White <taw@physics.org> | 2021-10-26 15:52:10 +0200 |
|---|---|---|
| committer | Thomas White <taw@physics.org> | 2021-10-26 15:57:41 +0200 |
| commit | 7a43f3b5a9c59a972949ca58a340d2bfe1222429 (patch) | |
| tree | c27a6c9d6f903e13ffb442a732c146e733ea2a11 /doc/man/crystfel_geometry.5 | |
| parent | 1b0649e5af029970def587d1c6c494d0cae48427 (diff) | |
Remove detector rail direction altogether
This got missed out by accident in the conversion to DataTemplate, but
absolutely no-one noticed. In the meantime, my views on how the
geometry files should work have changed somewhat. I don't want to
maintain the extra complexity here when it isn't even clear that it will
eliminate the need to re-refine geometry for each camera length.
This commit just takes the rail direction stuff out of the documentation
and the geometry file parser.
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/50
Diffstat (limited to 'doc/man/crystfel_geometry.5')
| -rw-r--r-- | doc/man/crystfel_geometry.5 | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/doc/man/crystfel_geometry.5 b/doc/man/crystfel_geometry.5 index 541d729e..e4edf06d 100644 --- a/doc/man/crystfel_geometry.5 +++ b/doc/man/crystfel_geometry.5 @@ -261,12 +261,6 @@ Specifies that the saturation map should come from the HDF5 file named here, ins .IP \fBno_index\fR Set this to 1 or "true" to ignore this panel completely. -.PD 0 -.IP \fBrail_direction\fR -.IP \fBclen_for_centering\fR -.PD -Specify the direction in which the panel should move when the camera length is increased. \fBclen_for_centering\fR is the camera length at which the central beam intersects the centre of the detector. If you've only calibrated the detector at one camera length, perhaps using prior known values for the rail direction, then this should be the camera length at which you calibrated the detector. \fBclen_for_centering\fR is the camera length \fBbefore\fR applying the \fBcoffset\fR, i.e. for CSPAD/CXI/LCLS data this value should be an "encoder value" in metres. If you specify the rail direction, you must also specify clen_for_centering. The default is for the panel to move in the +z direction, so rail_direction = z and clen_for_centering is irrelevant. The modulus of the "rail vector" should normally be equal to one. Otherwise, the camera length changes from the centering value will be correspondingly scaled (which might sometimes be what you want!). - .SH BAD REGIONS Bad regions will be completely ignored by CrystFEL. You can specify the pixels to exclude in pixel units, either in the lab coordinate system (see above) or in fast scan/slow scan coordinates (mixtures are not allowed). In the latter case, the range of pixels is specified \fIinclusively\fR. Bad regions are distinguished from normal panels by the fact that they begin with the three letters "bad". |