User Tools
processing:compute_gvectors
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
processing:compute_gvectors [2019/05/09 12:15] matthias [Optional step: evaluating g-vectors] |
processing:compute_gvectors [2023/03/14 14:29] (current) smerkel |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| ===== Loading peaks ===== | ===== Loading peaks ===== | ||
| - | ImageD11 can be started by typing the following command in a terminal | + | For calculating the G vectors, we use [[software:imaged11|ImageD11]]. The software can be started by typing the following command in a terminal: |
| ImageD11_gui.py | ImageD11_gui.py | ||
| - | Peaks found during [[processing:search_for_peaks|peak search]] can be loaded by clicking on ''Transformation –> Load filtered peaks'' and choose the corresponding ''.flt'' file. You can display the peaks by calling the corresponding menu item in ''Transformation''. You can either plot peaks in the 2D diffraction geometry (y/z plot), or after transforming detector peak positions into diffraction 2θ and the azimuth η angles (2θ/η plot). | + | Peaks found during [[processing:search_for_peaks|peak search]] can be loaded by clicking on ''Transformation –> Load filtered peaks'' and choosing the corresponding ''.flt'' file. You can display the peaks by calling the corresponding menu item in ''Transformation''. You can either plot peaks in the 2D diffraction geometry (y/z plot), or after transforming detector peak positions into diffraction 2θ and the azimuth η angles (2θ/η plot). |
| If things look weird after you switch from (y/z) to 2θ/η plots of vice-versa, trying calling the ''Clear plot'' button at the bottom of the interface. ''Clear'' does only erase the plot, the data is still there. | If things look weird after you switch from (y/z) to 2θ/η plots of vice-versa, trying calling the ''Clear plot'' button at the bottom of the interface. ''Clear'' does only erase the plot, the data is still there. | ||
| 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<sub>2</sub> or a LaB<sub>6</sub> standard. | ||
| Go in to ''Transformation –> Edit parameters'' and enter all parameters you know. These include | Go in to ''Transformation –> Edit parameters'' and enter all parameters you know. These include | ||
| 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, the imaginary lines should now be completely straight (if you don't have strain). If they are not, you have more work to do. | At the end of the calibration, the imaginary lines should now be completely straight (if you don't have strain). If they are not, you have more work to do. | ||
| - | Save the experimental parameters with ''Transformation –> Save Parameters'', with a [[fileformat:imageD11_pars|.par]] or [[fileformat:imageD11_pars|.prm]] extension preferably. You will be able to use those for the rest of the processing of the current experiment. | + | Save the experimental parameters with ''Transformation –> Save Parameters'', with a [[fileformat:prm|.prm]] extension preferably. You will be able to use those for the rest of the processing of the current experiment. |
| You are ready for G-vectors calculations. | You are ready for G-vectors calculations. | ||
| Line 77: | Line 79: | ||
| Note that this information is not saved in the //.gve// file. G-vectors do not know which crystal they belong to. | 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:list-peaks-from-cif|timelessPeaksFromCIF]] to generate a list of peaks, with h, k, l, intensity, ds, and 2theta | ||
| + | * Peaks | ||
| + | |||
processing/compute_gvectors.1557404106.txt.gz · Last modified: 2019/05/09 12:15 by matthias
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
