From 073f9ca18dcb0ae11aae8358b9fb964ef2ae3f88 Mon Sep 17 00:00:00 2001 From: Thomas White Date: Wed, 29 Feb 2012 17:02:38 +0100 Subject: Documentation update --- Makefile.am | 4 +- README | 5 +- doc/man/crystfel.7 | 113 +++++++++++++++++++++++++++++ doc/man/crystfel_geometry.1 | 169 -------------------------------------------- doc/man/crystfel_geometry.5 | 169 ++++++++++++++++++++++++++++++++++++++++++++ doc/man/hdfsee.1 | 90 ++++++++++++++++++++++- doc/man/partial_sim.1 | 65 +++++++---------- doc/man/powder_plot.1 | 38 +++++----- 8 files changed, 419 insertions(+), 234 deletions(-) create mode 100644 doc/man/crystfel.7 delete mode 100644 doc/man/crystfel_geometry.1 create mode 100644 doc/man/crystfel_geometry.5 diff --git a/Makefile.am b/Makefile.am index 7b94dc3b..c99b1a23 100644 --- a/Makefile.am +++ b/Makefile.am @@ -98,8 +98,8 @@ crystfel_DATA = data/diffraction.cl data/hdfsee.ui EXTRA_DIST += $(crystfel_DATA) -man_MANS = doc/man/check_hkl.1 doc/man/compare_hkl.1 \ - doc/man/crystfel_geometry.1 doc/man/get_hkl.1 doc/man/hdfsee.1 \ +man_MANS = doc/man/crystfel.7 doc/man/check_hkl.1 doc/man/compare_hkl.1 \ + doc/man/crystfel_geometry.5 doc/man/get_hkl.1 doc/man/hdfsee.1 \ doc/man/indexamajig.1 doc/man/partialator.1 doc/man/partial_sim.1 \ doc/man/pattern_sim.1 doc/man/powder_plot.1 doc/man/process_hkl.1 \ doc/man/render_hkl.1 diff --git a/README b/README index 4c2c3622..61cc9664 100644 --- a/README +++ b/README @@ -2,10 +2,11 @@ CrystFEL - Crystallography with a FEL ------------------------------------- Copyright © 2012 Thomas White +Copyright © 2012 Richard Kirian Copyright © 2012 Andrew Aquila Copyright © 2012 Andrew Martin Copyright © 2012 Lorenzo Galli -Copyright © 2012 Richard Kirian + Please read the AUTHORS file for a full list of contributions and contributors. See the COPYING file for licence conditions. Summary: GPLv3+. @@ -60,8 +61,6 @@ In addition, there is also: - check_hkl, for determining things like completeness. - - calibrate_detector, for refining detector geometry. - - partial_sim, for calculating partial reflection intensities. diff --git a/doc/man/crystfel.7 b/doc/man/crystfel.7 new file mode 100644 index 00000000..751261fb --- /dev/null +++ b/doc/man/crystfel.7 @@ -0,0 +1,113 @@ +.\" +.\" CrystFEL main man page +.\" +.\" Copyright © 2012 Thomas White +.\" +.\" Part of CrystFEL - crystallography with a FEL +.\" + +.TH CRYSTFEL 7 +.SH NAME +CrystFEL - data processing for FEL crystallography + +.SH DESCRIPTION +CrystFEL is a suite of programs for processing Bragg diffraction data acquired with a free electron laser in a "serial" manner. Some of the particular characteristics of such data which call for a specialised software suite are: + +.RS +Each crystal is used for only one exposure, and there is no oscillation, rotation nor a large bandwidth or divergence. Therefore, many or all reflections are partially integrated. +.PP +The crystals might be very small and the illumination highly coherent, leading to significant Fourier truncation effects on the detector. +.PP +Many patterns, numbering tens of thousands or more, are required, so high throughput automated processing is import. +.PP +The crystal orientations in each pattern are random and uncorrelated, which leads to special considerations during scaling and merging. +.RE + +CrystFEL includes programs for simulating and processing patterns subject to the +above characteristics. Four programs form the core of CrystFEL. They are: + +.IP \fBindexamajig\fR +Batch indexing, integration and data reduction program, which produces a "stream" containing the indexing and integration results for each diffraction pattern. + +.IP \fBpattern_sim\fR +A diffraction pattern simulation tool. + +.IP \fBprocess_hkl\fR +A tool merging intensities from many patterns into a single reflection list, via the Monte Carlo method. + +.IP \fBpartialator\fR +Full scaling and post-refinement process for accurate merging of data and outlier rejection. + +.PP +In addition, there is also: + +.IP \fBget_hkl\fR +A tool for manipulating reflection lists, such as performing symmetry expansion. + +.IP \fBpowder_plot\fR +A tool for the calculation of one-dimensional "powder" traces. + +.IP \fBcompare_hkl\fR and \fBcheck_hkl\fR +Tools for calculating figures of merit, such as completeness and R-factors. + +.IP \fBpartial_sim\fB +A tool for calculating partial reflection intensities, perhaps for testing the convergence of Monte Carlo merging. + +.IP \fBhdfsee\fR +A simple viewer for images stored in HDF5 format. + +.IP \fBrender_hkl\fR +A tool for rendering slices of reciprocal space in two dimensions. + +.PP +There is also a folder full of scripts for achieving many related tasks. + +.PP +CrystFEL mostly works with images stored in HDF5 format, unit cell data in PDB +format, and reflection lists in plain text format (i.e. not MTZ). There are +scripts for converting both ways between plain text reflection lists and MTZ +files. + +.PP +Please see the individual manual pages for the CrystFEL programs for detailed information. + +.SH AUTHOR +This page was written by Thomas White. + +.SH REPORTING BUGS +Report bugs to , or visit . + +.SH COPYRIGHT AND DISCLAIMER +.PD 0 +Copyright © 2012 Thomas White +.LP +Copyright © 2012 Richard Kirian +.LP +Copyright © 2012 Andrew Aquila +.LP +Copyright © 2012 Andrew Martin +.LP +Copyright © 2012 Lorenzo Galli +.PD +.PP +Please read the AUTHORS file in the CrystFEL source code distribution for a full list of contributions and contributors. +.P +CrystFEL is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. +.P +CrystFEL is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. +.P +You should have received a copy of the GNU General Public License along with CrystFEL. If not, see . + +.SH SEE ALSO +.BR indexamajig (1), +.BR process_hkl (1), +.BR partialator (1), +.BR pattern_sim (1), +.BR partial_sim (1), +.BR compare_hkl (1), +.BR check_hkl (1), +.BR render_hkl (1), +.BR powder_plot (1), +.BR hdfsee (1), +.BR get_hkl (1), +.BR crystfel_geometry (1). diff --git a/doc/man/crystfel_geometry.1 b/doc/man/crystfel_geometry.1 deleted file mode 100644 index 708086ff..00000000 --- a/doc/man/crystfel_geometry.1 +++ /dev/null @@ -1,169 +0,0 @@ -.\" -.\" Geometry man page -.\" -.\" Copyright © 2012 Thomas White -.\" -.\" Part of CrystFEL - crystallography with a FEL -.\" - -.TH CRYSTFEL\_GEOMETRY 1 - -.SH CRYSTFEL DETECTOR GEOMETRY FILES - -The detector geometry is taken from a text file rather than hardcoded into the -program. Programs which care about the geometry (particularly indexamajig, -pattern_sim and powder_plot) take an argument "--geometry=" -(or "-g "), where contains the geometry. - -A flexible (and pedantic) representation of the detector has been developed to -avoid all possible sources of ambiguity. CrystFEL's representation of a -detector is broken down into one or more "panels", each of which has its own -camera length, geometry, resolution and so on. Each panel fits into the overall -image taken from the HDF5 file, defined by minimum and maximum coordinates in -the "fast scan" and "slow scan" directions. "Fast scan" refers to the direction -whose coordinate changes most quickly as the bytes in the HDF5 file are moved -through. The coordinates are specified inclusively, meaning that a minimum of 0 -and a maximum of 9 results in a width of ten pixels. Counting begins from zero. -All pixels in the image must be assigned to a panel - gaps are not permitted. - -In the current version, panels are assumed to be perpendicular to the incident -beam and to have their edges parallel. Within these limitations, any geometry -can be constructed. - -The job of the geometry file is to establish a relationship between the array -of pixel values in the HDF5 file, defined in terms only of the "fast scan" and -"slow scan" directions, and the laboratory coordinate system defined as follows: - -+z is the beam direction, and points along the beam (i.e. away from the source) -.br -+y points towards the zenith (ceiling). -.br -+x completes the right-handed coordinate system. - -Naively speaking, this means that CrystFEL at the images from the "into the -beam" perspective, but please avoid thinking of things in this way. It's much -better to consider the precise way in which the coordinates are mapped. - -The syntax for a simple geometry might include several entires of the following -form: - -; Lines which should be ignored start with a semicolon. - -; The name before the slash indicates which panel is referred to. You can use -.br -; any name as long as it doesn't start with "bad" (see below). -.br -; The range of pixels in the HDF5 file which correspond to a panel are given: -.br -panel0/min_fs = 0 -.br -panel0/min_ss = 0 -.br -panel0/max_fs = 193 -.br -panel0/max_ss = 184 - -; The readout direction (x, y or 0). If more than three peaks are found in -.br -; the same readout region, they are all discarded. This helps to avoid -.br -; problems due to streaks appearing along the readout direction. -.br -; If the badrow direction is '-', then the culling described above will not -.br -; be performed for this panel. -.br -panel0/badrow_direction = - - -; The resolution (in pixels per metre) for this panel -.br -panel0/res = 9090.91 - -; The characteristic peak separation in pixels. The peak detection will assume -.br -; that genuine peaks are separated by at least this amount. -.br -panel0/peak_sep = 6.0 - -; You need to specify the peak integration radius, which should be a little -.br -; larger than the actual radii of the peaks in pixels -.br -panel0/integr_radius = 2.0 - -; The camera length (in metres) for this panel -.br -; You can also specify the HDF path to a scalar floating point value containing -.br -; the camera length in millimetres. -.br -panel0/clen = /LCLS/detectorPosition - -; For this panel, the fast and slow scan directions correspond to the given -.br -; directions in the lab coordinate system described above, measured in pixels. -.br -panel0/fs = +y -.br -panel0/ss = -x - -; The corner of this panel, defined as the first point in the panel to appear in -.br -; the HDF5 file, is now given a position in the lab coordinate system. -.br -; Note that "first point in the panel" is a conceptual simplification. We refer -.br -; to that corner, and to the very corner of the pixel - NOT, for example, to the -.br -; centre of the first pixel to appear. -.br -panel0/corner_x = 429.39 -.br -panel0/corner_y = -17.30 - -; You can suppress indexing for this panel if required, by setting "no_index" to -.br -; "true" or "1". -.br -panel0/no_index = 0 - -; You can also specify bad regions. Peaks with centroid locations within such -.br -; a region will not be integrated nor indexed. Bad regions are specified in -.br -; pixel units, but in the lab coordinate system (i.e. "y" points at the ceiling, -.br -; "z" is the beam direction and "x" completes the right-handed system). -.br -badregionA/min_x = -20.0 -.br -badregionA/max_x = +20.0 -.br -badregionA/min_y = -100.0 -.br -badregionA/max_y = +100.0 - -; If you have a bad pixel mask, you can include it in the HDF5 file as an -.br -; unsigned 16-bit integer array of the same size as the data. You need to -.br -; give its path within each HDF5 file, and two bitmasks. The pixel is -.br -; considered good if all of the bits which are set in "mask_good" are set, AND -.br -; if none of the bits which are set in "mask_bad" are set. -.br -mask = /processing/hitfinder/masks -.br -mask_good = 0x27 -.br -mask_bad = 0x00 - -; Any of the per-panel values can be given without a panel prefix, for example: -.br -peak_sep = 6.0 -.br -; in which case the value will be used for all *subsequent* panels. - - -See the "examples" folder for some examples (look at the ones ending in .geom). diff --git a/doc/man/crystfel_geometry.5 b/doc/man/crystfel_geometry.5 new file mode 100644 index 00000000..4b3b7aee --- /dev/null +++ b/doc/man/crystfel_geometry.5 @@ -0,0 +1,169 @@ +.\" +.\" Geometry man page +.\" +.\" Copyright © 2012 Thomas White +.\" +.\" Part of CrystFEL - crystallography with a FEL +.\" + +.TH CRYSTFEL\_GEOMETRY 5 + +.SH CRYSTFEL DETECTOR GEOMETRY FILES + +The detector geometry is taken from a text file rather than hardcoded into the +program. Programs which care about the geometry (particularly indexamajig, +pattern_sim and powder_plot) take an argument "--geometry=" +(or "-g "), where contains the geometry. + +A flexible (and pedantic) representation of the detector has been developed to +avoid all possible sources of ambiguity. CrystFEL's representation of a +detector is broken down into one or more "panels", each of which has its own +camera length, geometry, resolution and so on. Each panel fits into the overall +image taken from the HDF5 file, defined by minimum and maximum coordinates in +the "fast scan" and "slow scan" directions. "Fast scan" refers to the direction +whose coordinate changes most quickly as the bytes in the HDF5 file are moved +through. The coordinates are specified inclusively, meaning that a minimum of 0 +and a maximum of 9 results in a width of ten pixels. Counting begins from zero. +All pixels in the image must be assigned to a panel - gaps are not permitted. + +In the current version, panels are assumed to be perpendicular to the incident +beam and to have their edges parallel. Within these limitations, any geometry +can be constructed. + +The job of the geometry file is to establish a relationship between the array +of pixel values in the HDF5 file, defined in terms only of the "fast scan" and +"slow scan" directions, and the laboratory coordinate system defined as follows: + ++z is the beam direction, and points along the beam (i.e. away from the source) +.br ++y points towards the zenith (ceiling). +.br ++x completes the right-handed coordinate system. + +Naively speaking, this means that CrystFEL at the images from the "into the +beam" perspective, but please avoid thinking of things in this way. It's much +better to consider the precise way in which the coordinates are mapped. + +The syntax for a simple geometry might include several entires of the following +form: + +; Lines which should be ignored start with a semicolon. + +; The name before the slash indicates which panel is referred to. You can use +.br +; any name as long as it doesn't start with "bad" (see below). +.br +; The range of pixels in the HDF5 file which correspond to a panel are given: +.br +panel0/min_fs = 0 +.br +panel0/min_ss = 0 +.br +panel0/max_fs = 193 +.br +panel0/max_ss = 184 + +; The readout direction (x, y or 0). If more than three peaks are found in +.br +; the same readout region, they are all discarded. This helps to avoid +.br +; problems due to streaks appearing along the readout direction. +.br +; If the badrow direction is '-', then the culling described above will not +.br +; be performed for this panel. +.br +panel0/badrow_direction = - + +; The resolution (in pixels per metre) for this panel +.br +panel0/res = 9090.91 + +; The characteristic peak separation in pixels. The peak detection will assume +.br +; that genuine peaks are separated by at least this amount. +.br +panel0/peak_sep = 6.0 + +; You need to specify the peak integration radius, which should be a little +.br +; larger than the actual radii of the peaks in pixels +.br +panel0/integr_radius = 2.0 + +; The camera length (in metres) for this panel +.br +; You can also specify the HDF path to a scalar floating point value containing +.br +; the camera length in millimetres. +.br +panel0/clen = /LCLS/detectorPosition + +; For this panel, the fast and slow scan directions correspond to the given +.br +; directions in the lab coordinate system described above, measured in pixels. +.br +panel0/fs = +y +.br +panel0/ss = -x + +; The corner of this panel, defined as the first point in the panel to appear in +.br +; the HDF5 file, is now given a position in the lab coordinate system. +.br +; Note that "first point in the panel" is a conceptual simplification. We refer +.br +; to that corner, and to the very corner of the pixel - NOT, for example, to the +.br +; centre of the first pixel to appear. +.br +panel0/corner_x = 429.39 +.br +panel0/corner_y = -17.30 + +; You can suppress indexing for this panel if required, by setting "no_index" to +.br +; "true" or "1". +.br +panel0/no_index = 0 + +; You can also specify bad regions. Peaks with centroid locations within such +.br +; a region will not be integrated nor indexed. Bad regions are specified in +.br +; pixel units, but in the lab coordinate system (i.e. "y" points at the ceiling, +.br +; "z" is the beam direction and "x" completes the right-handed system). +.br +badregionA/min_x = -20.0 +.br +badregionA/max_x = +20.0 +.br +badregionA/min_y = -100.0 +.br +badregionA/max_y = +100.0 + +; If you have a bad pixel mask, you can include it in the HDF5 file as an +.br +; unsigned 16-bit integer array of the same size as the data. You need to +.br +; give its path within each HDF5 file, and two bitmasks. The pixel is +.br +; considered good if all of the bits which are set in "mask_good" are set, AND +.br +; if none of the bits which are set in "mask_bad" are set. +.br +mask = /processing/hitfinder/masks +.br +mask_good = 0x27 +.br +mask_bad = 0x00 + +; Any of the per-panel values can be given without a panel prefix, for example: +.br +peak_sep = 6.0 +.br +; in which case the value will be used for all *subsequent* panels. + + +See the "examples" folder for some examples (look at the ones ending in .geom). diff --git a/doc/man/hdfsee.1 b/doc/man/hdfsee.1 index 15bcdd51..1eff27ad 100644 --- a/doc/man/hdfsee.1 +++ b/doc/man/hdfsee.1 @@ -8,10 +8,94 @@ .TH HDFSEE 1 .SH NAME -hdfsee \- HDF5 image viewer +hdfsee - HDF5 image viewer .SH SYNOPSIS .PP -.B hdfsee -[options] +.B hdfsee \fIimage.h5\fR [\fIoptions\fR] \fB...\fR .SH DESCRIPTION +hdfsee is a simple image viewer for images stored in HDF5 files. + +.SH OPTIONS +.PD 0 +.IP "\fB-p\fR \fIfilename\fR" +.IP \fB--peak-overlay=\fR\fIfilename\fR +.PD +Peak locations will be read from \fIfilename\fR and displayed on the image. The peak location file can use the format used in CrystFEL stream files for lists of integrated reflections, i.e. including the Miller indices. If a line cannot be read using this format, it will be assumed to be a simple two-column list of fast scan and slow scan coordinates. Any text beyond the second column will be ignored. If the line cannot be read in either format, it will be ignored. + +.PD 0 +.IP \fB--ring-size=\fR\fIradius\fR +.PD +Set the radius of the rings used for displaying peak locations. The radius is given in pixels on the screen, i.e. the circles are drawn \fIafter\fR binning the image data. + +.PD 0 +.IP "\fB-b\fR \fIb\fR" +.IP \fB--binning=\fR\fIb\fR +.PD +Show the image after binning down by a factor of \fIb\fR. + +.PD 0 +.IP "\fB-e\fR \fIpath\fR" +.IP \fB--image=\fR\fIpath\fR +.PD +Get the image data to display from \fIpath\fR inside the HDF5 file. For example: \fI/data/rawdata\fR. + +.PD 0 +.IP "\fB-g\fR \fIfilename\fR" +.IP \fB--geometry=\fR\fIfilename\fR +.PD +Display the image data according to the geometry description in \fIfilename\fR. Out of plane components of the geometry will be ignored. This is required, in addition to a wavelength in the HDF5 file (as /LCLS/photon_wavelength_nm or /LCLS/photon_wavelength_A), to display resolution rings. + +.PD 0 +.IP "\fB-i\fR \fIn\fR" +.IP \fB--int-boost=\fR\fIn\fR +.PD +Multiply the intensity in the image by \fIn\fR before displaying. With n=1, the top of the colour scale will represent the maximum pixel intensity found in the image. + +.PD 0 +.IP \fB--show-rings\fR +.PD +Show resolution rings on the image at 1 Angstrom intervals. + +.PD 0 +.IP \fB--simple-rings=\fR\fIradii\fR +.PD +Show rings on the image with the radii specified. \fIradii\fR can be a comma-deliminated list of several values, for example \fI100,200\fR. The radii have units of pixels on the detector before bininng. + +.PD 0 +.IP \fB-c\fR \fIscale\fR +.IP \fB--colscale=\fR\fIscale\fR +.PD +Use \fIscale\fR as the colour scale. Possible scales are: \fBmono\fR, \fBinvmono\fR and \fBcolour\fR. + +.PD 0 +.IP \fB--filter-cm\fR +.PD +Attempt to subtract common-mode noise from the image. + +.PD 0 +.IP \fB--filter-noise\fR +.PD +Apply a noise filter to the image with checks 3x3 squares of pixels and sets all of them to zero if any of the nine pixels have a negative value. + +.SH AUTHOR +This page was written by Thomas White. + +.SH REPORTING BUGS +Report bugs to , or visit . + +.SH COPYRIGHT +Copyright © 2012 Thomas White +.P +partial_sim is part of CrystFEL. +.P +CrystFEL is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. +.P +CrystFEL is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. +.P +You should have received a copy of the GNU General Public License along with CrystFEL. If not, see . + +.SH SEE ALSO +.BR pattern_sim (1) +and +.BR crystfel_geometry (5). diff --git a/doc/man/partial_sim.1 b/doc/man/partial_sim.1 index ea786856..e8d608b4 100644 --- a/doc/man/partial_sim.1 +++ b/doc/man/partial_sim.1 @@ -11,33 +11,21 @@ partial_sim \- calculate partial reflections .SH SYNOPSIS .PP -.B partial_sim --o simulated.stream -g geometry.geom -b xrays.beam -p unitcell.pdb -.BR [options] +.BR partial_sim +\fB-o\fR \fIsimulated.stream\fR +\fB-g\fR \fIgeometry.geom\fR +\fB-b\fR \fIxrays.beam\fR +\fB-p\fR \fIunitcell.pdb\fR +[\fIoptions\fR] \fB...\fR -.B partial_sim ---help +.BR partial_sim +\fB--help\fR .SH DESCRIPTION partial_sim calculates the intensities of idealised partial reflections from crystals in random orientations, which is useful for testing the convergence of Monte Carlo integration or scaling/post-refinement techniques. .P -You need to provide a CrystFEL geometry file (with -.BR --geometry=my.geom -or -.BR "-g my.geom" ), -a beam description file (with -.BR --beam=my.beam -or -.BR "-b my.beam" ), -a PDB file containing at least a CRYST1 line specifying the unit cell to use for the simulation (with -.BR --pdb=my.pdb -or -.BR "-p my.pdb" ), -and an output filename with -.BR --output=my.stream -or -.BR "-o my.stream" . +You need to provide a CrystFEL geometry file (with \fB--geometry=\fR\fImy.geom\fR or \fB-g\fR \fImy.geom\fR), a beam description file (with \fB--beam=\fR\fImy.beam\fR or \fB-b\fR \fImy.beam\fR), a PDB file containing at least a CRYST1 line specifying the unit cell to use for the simulation (with \fB--pdb=\fR\fImy.pdb\fR or \fB-p\fR \fImy.pdb\fR), and an output filename with \fB--output=\fR\fImy.stream\fR or \fB-o\fR \fImy.stream\fR. For each randomly generated orientation, partial_sim calculates which reflections would appear on the detector with the specified beam parameters. It calculates the partiality for each reflection and multiplies it by the fully integrated intensity to produce a partial intensity. The fully integrated intensities can be taken from a file you provide (see below), otherwise they will be randomly generated (by taking the absolute value of a Gaussian random number, mean zero and standard deviation 1000). All the partial intensities for the orientation are multiplied by an overall scaling factor, which is randomly generated with a Gaussian distribution with mean 1 and standard deviation 0.3. The partial intensities are written to the output stream, and the process repeated for as many different orientations as you ask for (see below, default: 2). @@ -49,43 +37,39 @@ for information about CrystFEL geometry description files. .SH OPTIONS .PD 0 .B -.IP "-i " +.IP "-i \fIfile.hkl\fR" .B -.IP --input= +.IP --input=\fIfile.hkl\fR .PD -Take the fully integrated reflection intensities from , instead of generating them randomly. +Take the fully integrated reflection intensities from \fIfile.hkl\fR, instead of generating them randomly. .B -.IP -n +.IP -n \fIn\fR Specify the number of different orientations to simulate. Default: 2. .PD 0 .B -.IP "-r " +.IP "-r \fIrandom.hkl\fR" .B -.IP --save-random= +.IP --save-random=\fIrandom.hkl\fR .PD If you did not provide your own fully integrated reflection intensities, they will be generated randomly for you. Use this option to save the random intensities for future comparisons. .PD 0 .B -.IP "-y " +.IP "\fB-y\fR \fIpointgroup\fR" .B -.IP --symmetry= +.IP \fB--symmetry=\fR\fIpointgroup\fR .PD -Specifies the symmetry of the input reflection list (with -.B -i , -or the symmetry of the randomly generated intensities. +When combined with with \fB-i\fR, specifies the symmetry of the input reflection list. Otherwise, specifies the symmetry of the randomly generated intensities. .PD 0 .B -.IP "-c " +.IP "\fB-c\fR \fIval\fR" .B -.IP "--cnoise= +.IP "\fB--cnoise=\fR\fIval\fR .PD -Add random values with a flat distribution to the components of the reciprocal lattice vectors written to the stream, simulating indexing errors. The maximum value that will be added is +/- -.BR -percent. +Add random values with a flat distribution to the components of the reciprocal lattice vectors written to the stream, simulating indexing errors. The maximum value that will be added is +/- \fIval\fR percent. .SH AUTHOR This page was written by Thomas White. @@ -93,7 +77,7 @@ This page was written by Thomas White. .SH REPORTING BUGS Report bugs to , or visit . -.SH COPYRIGHT +.SH COPYRIGHT AND DISCLAIMER Copyright © 2012 Thomas White .P partial_sim is part of CrystFEL. @@ -107,6 +91,5 @@ You should have received a copy of the GNU General Public License along with Cry .SH SEE ALSO .BR process_hkl (1), .BR partialator (1), -.BR pattern_sim (1) -and -.BR crystfel_geometry (1). +.BR pattern_sim (1), +.BR crystfel_geometry (5). diff --git a/doc/man/powder_plot.1 b/doc/man/powder_plot.1 index df185d61..9a1151fa 100644 --- a/doc/man/powder_plot.1 +++ b/doc/man/powder_plot.1 @@ -12,27 +12,30 @@ powder_plot \- generate 1D powder patterns .SH SYNOPSIS .PP .B powder_plot --i -o -[--min=<1/d> --max=<1/d>] +\fB-i\fR \fIinput.hkl\fR | \fB-i\fR \fIinput.h5\fR | \fB-i\fR \fIinput.stream\fR +\fB-o\fR \fIoutput.dat\fR +[\fB--min=\fR\fI1/d\fR \fB--max=\fR\fI1/d\fR] +[\fIoptions\fR\] \fB...\fR .PP -.B powder_plot --i file.hkl [..] [--use-redundancy] [--no-d-scaling] +.BR powder_plot +\fB-i\fR \fIfile.hkl\fR [\fIoptions\fR\] \fB...\fR [\fB--use-redundancy\fR] [\fB--no-d-scaling\fR] .PP -.B powder\_plot --i file.h5 [..] -g -b [--no-sat-corr] -[--ring-corr] +.BR powder_plot +\fB-i\fR \fIfile.h5\fR [\fIoptions\fR\] \fB...\fR +\fB-g\fR \fIgeometry.geom\fR +\fB-b\fR \fIbeam.beam\fR [\fB--no-sat-corr\fR] [\fB--ring-corr\fR] .PP -.B powder_plot --i file.stream [..] --data= -[-g ] [-b ] [--no-sat-corr] [--only-indexed] -[--use-redundancy] [--ring-corr] [--no-d-scaling] +.BR powder_plot +\fB-i\fR \fIfile.stream\fR [\fIoptions\fR\] \fB...\fR --data=\fItype\fR +[-g \fIgeometry.geom\fR] [-b \fIbeam.beam\fR] [\fB--no-sat-corr\fR] [\fB--only-indexed\fR] +[\fB--use-redundancy\fR] [\fB--ring-corr\fR] [\fB--no-d-scaling\fR] .PP -.B powder_plot ---help +.BR powder_plot +\fB--help\fR .SH DESCRIPTION @@ -126,9 +129,12 @@ This page was written by Andrew Aquila and Thomas White. .SH REPORTING BUGS Report bugs to , or visit . -.SH COPYRIGHT +.SH COPYRIGHT AND DISCLAIMER Copyright © 2012 Andrew Aquila +.PD 0 +.LP Copyright © 2012 Thomas White +.PD .P powder_plot is part of CrystFEL. .P @@ -141,6 +147,6 @@ You should have received a copy of the GNU General Public License along with Cry .SH SEE ALSO .BR indexamajig (1), .BR process_hkl (1), -.BR check_hkl (1) -and +.BR check_hkl (1), +.BR crystfel_geometry (5), .BR render_hkl (1) . -- cgit v1.2.3