-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
7197dba
commit c9569b1
Showing
2 changed files
with
63 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,63 @@ | ||
# DIALS Geometry Viewer | ||
|
||
In X-ray diffraction experiments the experimental geometry is critical for the success of the data analysis. With "traditional" set ups where the detector was downstream of the sample, with the beam in about the middle and only one way of sitting the detector on a mount this was straightforward, and the geometry was encoded in just the distance, wavelength, beam centre and any deviations from the ideal geometry were assumed to be small and corrected for with parameters such as TILT and TWIST, or similar. | ||
|
||
With imgCIF the possibility arrived to encode the geometry properly with very few assumptions, allowing e.g. the detector to sit above the sample, or upstream, and ensuring that the correct geometry could be reliably carried from the experiment to the data analysis alongside the raw image data. This concept was then extended to the NeXus format, which is a HDF5 representation of the same concepts following the same basic philosophy. | ||
|
||
While these are genuine improvements to the recording of experimental metadata they are sadly _opaque_ - which is to say the general scientist has a challenge in understanding if they have got the settings in the headers / metadata areas _correct_. As this was a recurrent problem with DIALS users we implemented the DIALS geometry viewer to show a graphical and interactive representation of the recorded experimental geometry. | ||
|
||
## Working with DIALS | ||
|
||
The basic workflow of DIALS is to _import_ data before beginning any processing. This reads the metadata and saves it in a DIALS "experiment" file in a standard way: | ||
|
||
``` | ||
dials.import /path/to/data/files | ||
``` | ||
|
||
e.g. | ||
|
||
``` | ||
Grey-Area geom :) $ dials.import ~/data/i03-2021-run1-small/xtal_1_5.nxs | ||
DIALS (2018) Acta Cryst. D74, 85-97. https://doi.org/10.1107/S2059798317017235 | ||
DIALS 3.dev.964-g641fcbbf1 | ||
The following parameters have been modified: | ||
input { | ||
experiments = <image files> | ||
} | ||
-------------------------------------------------------------------------------- | ||
format: <class 'dxtbx.format.FormatNXmxDLS16M.FormatNXmxDLS16M'> | ||
template: /Users/graeme/data/i03-2021-run1-small/xtal_1_5.nxs:1:500 | ||
num images: 500 | ||
sequences: | ||
still: 0 | ||
sweep: 1 | ||
num stills: 0 | ||
-------------------------------------------------------------------------------- | ||
Writing experiments to imported.expt | ||
``` | ||
|
||
The content of this file can be shown as human-readable text with `dials.show` e.g. | ||
|
||
``` | ||
dials.show imported.expt | ||
``` | ||
|
||
the output of which shows a few derived quantities such as the beam centre and distance which are important for processing. A key point here is if any of these quantities have surprising values it could be an indicator that something is wrong! For example, a negative distance. | ||
|
||
## The Geometry Viewer | ||
|
||
The intention of the geometry viewer is to show a graphical representation of the same information as is included in the output of `dials.show` but in a far more scientist-friendly way. The image below shows an example of the view: | ||
|
||
![Simple view of the geometry viewer](./basic-viewer.png) | ||
|
||
This shows: | ||
|
||
- the beam vector | ||
- the panel vectors e.g. origin, fast, slow, normal | ||
- the goniometer vectors (here chi is close to the beam, phi and omega coincident) | ||
|
||
Key points here are the vectors from the sample to source are dashed, from the sample to detector solid i.e. if the detector intersects with the dashed line _something is wrong_. The UI allows modification of the geometry parameters, and will allow any goniometer shadows or similar to be displayed if the instrument configuration is known to DIALS. | ||
|
||
Adjusting the setting parameters is an excellent way of comparing the description of the metadata with reality: if the axes move in the same way as they do in real life you can be fairly confident that things are correct. You can also see if the detector axes are aligned correctly with the beam and goniometer axes. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.