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/21 07:52] – smerkel | processing:compute_gvectors [2023/03/14 15:29] (current) – smerkel | ||
|---|---|---|---|
| Line 13: | 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 26: | Line 26: | ||
| ===== ImageD11 Calibration ===== | ===== ImageD11 Calibration ===== | ||
| - | Preferably, this step should be performed with data collected on calibrant, for which you are sure of the unit cell parameters. | + | Preferably, this step should be performed with data collected on calibrant, for which you are sure of the unit cell parameters, which is free of strain, and with a controlled microstructures. |
| + | |||
| + | In diamond anvil cell beamlines, this step is often performed with a CeO< | ||
| Go in to '' | Go in to '' | ||
| Line 32: | Line 34: | ||
| * the O-Matrix, | * the O-Matrix, | ||
| * the x-ray wavelength, | * the x-ray wavelength, | ||
| - | * the sample to dectector, | + | * the sample to detector distance, |
| * information on beam center. | * information on beam center. | ||
| Line 52: | Line 54: | ||
| At the end of the calibration, | At the end of the calibration, | ||
| - | Save the experimental parameters with '' | + | Save the experimental parameters with '' |
| You are ready for G-vectors calculations. | You are ready for G-vectors calculations. | ||
| Line 66: | Line 68: | ||
| [[software: | [[software: | ||
| - | Note that, at this point, [[software: | + | Note that, at this point, [[software: |
| + | |||
| + | While [[processing: | ||
| ===== Optional step: evaluating g-vectors ===== | ===== Optional step: evaluating g-vectors ===== | ||
| Line 72: | Line 76: | ||
| In [[software: | In [[software: | ||
| - | The results are visible in the command window, | + | The results are visible in the command window, |
| + | |||
| + | Note that this information is not saved in the //.gve// file. G-vectors do not know which crystal they belong to. | ||
| + | |||
| + | |||
| + | ===== 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 | ||
| - | With that G-vectors file, you will be able to use GrainSpotter to find your original grains. | ||
processing/compute_gvectors.1550731947.txt.gz · Last modified: by smerkel
