processing:compute_gvectors
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| processing:compute_gvectors [2019/02/19 13:47] – smerkel | processing:compute_gvectors [2023/03/14 15:29] (current) – smerkel | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| G-vectors are the scattering vector associated with the diffraction. The are nodes of the reciprocal space or, in direct space, normal to the diffracting plane. | G-vectors are the scattering vector associated with the diffraction. The are nodes of the reciprocal space or, in direct space, normal to the diffracting plane. | ||
| - | For a given reflection in the crystal, **G**< | + | For a given reflection in the crystal, **G**< |
| + | |||
| + | The real space coordinates | ||
| The x-ray wavelength λ is known, so is the rotation angle ω. There are issues, however, to evaluate the diffraction angle 2θ and the azimuth angle η. What is measured is the location of a diffraction spot on a detector. Calculating 2θ and η from the location of a diffraction spot on a detector requires calibration. | The x-ray wavelength λ is known, so is the rotation angle ω. There are issues, however, to evaluate the diffraction angle 2θ and the azimuth angle η. What is measured is the location of a diffraction spot on a detector. Calculating 2θ and η from the location of a diffraction spot on a detector requires calibration. | ||
| Line 11: | Line 13: | ||
| ===== O-Matrix ===== | ===== O-Matrix ===== | ||
| - | At this point, you should know the O-Matrix of your experiment. If not, go back to the section on understanding the [[processing:o_matrix|concept of the O-Matrix]]. | + | At this point, you should know the O-Matrix of your experiment. If not, go back to the section on understanding the [[dac_experiments:geometry|concept of the O-Matrix]]. |
| ===== Loading peaks ===== | ===== Loading peaks ===== | ||
| - | ImageD11 can be started by typing the following command in a terminal | + | For calculating the G vectors, we use [[software: |
| | | ||
| - | Peaks found during [[processing: | + | Peaks found during [[processing: |
| If things look weird after you switch from (y/z) to 2θ/η plots of vice-versa, trying calling the '' | If things look weird after you switch from (y/z) to 2θ/η plots of vice-versa, trying calling the '' | ||
| Line 24: | Line 26: | ||
| ===== ImageD11 Calibration ===== | ===== ImageD11 Calibration ===== | ||
| - | Before you check the plots you should | + | Preferably, this step should |
| - | Next you can have a look at the tth/eta plot. Most of the peaks should appear to be on imaginary vertical lines. Zoom in and check, if these lines are completely vertical. If not, you might have strain in your sample. If the line looks like a sinus curve of exactly one period | + | In diamond anvil cell beamlines, this step is often performed with a CeO< |
| - | At some point you can click on Transformation –> Add unit cell peaks. Red tick marks will appear which indicate the expected positions of the vertical lines. With this you can check whether your input parameters (cell parameters, detector distance, …) were correct. | + | Go in to '' |
| + | * the sample symmetry and unit cell parameters, | ||
| + | * the O-Matrix, | ||
| + | * the x-ray wavelength, | ||
| + | * the sample to detector distance, | ||
| + | * information on beam center. | ||
| + | |||
| + | Because of different conventions used by different softwares, the beam center might change from your calibration (in [[software: | ||
| + | |||
| + | Most of the peaks should appear to be on imaginary vertical lines. Zoom in and check, if these lines are actually vertical. If not, you might | ||
| + | * have strain in your sample, | ||
| + | * have a wrong beam center, | ||
| + | * need to refine the detector tilts. | ||
| + | |||
| + | [{{ : | ||
| + | |||
| + | At this point, you should | ||
| + | |||
| + | If you sample is strained, there is nothing you can do beyond this step. Your calibration of [[software: | ||
| + | |||
| + | If not, you a ready for a final refinement of the experimental parameters. You should start by refining the '' | ||
| + | |||
| + | At the end of the calibration, | ||
| + | |||
| + | Save the experimental parameters with '' | ||
| + | |||
| + | You are ready for G-vectors calculations. | ||
| ===== Computing G-vectors with ImageD11 ===== | ===== Computing G-vectors with ImageD11 ===== | ||
| - | For the calculation, | + | Once [[software: |
| - | You can compute the G-vectors by following three steps: | + | - load your peaks (e.g. the [[fileformat: |
| - | - Click //Transformation// --> | + | - make sure the ImageD11 |
| - | - Click //Transformation// --> | + | - Click '' |
| - | - Click // | + | - Click '' |
| + | |||
| + | [[software: | ||
| + | |||
| + | Note that, at this point, [[software: | ||
| + | |||
| + | While [[processing: | ||
| + | |||
| + | ===== Optional step: evaluating g-vectors ===== | ||
| + | |||
| + | In [[software: | ||
| + | |||
| + | The results are visible in the command window, for each potential Debye ring, the output shows h, k, l, the multiplicity of the reflection, and the number of g-vectors that can be potentially assigned to this ring. Intense powder diffraction rings should have many g-vectors assigned, low-intensity rings should have few g-vectors assigned, and extinct rings should have none. | ||
| + | |||
| + | Note that this information is not saved in the // | ||
| + | |||
| + | |||
| + | ===== Optionnal step: better list of g-vectors based on cif file ===== | ||
| + | |||
| + | In some cases (complex silicates with many peaks, multi-phase indexing, etc) it can be useful to have a better list of peaks in the g-vector file. This list should be calculated from a CIF file for the phase you will try to index. | ||
| + | |||
| + | The procedure is a bit tedious, as follow: | ||
| + | * Create a CIF file for the phase you are trying to index, with the proper unit cell parameters and atomic positions, | ||
| + | * Use the [[processing: | ||
| + | * Peaks | ||
processing/compute_gvectors.1550580435.txt.gz · Last modified: by smerkel
