orGUI 1.0.1__tar.gz

orgui-1.0.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2020-2024 Timo Fuchs
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

orgui-1.0.1/PKG-INFO

@@ -0,0 +1,147 @@
+Metadata-Version: 2.1
+Name: orGUI
+Version: 1.0.1
+Summary: orGUI: Orientation and Integration with 2D detectors
+Author-email: Timo Fuchs <fuchs@physik.uni-kiel.de>
+License: MIT License
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Win32 (MS Windows)
+Classifier: Environment :: X11 Applications :: Qt
+Classifier: Intended Audience :: End Users/Desktop
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: MacOS :: MacOS X
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Topic :: Scientific/Engineering :: Chemistry
+Classifier: Topic :: Scientific/Engineering :: Physics
+Classifier: Topic :: Scientific/Engineering :: Visualization
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.7
+Description-Content-Type: text/x-rst
+License-File: LICENSE
+Requires-Dist: numpy>=1.12
+Requires-Dist: scipy>=1.0
+Requires-Dist: matplotlib>=1.2
+Requires-Dist: fabio>=0.7
+Requires-Dist: silx>=1.1
+Requires-Dist: pyFAI>=0.19
+Requires-Dist: pymca>=5.3
+Requires-Dist: xraydb>=4.0
+Requires-Dist: pytz>=2022
+Provides-Extra: console
+Requires-Dist: qtconsole; extra == "console"
+Provides-Extra: speedup
+Requires-Dist: numba; extra == "speedup"
+
+
+orGUI: Orientation and Integration with 2D detectors
+====================================================
+
+.. |logo| image:: ./orgui/resources/icons/logo.svg
+   :height: 320px
+   
+|logo|
+
+orGUI is a software that can be used to determine the orientation of single crystal samples in X-ray diffraction experiments 
+from the observation of few reflections on a large, statinary 2D detector. 
+The settings of a 4-circle sample positioning stage as used for surface X-ray diffraction can be calculated. 
+
+Its primary usecase is High Energy Surface X-ray Diffraction (`HESXRD <https://doi.org/10.1126/science.1246834>`_) or Transmission Surface Diffraction (`TSD <https://doi.org/10.1021/acs.jpclett.7b00332>`_). 
+
+Intensity integration is possible along arbitrary directions in reciprocal space (in reciprocal lattice coordinates (*h k l*)). Stationary and rocking scans can be integrated. 
+In addition, the crystal orientation obtained by *orGUI* can be used for further processing with other software such as `binoculars <https://github.com/id03/binoculars>`_, which is described `here <https://doi.org/10.1107/S1600576715009607>`_. 
+Examples for the application of orGUI and binoculars for CTR data analysis is described in the Supporting Information of `this <https://doi.org/10.1002/anie.202304293>`__ paper or the Methods section of `this <https://doi.org/10.1038/s41929-020-0497-y>`__ paper.
+
+
+Installation
+------------
+
+To install orGUI (and all its dependencies), run:
+
+.. code-block:: bash
+
+    pip install orGUI[full]
+
+To install orGUI with a minimal set of dependencies, run:
+
+.. code-block:: bash
+
+    pip install orGUI
+	
+Getting started
+---------------
+
+*orGUI* can be started by the shell command `orGUI`. *orGUI* can also be started preconfigured with a configuration file `<configfile>` by typing
+
+.. code-block:: bash
+
+   orGUI <configfile>
+   
+All configuration is accessible in the user interface in the menu `Config->Machine parameters` and `Config->Crystal parameters`. 
+Examples of configuration files are provided with the `source code <https://doi.org/10.5281/zenodo.12592485>`_.
+
+*orGUI* is designed to handle data, which is saved in a `NEXUS <https://doi.org/10.1107/S1600576714027575>`_ format or a combination of `SPEC <https://certif.com/spec.html>`_ files and separately saved image files. 
+The file browser on the left side of orGUI shows the contents of the NEXUS or SPEC file, which typically contain multiple scans. Double clicking a scan in the file browser will open the specified scan.
+
+Data is typically saved differently (i.e. counter names, image locations, etc.) at different beamlines. Backends for loading scan data currently only exists for ID31 at the ESRF and P21.2 at DESY. 
+Loading data from other beamlines requires writing a new backend, which handles the loading of the scan data. The backends are located in `orgui/backend` of the source directory. 
+Documentation about writing new backends will follow in a future release. Please create an issue on Github or write an Email for help on writing a new backend.
+
+A simplistic backend for loading of bare image data without meta data information is available under `file->Generate scan from images`. 
+
+
+Documentation
+-------------
+
+A detailed documentation is not yet available, but will be provided in a future release.
+
+.. |diffractometer| image:: ./orgui/resources/icons/diffractometer_v3.png
+   :height: 360px
+   
+|diffractometer|
+
+orGUI uses the diffractometer convention by `Lohmeier & Vlieg 1993 <https://doi.org/10.1107/S0021889893004868>`_. However, the phi-circle rotates around the x-axis instead of the z-axis!. The azimuth angle in "machine parameters" rotates the whole diffractometer around the primary beam direction. Also :math:`$\theta = - \omega$`. (Since at ID31 the :math:`$\theta$` rotation is right-handed).
+xyz in lab frame is: y along beam direction, z along direction defined by azimuth (when azimuth = 90°, z points upwards), x perpendicular to both. 
+The detector geometry of orGUI is adapted from the commonly used python package `pyFAI <https://pyfai.readthedocs.io/en/stable/>`_, which enables comprehensive detector geometry calibration.
+It is recommended to determine the position of the X-ray detector from the Debye-Scherrer rings of a X-ray diffraction calibration standard such as CeO2 with the `geometry calibration tools <https://pyfai.readthedocs.io/en/stable/usage/cookbook/calib-gui/index.html>`_ of pyFAI.
+The resulting `poni` file can currently only be loaded in orGUI by setting the `poni` parameter in the `Machine` section of the orGUI config file to the poni file location. The orGUI config file must then be loaded.
+
+Here is a simplistic description of the usual workflow for crystal truncation rod integration (a more complete manual will follow): 
+
+For setting the orientation matrix, there are 2 methods available:
+
+1. Expert mode: This is in the menu Reciprocal Space -> Edit orientation matrix. This is more intended to be used if symmetries can be directly observed at specific angle settings and applies more to Transmission Diffraction (e.g. if you see that two Bragg reflections have identical intensities, a reference position can be obtained from that). This is not really extremely useful for Grazing incidence geometry since you have to think about what you are doing.
+
+2. Conventional setting of matrix using reference reflections (`Busing & Levy <https://doi.org/10.1107/S0365110X67000970>`_): The images and the window "Reciprocal space navigation" is used for that. Double clicking at any position in the image will set a red reference reflection at this specific image. The position of the marker on the image defines the scattering angles and the image number gives the sample rotation angle (i.e. theta) of the reference reflection. You can drag+drop the marker around in the image and the image number can be changed with the two buttons in the top right corner of the "Reciprocal space navigation" window (one button selects the current image for the chosen refllection; with the other you can jump to the image which was previously selected for the reflection). Usually the HKL values are wrong when you add a reflection. This can be overridden in the table in the Reciprocal space navigation window. To calculate the matrix click "calculate U". This function also works with only one reference reflection by assuming that the L axis is pointing towards the z/azimuth-direction (Enable View->machine parameters to display a marker at the z-direction). For other geometries you need at least 2 reference reflections. So what I ususally do is to search for a nicely visible reflection close to L = 0 (Either a Bragg reflection or a CTR at L = 0 usually work fine.)
+
+When the matrix is set correctly, the calculated CTR reflections (Enable View->CTR reflections) should match up with the ones in the data when you change the active image.
+To integrate a stationary scan (i.e. for each image, find the intersection of the CTR with the image and integrate a ROI around it), use hklscan in the ROI integration tab on the left side. To visualize the ROI on the image, enable View-> show ROI. Lorentz correction is not yet automatically applied here! Setting a pixel mask works by using the mask tool at the top of the image view (it is the mask icon).
+
+
+There is now a also a rocking scan integration feature, which usually gives better integrated CTR, but is not yet optimized for computation time currently takes a long time to compute. 
+
+
+Examples
+--------
+
+Some examples of configuration files are provided with the
+`source code <https://doi.org/10.5281/zenodo.12592485>`_.
+
+
+License
+-------
+
+The source code of *orGUI* is licensed under the MIT license.
+
+Citation
+--------
+
+*orGUI* releases can be cited via their DOI on Zenodo: |zenodo DOI|
+
+.. |zenodo DOI| image:: https://zenodo.org/badge/DOI/10.5281/zenodo.12592485.svg
+  :target: https://doi.org/10.5281/zenodo.12592485

orgui-1.0.1/README.rst

@@ -0,0 +1,107 @@
+
+orGUI: Orientation and Integration with 2D detectors
+====================================================
+
+.. |logo| image:: ./orgui/resources/icons/logo.svg
+   :height: 320px
+   
+|logo|
+
+orGUI is a software that can be used to determine the orientation of single crystal samples in X-ray diffraction experiments 
+from the observation of few reflections on a large, statinary 2D detector. 
+The settings of a 4-circle sample positioning stage as used for surface X-ray diffraction can be calculated. 
+
+Its primary usecase is High Energy Surface X-ray Diffraction (`HESXRD <https://doi.org/10.1126/science.1246834>`_) or Transmission Surface Diffraction (`TSD <https://doi.org/10.1021/acs.jpclett.7b00332>`_). 
+
+Intensity integration is possible along arbitrary directions in reciprocal space (in reciprocal lattice coordinates (*h k l*)). Stationary and rocking scans can be integrated. 
+In addition, the crystal orientation obtained by *orGUI* can be used for further processing with other software such as `binoculars <https://github.com/id03/binoculars>`_, which is described `here <https://doi.org/10.1107/S1600576715009607>`_. 
+Examples for the application of orGUI and binoculars for CTR data analysis is described in the Supporting Information of `this <https://doi.org/10.1002/anie.202304293>`__ paper or the Methods section of `this <https://doi.org/10.1038/s41929-020-0497-y>`__ paper.
+
+
+Installation
+------------
+
+To install orGUI (and all its dependencies), run:
+
+.. code-block:: bash
+
+    pip install orGUI[full]
+
+To install orGUI with a minimal set of dependencies, run:
+
+.. code-block:: bash
+
+    pip install orGUI
+	
+Getting started
+---------------
+
+*orGUI* can be started by the shell command `orGUI`. *orGUI* can also be started preconfigured with a configuration file `<configfile>` by typing
+
+.. code-block:: bash
+
+   orGUI <configfile>
+   
+All configuration is accessible in the user interface in the menu `Config->Machine parameters` and `Config->Crystal parameters`. 
+Examples of configuration files are provided with the `source code <https://doi.org/10.5281/zenodo.12592485>`_.
+
+*orGUI* is designed to handle data, which is saved in a `NEXUS <https://doi.org/10.1107/S1600576714027575>`_ format or a combination of `SPEC <https://certif.com/spec.html>`_ files and separately saved image files. 
+The file browser on the left side of orGUI shows the contents of the NEXUS or SPEC file, which typically contain multiple scans. Double clicking a scan in the file browser will open the specified scan.
+
+Data is typically saved differently (i.e. counter names, image locations, etc.) at different beamlines. Backends for loading scan data currently only exists for ID31 at the ESRF and P21.2 at DESY. 
+Loading data from other beamlines requires writing a new backend, which handles the loading of the scan data. The backends are located in `orgui/backend` of the source directory. 
+Documentation about writing new backends will follow in a future release. Please create an issue on Github or write an Email for help on writing a new backend.
+
+A simplistic backend for loading of bare image data without meta data information is available under `file->Generate scan from images`. 
+
+
+Documentation
+-------------
+
+A detailed documentation is not yet available, but will be provided in a future release.
+
+.. |diffractometer| image:: ./orgui/resources/icons/diffractometer_v3.png
+   :height: 360px
+   
+|diffractometer|
+
+orGUI uses the diffractometer convention by `Lohmeier & Vlieg 1993 <https://doi.org/10.1107/S0021889893004868>`_. However, the phi-circle rotates around the x-axis instead of the z-axis!. The azimuth angle in "machine parameters" rotates the whole diffractometer around the primary beam direction. Also :math:`$\theta = - \omega$`. (Since at ID31 the :math:`$\theta$` rotation is right-handed).
+xyz in lab frame is: y along beam direction, z along direction defined by azimuth (when azimuth = 90°, z points upwards), x perpendicular to both. 
+The detector geometry of orGUI is adapted from the commonly used python package `pyFAI <https://pyfai.readthedocs.io/en/stable/>`_, which enables comprehensive detector geometry calibration.
+It is recommended to determine the position of the X-ray detector from the Debye-Scherrer rings of a X-ray diffraction calibration standard such as CeO2 with the `geometry calibration tools <https://pyfai.readthedocs.io/en/stable/usage/cookbook/calib-gui/index.html>`_ of pyFAI.
+The resulting `poni` file can currently only be loaded in orGUI by setting the `poni` parameter in the `Machine` section of the orGUI config file to the poni file location. The orGUI config file must then be loaded.
+
+Here is a simplistic description of the usual workflow for crystal truncation rod integration (a more complete manual will follow): 
+
+For setting the orientation matrix, there are 2 methods available:
+
+1. Expert mode: This is in the menu Reciprocal Space -> Edit orientation matrix. This is more intended to be used if symmetries can be directly observed at specific angle settings and applies more to Transmission Diffraction (e.g. if you see that two Bragg reflections have identical intensities, a reference position can be obtained from that). This is not really extremely useful for Grazing incidence geometry since you have to think about what you are doing.
+
+2. Conventional setting of matrix using reference reflections (`Busing & Levy <https://doi.org/10.1107/S0365110X67000970>`_): The images and the window "Reciprocal space navigation" is used for that. Double clicking at any position in the image will set a red reference reflection at this specific image. The position of the marker on the image defines the scattering angles and the image number gives the sample rotation angle (i.e. theta) of the reference reflection. You can drag+drop the marker around in the image and the image number can be changed with the two buttons in the top right corner of the "Reciprocal space navigation" window (one button selects the current image for the chosen refllection; with the other you can jump to the image which was previously selected for the reflection). Usually the HKL values are wrong when you add a reflection. This can be overridden in the table in the Reciprocal space navigation window. To calculate the matrix click "calculate U". This function also works with only one reference reflection by assuming that the L axis is pointing towards the z/azimuth-direction (Enable View->machine parameters to display a marker at the z-direction). For other geometries you need at least 2 reference reflections. So what I ususally do is to search for a nicely visible reflection close to L = 0 (Either a Bragg reflection or a CTR at L = 0 usually work fine.)
+
+When the matrix is set correctly, the calculated CTR reflections (Enable View->CTR reflections) should match up with the ones in the data when you change the active image.
+To integrate a stationary scan (i.e. for each image, find the intersection of the CTR with the image and integrate a ROI around it), use hklscan in the ROI integration tab on the left side. To visualize the ROI on the image, enable View-> show ROI. Lorentz correction is not yet automatically applied here! Setting a pixel mask works by using the mask tool at the top of the image view (it is the mask icon).
+
+
+There is now a also a rocking scan integration feature, which usually gives better integrated CTR, but is not yet optimized for computation time currently takes a long time to compute. 
+
+
+Examples
+--------
+
+Some examples of configuration files are provided with the
+`source code <https://doi.org/10.5281/zenodo.12592485>`_.
+
+
+License
+-------
+
+The source code of *orGUI* is licensed under the MIT license.
+
+Citation
+--------
+
+*orGUI* releases can be cited via their DOI on Zenodo: |zenodo DOI|
+
+.. |zenodo DOI| image:: https://zenodo.org/badge/DOI/10.5281/zenodo.12592485.svg
+  :target: https://doi.org/10.5281/zenodo.12592485

orgui-1.0.1/orGUI.egg-info/PKG-INFO

@@ -0,0 +1,147 @@
+Metadata-Version: 2.1
+Name: orGUI
+Version: 1.0.1
+Summary: orGUI: Orientation and Integration with 2D detectors
+Author-email: Timo Fuchs <fuchs@physik.uni-kiel.de>
+License: MIT License
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Win32 (MS Windows)
+Classifier: Environment :: X11 Applications :: Qt
+Classifier: Intended Audience :: End Users/Desktop
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: MacOS :: MacOS X
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Topic :: Scientific/Engineering :: Chemistry
+Classifier: Topic :: Scientific/Engineering :: Physics
+Classifier: Topic :: Scientific/Engineering :: Visualization
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.7
+Description-Content-Type: text/x-rst
+License-File: LICENSE
+Requires-Dist: numpy>=1.12
+Requires-Dist: scipy>=1.0
+Requires-Dist: matplotlib>=1.2
+Requires-Dist: fabio>=0.7
+Requires-Dist: silx>=1.1
+Requires-Dist: pyFAI>=0.19
+Requires-Dist: pymca>=5.3
+Requires-Dist: xraydb>=4.0
+Requires-Dist: pytz>=2022
+Provides-Extra: console
+Requires-Dist: qtconsole; extra == "console"
+Provides-Extra: speedup
+Requires-Dist: numba; extra == "speedup"
+
+
+orGUI: Orientation and Integration with 2D detectors
+====================================================
+
+.. |logo| image:: ./orgui/resources/icons/logo.svg
+   :height: 320px
+   
+|logo|
+
+orGUI is a software that can be used to determine the orientation of single crystal samples in X-ray diffraction experiments 
+from the observation of few reflections on a large, statinary 2D detector. 
+The settings of a 4-circle sample positioning stage as used for surface X-ray diffraction can be calculated. 
+
+Its primary usecase is High Energy Surface X-ray Diffraction (`HESXRD <https://doi.org/10.1126/science.1246834>`_) or Transmission Surface Diffraction (`TSD <https://doi.org/10.1021/acs.jpclett.7b00332>`_). 
+
+Intensity integration is possible along arbitrary directions in reciprocal space (in reciprocal lattice coordinates (*h k l*)). Stationary and rocking scans can be integrated. 
+In addition, the crystal orientation obtained by *orGUI* can be used for further processing with other software such as `binoculars <https://github.com/id03/binoculars>`_, which is described `here <https://doi.org/10.1107/S1600576715009607>`_. 
+Examples for the application of orGUI and binoculars for CTR data analysis is described in the Supporting Information of `this <https://doi.org/10.1002/anie.202304293>`__ paper or the Methods section of `this <https://doi.org/10.1038/s41929-020-0497-y>`__ paper.
+
+
+Installation
+------------
+
+To install orGUI (and all its dependencies), run:
+
+.. code-block:: bash
+
+    pip install orGUI[full]
+
+To install orGUI with a minimal set of dependencies, run:
+
+.. code-block:: bash
+
+    pip install orGUI
+	
+Getting started
+---------------
+
+*orGUI* can be started by the shell command `orGUI`. *orGUI* can also be started preconfigured with a configuration file `<configfile>` by typing
+
+.. code-block:: bash
+
+   orGUI <configfile>
+   
+All configuration is accessible in the user interface in the menu `Config->Machine parameters` and `Config->Crystal parameters`. 
+Examples of configuration files are provided with the `source code <https://doi.org/10.5281/zenodo.12592485>`_.
+
+*orGUI* is designed to handle data, which is saved in a `NEXUS <https://doi.org/10.1107/S1600576714027575>`_ format or a combination of `SPEC <https://certif.com/spec.html>`_ files and separately saved image files. 
+The file browser on the left side of orGUI shows the contents of the NEXUS or SPEC file, which typically contain multiple scans. Double clicking a scan in the file browser will open the specified scan.
+
+Data is typically saved differently (i.e. counter names, image locations, etc.) at different beamlines. Backends for loading scan data currently only exists for ID31 at the ESRF and P21.2 at DESY. 
+Loading data from other beamlines requires writing a new backend, which handles the loading of the scan data. The backends are located in `orgui/backend` of the source directory. 
+Documentation about writing new backends will follow in a future release. Please create an issue on Github or write an Email for help on writing a new backend.
+
+A simplistic backend for loading of bare image data without meta data information is available under `file->Generate scan from images`. 
+
+
+Documentation
+-------------
+
+A detailed documentation is not yet available, but will be provided in a future release.
+
+.. |diffractometer| image:: ./orgui/resources/icons/diffractometer_v3.png
+   :height: 360px
+   
+|diffractometer|
+
+orGUI uses the diffractometer convention by `Lohmeier & Vlieg 1993 <https://doi.org/10.1107/S0021889893004868>`_. However, the phi-circle rotates around the x-axis instead of the z-axis!. The azimuth angle in "machine parameters" rotates the whole diffractometer around the primary beam direction. Also :math:`$\theta = - \omega$`. (Since at ID31 the :math:`$\theta$` rotation is right-handed).
+xyz in lab frame is: y along beam direction, z along direction defined by azimuth (when azimuth = 90°, z points upwards), x perpendicular to both. 
+The detector geometry of orGUI is adapted from the commonly used python package `pyFAI <https://pyfai.readthedocs.io/en/stable/>`_, which enables comprehensive detector geometry calibration.
+It is recommended to determine the position of the X-ray detector from the Debye-Scherrer rings of a X-ray diffraction calibration standard such as CeO2 with the `geometry calibration tools <https://pyfai.readthedocs.io/en/stable/usage/cookbook/calib-gui/index.html>`_ of pyFAI.
+The resulting `poni` file can currently only be loaded in orGUI by setting the `poni` parameter in the `Machine` section of the orGUI config file to the poni file location. The orGUI config file must then be loaded.
+
+Here is a simplistic description of the usual workflow for crystal truncation rod integration (a more complete manual will follow): 
+
+For setting the orientation matrix, there are 2 methods available:
+
+1. Expert mode: This is in the menu Reciprocal Space -> Edit orientation matrix. This is more intended to be used if symmetries can be directly observed at specific angle settings and applies more to Transmission Diffraction (e.g. if you see that two Bragg reflections have identical intensities, a reference position can be obtained from that). This is not really extremely useful for Grazing incidence geometry since you have to think about what you are doing.
+
+2. Conventional setting of matrix using reference reflections (`Busing & Levy <https://doi.org/10.1107/S0365110X67000970>`_): The images and the window "Reciprocal space navigation" is used for that. Double clicking at any position in the image will set a red reference reflection at this specific image. The position of the marker on the image defines the scattering angles and the image number gives the sample rotation angle (i.e. theta) of the reference reflection. You can drag+drop the marker around in the image and the image number can be changed with the two buttons in the top right corner of the "Reciprocal space navigation" window (one button selects the current image for the chosen refllection; with the other you can jump to the image which was previously selected for the reflection). Usually the HKL values are wrong when you add a reflection. This can be overridden in the table in the Reciprocal space navigation window. To calculate the matrix click "calculate U". This function also works with only one reference reflection by assuming that the L axis is pointing towards the z/azimuth-direction (Enable View->machine parameters to display a marker at the z-direction). For other geometries you need at least 2 reference reflections. So what I ususally do is to search for a nicely visible reflection close to L = 0 (Either a Bragg reflection or a CTR at L = 0 usually work fine.)
+
+When the matrix is set correctly, the calculated CTR reflections (Enable View->CTR reflections) should match up with the ones in the data when you change the active image.
+To integrate a stationary scan (i.e. for each image, find the intersection of the CTR with the image and integrate a ROI around it), use hklscan in the ROI integration tab on the left side. To visualize the ROI on the image, enable View-> show ROI. Lorentz correction is not yet automatically applied here! Setting a pixel mask works by using the mask tool at the top of the image view (it is the mask icon).
+
+
+There is now a also a rocking scan integration feature, which usually gives better integrated CTR, but is not yet optimized for computation time currently takes a long time to compute. 
+
+
+Examples
+--------
+
+Some examples of configuration files are provided with the
+`source code <https://doi.org/10.5281/zenodo.12592485>`_.
+
+
+License
+-------
+
+The source code of *orGUI* is licensed under the MIT license.
+
+Citation
+--------
+
+*orGUI* releases can be cited via their DOI on Zenodo: |zenodo DOI|
+
+.. |zenodo DOI| image:: https://zenodo.org/badge/DOI/10.5281/zenodo.12592485.svg
+  :target: https://doi.org/10.5281/zenodo.12592485

orgui-1.0.1/orGUI.egg-info/SOURCES.txt

@@ -0,0 +1,86 @@
+LICENSE
+README.rst
+pyproject.toml
+orGUI.egg-info/PKG-INFO
+orGUI.egg-info/SOURCES.txt
+orGUI.egg-info/dependency_links.txt
+orGUI.egg-info/entry_points.txt
+orGUI.egg-info/requires.txt
+orGUI.egg-info/top_level.txt
+orgui/__init__.py
+orgui/main.py
+orgui/app/ArrayTableDialog.py
+orgui/app/QReflectionSelector.py
+orgui/app/QScanSelector.py
+orgui/app/QUBCalculator.py
+orgui/app/__init__.py
+orgui/app/database.py
+orgui/app/orGUI.py
+orgui/app/qutils.py
+orgui/backend/__init__.py
+orgui/backend/backends.py
+orgui/backend/scans.py
+orgui/backend/udefaults.py
+orgui/backend/universalScanLoader.py
+orgui/backend/beamline/ID31DiffractLinTilt.py
+orgui/backend/beamline/P212_tools.py
+orgui/backend/beamline/__init__.py
+orgui/backend/beamline/fio_reader.py
+orgui/backend/beamline/id31_tools.py
+orgui/datautils/__init__.py
+orgui/datautils/util.py
+orgui/datautils/xrayutils/CTRcalc.py
+orgui/datautils/xrayutils/CTRopt.py
+orgui/datautils/xrayutils/CTRplotutil.py
+orgui/datautils/xrayutils/DetectorCalibration.py
+orgui/datautils/xrayutils/HKLVlieg.py
+orgui/datautils/xrayutils/ReciprocalNavigation.py
+orgui/datautils/xrayutils/_CTRcalc_accel.py
+orgui/datautils/xrayutils/__init__.py
+orgui/datautils/xrayutils/element_data.py
+orgui/datautils/xrayutils/test/__init__.py
+orgui/datautils/xrayutils/test/test_CTRcalc.py
+orgui/datautils/xrayutils/test/test_DetectorCalibration.py
+orgui/datautils/xrayutils/test/test_HKLcalc.py
+orgui/datautils/xrayutils/unitcells/Fe3O4(100).bul
+orgui/datautils/xrayutils/unitcells/Pt100.bul
+orgui/datautils/xrayutils/unitcells/Pt100_small.bul
+orgui/datautils/xrayutils/unitcells/Pt110.bul
+orgui/datautils/xrayutils/unitcells/Pt111.bul
+orgui/datautils/xrayutils/unitcells/Pt310.bul
+orgui/datautils/xrayutils/unitcells/Pt3O4(100).bul
+orgui/datautils/xrayutils/unitcells/PtO(001).bul
+orgui/datautils/xrayutils/unitcells/PtO(010).bul
+orgui/datautils/xrayutils/unitcells/PtO(100).bul
+orgui/datautils/xrayutils/unitcells/__init__.py
+orgui/datautils/xrayutils/unitcells/a-PtO2(0001).bul
+orgui/resources/__init__.py
+orgui/resources/icons/alpha.png
+orgui/resources/icons/alpha.svg
+orgui/resources/icons/diffractometer_v3.png
+orgui/resources/icons/disable-image.png
+orgui/resources/icons/disable-image.svg
+orgui/resources/icons/document-nx-open.png
+orgui/resources/icons/document-nx-open.svg
+orgui/resources/icons/document-nx-save.png
+orgui/resources/icons/document-nx-save.svg
+orgui/resources/icons/logo.png
+orgui/resources/icons/logo.svg
+orgui/resources/icons/max_image.png
+orgui/resources/icons/max_image.svg
+orgui/resources/icons/max_image2.png
+orgui/resources/icons/max_image2.svg
+orgui/resources/icons/search-image.png
+orgui/resources/icons/search-image.svg
+orgui/resources/icons/search-reflection.png
+orgui/resources/icons/search-reflection.svg
+orgui/resources/icons/search.png
+orgui/resources/icons/search.svg
+orgui/resources/icons/select-image.png
+orgui/resources/icons/select-image.svg
+orgui/resources/icons/set-reflection.png
+orgui/resources/icons/set-reflection.svg
+orgui/resources/icons/sum_image.png
+orgui/resources/icons/sum_image.svg
+orgui/resources/icons/sum_image2.png
+orgui/resources/icons/sum_image2.svg

orgui-1.0.1/orGUI.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

orgui-1.0.1/orGUI.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+orGUI = orgui.main:main

orgui-1.0.1/orGUI.egg-info/requires.txt

@@ -0,0 +1,15 @@
+numpy>=1.12
+scipy>=1.0
+matplotlib>=1.2
+fabio>=0.7
+silx>=1.1
+pyFAI>=0.19
+pymca>=5.3
+xraydb>=4.0
+pytz>=2022
+
+[console]
+qtconsole
+
+[speedup]
+numba

orgui-1.0.1/orGUI.egg-info/top_level.txt

@@ -0,0 +1 @@
+orgui

orgui-1.0.1/orgui/__init__.py

@@ -0,0 +1,36 @@
+# -*- coding: utf-8 -*-
+# /*##########################################################################
+#
+# Copyright (c) 2020-2024 Timo Fuchs
+#
+# Permission is hereby granted, free of charge, to any person obtaining a copy
+# of this software and associated documentation files (the "Software"), to deal
+# in the Software without restriction, including without limitation the rights
+# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+# copies of the Software, and to permit persons to whom the Software is
+# furnished to do so, subject to the following conditions:
+#
+# The above copyright notice and this permission notice shall be included in
+# all copies or substantial portions of the Software.
+#
+# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+# THE SOFTWARE.
+#
+# ###########################################################################*/
+"""Module descripiton
+
+"""
+__author__ = "Timo Fuchs"
+__copyright__ = "Copyright 2020-2024 Timo Fuchs"
+__credits__ = []
+__license__ = "MIT License"
+__version__ = "1.0.1"
+__maintainer__ = "Timo Fuchs"
+__email__ = "fuchs@physik.uni-kiel.de"
+
+__all__ = ['main']