optics_design_workbench 0.4.3__tar.gz

optics_design_workbench-0.4.3/.gitattributes

@@ -0,0 +1,2 @@
+*.ipynb filter=clean-ipynb
+

optics_design_workbench-0.4.3/.github/workflows/python-app.yml

@@ -0,0 +1,34 @@
+# This workflow will install Python dependencies, run tests and lint with a single version of Python
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python
+
+name: Python application
+
+on:
+  push:
+    branches: [ "master" ]
+  pull_request:
+    branches: [ "master" ]
+
+permissions:
+  contents: read
+
+jobs:
+  build-and-test:
+    strategy:
+      matrix:
+        version: ["v3.11", "v3.12", "v3.13"]
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+    - name: Install uv
+      uses: astral-sh/setup-uv@v5
+    - name: Install dependencies
+      run: |
+        git fetch --deepen 50
+        uv venv --python=${{ matrix.version }}
+        uv pip install pytest
+        uv pip install jupyter nbconvert
+        uv sync --all-extras --dev
+    - name: Test with pytest
+      run: |
+        uv run pytest

optics_design_workbench-0.4.3/.gitignore

@@ -0,0 +1,28 @@
+fcstd
+build
+dist
+*.FCBak
+__pycache__
+*.ipynb_checkpoints*
+*.pkl
+*.pdf
+*.png
+*.jpg
+*.tar.gz
+*.egg-info
+*.nbconvert*
+**/*.OpticsDesign/raw/*
+**/*.OpticsDesign/**/*.pdf
+**/*.OpticsDesign/**/*.png
+**/*.OpticsDesign/**/*.jpg
+**/*.OpticsDesign/**/*.md
+**/*.OpticsDesign/**/*.txt
+**/*.OpticsDesign/**/*.log
+**/*.OpticsDesign/**/simulation-*
+*.md5
+test-docker/**/container-home
+*.AppImage
+releases
+
+# include screenshots in examples
+!examples/**/*.png

optics_design_workbench-0.4.3/LICENSE.txt

@@ -0,0 +1,66 @@
+
+GNU LESSER GENERAL PUBLIC LICENSE
+
+Version 3, 29 June 2007
+
+Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.
+0. Additional Definitions.
+
+As used herein, “this License” refers to version 3 of the GNU Lesser General Public License, and the “GNU GPL” refers to version 3 of the GNU General Public License.
+
+“The Library” refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
+
+An “Application” is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.
+
+A “Combined Work” is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the “Linked Version”.
+
+The “Minimal Corresponding Source” for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
+
+The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.
+1. Exception to Section 3 of the GNU GPL.
+
+You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.
+2. Conveying Modified Versions.
+
+If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:
+
+    a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or
+    b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
+
+3. Object Code Incorporating Material from Library Header Files.
+
+The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:
+
+    a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.
+    b) Accompany the object code with a copy of the GNU GPL and this license document.
+
+4. Combined Works.
+
+You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:
+
+    a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.
+    b) Accompany the Combined Work with a copy of the GNU GPL and this license document.
+    c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.
+    d) Do one of the following:
+        0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
+        1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.
+    e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)
+
+5. Combined Libraries.
+
+You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:
+
+    a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License.
+    b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
+
+6. Revised Versions of the GNU Lesser General Public License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.
+
+If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.

optics_design_workbench-0.4.3/MANIFEST.in

@@ -0,0 +1,2 @@
+include freecad/optics_design_workbench/icons/*
+

optics_design_workbench-0.4.3/PKG-INFO

@@ -0,0 +1,183 @@
+Metadata-Version: 2.4
+Name: optics_design_workbench
+Version: 0.4.3
+Summary: Physically accurate forward ray tracing for optics simulation and optimization with FreeCAD workbench frontend inspired by the FreeCAD OpticsWorkbench
+Project-URL: Homepage, https://github.com/zaphB/freecad.optics_design_workbench
+Project-URL: Repository, https://github.com/zaphB/freecad.optics_design_workbench.git
+Author-email: Philipp Bredol <philipp.bredol@rwth-aachen.de>
+License: 
+        GNU LESSER GENERAL PUBLIC LICENSE
+        
+        Version 3, 29 June 2007
+        
+        Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/>
+        
+        Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+        
+        This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.
+        0. Additional Definitions.
+        
+        As used herein, “this License” refers to version 3 of the GNU Lesser General Public License, and the “GNU GPL” refers to version 3 of the GNU General Public License.
+        
+        “The Library” refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
+        
+        An “Application” is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.
+        
+        A “Combined Work” is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the “Linked Version”.
+        
+        The “Minimal Corresponding Source” for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
+        
+        The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.
+        1. Exception to Section 3 of the GNU GPL.
+        
+        You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.
+        2. Conveying Modified Versions.
+        
+        If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:
+        
+            a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or
+            b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
+        
+        3. Object Code Incorporating Material from Library Header Files.
+        
+        The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:
+        
+            a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.
+            b) Accompany the object code with a copy of the GNU GPL and this license document.
+        
+        4. Combined Works.
+        
+        You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:
+        
+            a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.
+            b) Accompany the Combined Work with a copy of the GNU GPL and this license document.
+            c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.
+            d) Do one of the following:
+                0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
+                1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.
+            e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)
+        
+        5. Combined Libraries.
+        
+        You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:
+        
+            a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License.
+            b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
+        
+        6. Revised Versions of the GNU Lesser General Public License.
+        
+        The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+        
+        Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.
+        
+        If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.
+License-File: LICENSE.txt
+Requires-Python: >=3.10
+Requires-Dist: atomicwrites
+Requires-Dist: cloudpickle
+Requires-Dist: jupyterlab
+Requires-Dist: matplotlib
+Requires-Dist: numpy>1.24.4
+Requires-Dist: pyside6
+Requires-Dist: scipy>=1.14.0
+Requires-Dist: seaborn
+Requires-Dist: sympy
+Description-Content-Type: text/markdown
+
+# Optics Design Workbench
+
+This workbench was inspired by the [OpticsWorkbench](https://github.com/chbergmann/OpticsWorkbench) and aims to extend its functionality towards design and optimization of optical assemblies.
+
+Feel free to ask any question in the [forum thread](https://forum.freecad.org/viewtopic.php?t=89264).
+
+
+## Prerequisites
+
+FreeCAD version >=0.21, python packages numpy, scipy, matplotlib, atomicwrites. A jupyter notebook installation is recommended.
+
+
+## Installing the FreeCAD workbench
+
+To make the Optics Design Workbench available in FreeCAD, install it using FreeCAD's built in addon manager.
+
+If you want to install without the addon manager, head to the releases section and download the zipped source of your version of choice. Extract the downloaded zip to the Mod folder of your FreeCAD installation. Make sure that the folder containing the `init_gui.py` is on the third subfolder level below the Mod directory like this:
+
+```bash
+..../Mod/freecad.optics_design_workbench-1.2.3/freecad/optics_design_workbench/init_gui.py
+```
+
+
+## Installing for usage in external python shells and jupyter notebooks
+
+To install as a regular python package run
+
+```bash
+pip install optics_design_workbench
+```
+
+(Note that the package looks very much like a `freecad.optics_design_workbench` namespace package, however it is uploaded to PyPi just as `optics_design_workbench`, i.e., not being part of the freecad namespace. The reason for this is that the freecad base package is not pip-installable yet and is therefore very difficult to install in virtual environments. The `optics_design_workbench` without the namespace component does not rely on the freecad package to exist, therefore can be installed via pip in any virtual environment without any issue.)
+
+
+## Development installation
+
+Clone this repository, install the python module in development mode using `pip install -e .`. Create a symlink in your FreeCAD's Mod folder pointing to the directory of the cloned directory. With this setup, changes in the cloned repository folder will be effective immediately when restarting FreeCAD. Avoid using regular PyPi or addon manager installations in parallel with the development installation.
+
+
+## Getting started with examples
+
+To get started, FCStd files and corresponding jupyter notebooks can be found the examples folder of this repository.
+
+
+### Gaussian beam point source and detector
+
+[examples/1-source-and-detector](./examples/1-source-and-detector)
+
+#### Ray-fan simulation mode
+
+The ray-fan mode renders rays for cross-sections of the solid angle with a spacing matching the inverse power density of the light source. This mode renders fast and gives a good first impression where the optical power of your sources ends up.
+
+![ray-fan mode screenshot](./examples/1-source-and-detector/screenshot-ray-fan.png)
+
+
+#### Monte-Carlo simulation mode
+
+In the Monte-Carlo simulation mode, rays are placed randomly in the full solid angle according to the given power density of the light source. If the simulation is run in continuous mode, recorded ray hits will be stored to disk and can be loaded and further analyzed with the accompanying notebook in the example folder.
+
+![monte-carlo mode screenshot](./examples/1-source-and-detector/screenshot-monte-carlo.png)
+
+
+### Spherical lens and parabolic mirror
+
+[examples/2-lens-and-mirror](./examples/2-lens-and-mirror)
+
+Any geometric body in FreeCAD can become member of one of the `OpticalGroup`s to turn them into reflective, refractive, absorbing or ray-detecting objects. This example contains spherical lenses and slotted parabolic mirrors, transparent and absorbing detectors. When running the continuous simulation, folders for all objects that have set `Store Hits` to true will be generated.
+
+![lens and mirror screenshot](./examples/2-lens-and-mirror/screenshot.png)
+
+
+### Geometry parameter optimization
+
+[examples/3-parameter-sweeps](./examples/3-parameter-sweeps)
+
+All parameters of the FreeCAD model are accessible from an external python shell through the `jupyter_utils` submodule. The recommended workflow is to use a jupyter notebook for such edits (hence the module name). The example shows a simple spherical lens, the radius of which is optimized to minimize the spot size on a detector.
+
+
+## Troubleshooting
+
+When things don't work as expected first make sure you are actually running want you intend to run and whether the same workbench version is installed on the python and the FreeCAD side. To check this, run
+
+```python
+import optics_design_workbench
+optics_design_workbench.versionInfo()
+```
+
+in the FreeCAD python shell and
+
+```python
+import optics_design_workbench
+optics_design_workbench.versionInfo()
+```
+
+in your regular python shell of choice.
+
+Make sure that the workbench versions seen by FreeCAD and by python match and that all the displayed versions and paths match your expectations.

optics_design_workbench-0.4.3/README.md

@@ -0,0 +1,97 @@
+# Optics Design Workbench
+
+This workbench was inspired by the [OpticsWorkbench](https://github.com/chbergmann/OpticsWorkbench) and aims to extend its functionality towards design and optimization of optical assemblies.
+
+Feel free to ask any question in the [forum thread](https://forum.freecad.org/viewtopic.php?t=89264).
+
+
+## Prerequisites
+
+FreeCAD version >=0.21, python packages numpy, scipy, matplotlib, atomicwrites. A jupyter notebook installation is recommended.
+
+
+## Installing the FreeCAD workbench
+
+To make the Optics Design Workbench available in FreeCAD, install it using FreeCAD's built in addon manager.
+
+If you want to install without the addon manager, head to the releases section and download the zipped source of your version of choice. Extract the downloaded zip to the Mod folder of your FreeCAD installation. Make sure that the folder containing the `init_gui.py` is on the third subfolder level below the Mod directory like this:
+
+```bash
+..../Mod/freecad.optics_design_workbench-1.2.3/freecad/optics_design_workbench/init_gui.py
+```
+
+
+## Installing for usage in external python shells and jupyter notebooks
+
+To install as a regular python package run
+
+```bash
+pip install optics_design_workbench
+```
+
+(Note that the package looks very much like a `freecad.optics_design_workbench` namespace package, however it is uploaded to PyPi just as `optics_design_workbench`, i.e., not being part of the freecad namespace. The reason for this is that the freecad base package is not pip-installable yet and is therefore very difficult to install in virtual environments. The `optics_design_workbench` without the namespace component does not rely on the freecad package to exist, therefore can be installed via pip in any virtual environment without any issue.)
+
+
+## Development installation
+
+Clone this repository, install the python module in development mode using `pip install -e .`. Create a symlink in your FreeCAD's Mod folder pointing to the directory of the cloned directory. With this setup, changes in the cloned repository folder will be effective immediately when restarting FreeCAD. Avoid using regular PyPi or addon manager installations in parallel with the development installation.
+
+
+## Getting started with examples
+
+To get started, FCStd files and corresponding jupyter notebooks can be found the examples folder of this repository.
+
+
+### Gaussian beam point source and detector
+
+[examples/1-source-and-detector](./examples/1-source-and-detector)
+
+#### Ray-fan simulation mode
+
+The ray-fan mode renders rays for cross-sections of the solid angle with a spacing matching the inverse power density of the light source. This mode renders fast and gives a good first impression where the optical power of your sources ends up.
+
+![ray-fan mode screenshot](./examples/1-source-and-detector/screenshot-ray-fan.png)
+
+
+#### Monte-Carlo simulation mode
+
+In the Monte-Carlo simulation mode, rays are placed randomly in the full solid angle according to the given power density of the light source. If the simulation is run in continuous mode, recorded ray hits will be stored to disk and can be loaded and further analyzed with the accompanying notebook in the example folder.
+
+![monte-carlo mode screenshot](./examples/1-source-and-detector/screenshot-monte-carlo.png)
+
+
+### Spherical lens and parabolic mirror
+
+[examples/2-lens-and-mirror](./examples/2-lens-and-mirror)
+
+Any geometric body in FreeCAD can become member of one of the `OpticalGroup`s to turn them into reflective, refractive, absorbing or ray-detecting objects. This example contains spherical lenses and slotted parabolic mirrors, transparent and absorbing detectors. When running the continuous simulation, folders for all objects that have set `Store Hits` to true will be generated.
+
+![lens and mirror screenshot](./examples/2-lens-and-mirror/screenshot.png)
+
+
+### Geometry parameter optimization
+
+[examples/3-parameter-sweeps](./examples/3-parameter-sweeps)
+
+All parameters of the FreeCAD model are accessible from an external python shell through the `jupyter_utils` submodule. The recommended workflow is to use a jupyter notebook for such edits (hence the module name). The example shows a simple spherical lens, the radius of which is optimized to minimize the spot size on a detector.
+
+
+## Troubleshooting
+
+When things don't work as expected first make sure you are actually running want you intend to run and whether the same workbench version is installed on the python and the FreeCAD side. To check this, run
+
+```python
+import optics_design_workbench
+optics_design_workbench.versionInfo()
+```
+
+in the FreeCAD python shell and
+
+```python
+import optics_design_workbench
+optics_design_workbench.versionInfo()
+```
+
+in your regular python shell of choice.
+
+Make sure that the workbench versions seen by FreeCAD and by python match and that all the displayed versions and paths match your expectations.

optics_design_workbench-0.4.3/examples/1-source-and-detector/main.ipynb

@@ -0,0 +1,70 @@
+{
+ "cells": [
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from numpy import *\n",
+    "from matplotlib.pyplot import *\n",
+    "import pickle\n",
+    "import os"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "# Loading the data\n",
+    "\n",
+    "The simulation workers dump their results to disk every few seconds. To load all the results from a simulation, we have to unpickle all relevant pkl files. Here we assemble all found ray hit coordinates in the `allPoints` array:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "allPoints = None\n",
+    "for r, ds, fs in os.walk('main.opticalSimulationResults/run-0000-raw'):\n",
+    "  for f in fs:\n",
+    "    if f.endswith('.pkl'):\n",
+    "      with open(f'{r}/{f}', 'rb') as _f:\n",
+    "        blob = pickle.load(_f)\n",
+    "        allPoints = concatenate([allPoints, blob['points']]) if allPoints is not None else blob['points']"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "allPoints.shape"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "# Plot the results\n",
+    "\n",
+    "After loading the data, we can apply any data analysis tools to visualize or further analyze the data. For example we can plot a 2d histogram of the X and Y coordinates:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "hist2d(*allPoints[:,:2].T, bins=30);"
+   ]
+  }
+ ],
+ "metadata": {},
+ "nbformat": 4,
+ "nbformat_minor": 2
+}