PyGEL3D 0.8.0__py3-none-win_amd64.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- pygel3d/PyGEL.dll +0 -0
- pygel3d/__init__.py +389 -0
- pygel3d/experimental/__init__.py +1 -0
- pygel3d/experimental/hmesh.py +32 -0
- pygel3d/gl_display.py +127 -0
- pygel3d/graph.py +290 -0
- pygel3d/hmesh.py +1112 -0
- pygel3d/jupyter_display.py +91 -0
- pygel3d/spatial.py +40 -0
- pygel3d-0.8.0.dist-info/METADATA +159 -0
- pygel3d-0.8.0.dist-info/RECORD +14 -0
- pygel3d-0.8.0.dist-info/WHEEL +5 -0
- pygel3d-0.8.0.dist-info/licenses/LICENSE.md +27 -0
- pygel3d-0.8.0.dist-info/top_level.txt +1 -0
|
@@ -0,0 +1,91 @@
|
|
|
1
|
+
""" This is a module with a function, display, that provides functionality for displaying a
|
|
2
|
+
Manifold or a Graph as an interactive 3D model in a Jupyter Notebook. It is based on
|
|
3
|
+
plotly. """
|
|
4
|
+
|
|
5
|
+
from numpy.typing import ArrayLike
|
|
6
|
+
from pygel3d.hmesh import Manifold, triangulate
|
|
7
|
+
from pygel3d.graph import Graph
|
|
8
|
+
from numpy import array
|
|
9
|
+
import plotly.graph_objs as go
|
|
10
|
+
import plotly.offline as py
|
|
11
|
+
|
|
12
|
+
EXPORT_MODE = False
|
|
13
|
+
|
|
14
|
+
def set_export_mode(_exp_mode: bool = True):
|
|
15
|
+
""" Calling this function will set export mode to true. It is necessary
|
|
16
|
+
to do so if we wish to export a notebook containing interactive
|
|
17
|
+
plotly graphics (made with display below) to HTML. In other words, this function
|
|
18
|
+
should not necessarily be called in normal usage but only when we export to HTML. It is
|
|
19
|
+
then called once in the beginning of the notebook. However, as a bit of a twist on
|
|
20
|
+
this story, it appears that if we don't call this function, any call to display must
|
|
21
|
+
be the last thing that happens in a cell. So, maybe it is best to always call
|
|
22
|
+
set_export_mode in the beginning of a notebook.
|
|
23
|
+
"""
|
|
24
|
+
global EXPORT_MODE
|
|
25
|
+
EXPORT_MODE=_exp_mode
|
|
26
|
+
if EXPORT_MODE:
|
|
27
|
+
py.init_notebook_mode(connected=False)
|
|
28
|
+
|
|
29
|
+
def display(m: Manifold | Graph, wireframe: bool = True, smooth: bool = True, data: ArrayLike | None = None):
|
|
30
|
+
""" The display function shows an interactive presentation of the Manifold, m, inside
|
|
31
|
+
a Jupyter Notebook. wireframe=True means that a wireframe view of the mesh is
|
|
32
|
+
superimposed on the 3D model. If smooth=True, the mesh is rendered with vertex
|
|
33
|
+
normals. Otherwise, the mesh is rendered with face normals. If data=None, the
|
|
34
|
+
mesh is shown in a light grey color. If data contains an array of scalar values
|
|
35
|
+
per vertex, these are mapped to colors used to color the mesh. Finally, note that
|
|
36
|
+
m can also be a Graph. In that case the display function just draws the edges as
|
|
37
|
+
black lines. """
|
|
38
|
+
mesh_data = []
|
|
39
|
+
if isinstance(m, Manifold):
|
|
40
|
+
xyz = array([ p for p in m.positions()])
|
|
41
|
+
m_tri = Manifold(m)
|
|
42
|
+
triangulate(m_tri, clip_ear=False)
|
|
43
|
+
ijk = array([[ idx for idx in m_tri.circulate_face(f,'v')] for f in m_tri.faces()])
|
|
44
|
+
mesh = go.Mesh3d(x=xyz[:,0],y=xyz[:,1],z=xyz[:,2],
|
|
45
|
+
i=ijk[:,0],j=ijk[:,1],k=ijk[:,2],color='#dddddd',flatshading=not smooth)
|
|
46
|
+
if data is not None:
|
|
47
|
+
mesh['intensity'] = data
|
|
48
|
+
mesh['contour'] = {'show': True, 'color': '#ff0000'}
|
|
49
|
+
mesh_data += [mesh]
|
|
50
|
+
if wireframe:
|
|
51
|
+
pos = m.positions()
|
|
52
|
+
xyze = []
|
|
53
|
+
for h in m.halfedges():
|
|
54
|
+
if h < m.opposite_halfedge(h):
|
|
55
|
+
p0 = pos[m.incident_vertex(m.opposite_halfedge(h))]
|
|
56
|
+
p1 = pos[m.incident_vertex(h)]
|
|
57
|
+
xyze.append(array(p0))
|
|
58
|
+
xyze.append(array(p1))
|
|
59
|
+
xyze.append(array([None, None, None]))
|
|
60
|
+
xyze = array(xyze)
|
|
61
|
+
trace1=go.Scatter3d(x=xyze[:,0],y=xyze[:,1],z=xyze[:,2],
|
|
62
|
+
mode='lines',
|
|
63
|
+
line=dict(color='rgb(125,0,0)', width=1),
|
|
64
|
+
hoverinfo='none')
|
|
65
|
+
mesh_data += [trace1]
|
|
66
|
+
elif isinstance(m, Graph):
|
|
67
|
+
pos = m.positions()
|
|
68
|
+
xyze = []
|
|
69
|
+
for v in m.nodes():
|
|
70
|
+
for w in m.neighbors(v):
|
|
71
|
+
if v < w:
|
|
72
|
+
p0 = pos[v]
|
|
73
|
+
p1 = pos[w]
|
|
74
|
+
xyze.append(array(p0))
|
|
75
|
+
xyze.append(array(p1))
|
|
76
|
+
xyze.append(array([None, None, None]))
|
|
77
|
+
xyze = array(xyze)
|
|
78
|
+
trace1=go.Scatter3d(x=xyze[:,0],y=xyze[:,1],z=xyze[:,2],
|
|
79
|
+
mode='lines',
|
|
80
|
+
line=dict(color='rgb(0,0,0)', width=1),
|
|
81
|
+
hoverinfo='none')
|
|
82
|
+
mesh_data += [trace1]
|
|
83
|
+
|
|
84
|
+
|
|
85
|
+
lyt = go.Layout(width=850,height=800)
|
|
86
|
+
lyt.scene.aspectmode="data"
|
|
87
|
+
if EXPORT_MODE:
|
|
88
|
+
py.iplot(dict(data=mesh_data,layout=lyt))
|
|
89
|
+
else:
|
|
90
|
+
return go.FigureWidget(mesh_data,lyt)
|
|
91
|
+
|
pygel3d/spatial.py
ADDED
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
""" DEPRECATED!!!! This module provides a kD-tree implementation but specialized to 3D. The reason why it is deprecated is that scipy.spatial contains a very flexible KDTree class that is much more generic and obviates the need for GEL's KDTree. Going forward, the KDTree may be removed from PyGEL but not from the C++ GEL API. """
|
|
2
|
+
|
|
3
|
+
import ctypes as ct
|
|
4
|
+
from numpy.typing import ArrayLike
|
|
5
|
+
from pygel3d import lib_py_gel, Vec3dVector, IntVector
|
|
6
|
+
|
|
7
|
+
class I3DTree:
|
|
8
|
+
""" kD tree specialized for 3D keys and integer values.
|
|
9
|
+
This tree data structure is useful for storing 3D points and
|
|
10
|
+
associated integer values - typically indices. There is also
|
|
11
|
+
a more general kd tree in scipy.spatial if this one does not
|
|
12
|
+
suit your needs. """
|
|
13
|
+
def __init__(self):
|
|
14
|
+
self.obj = lib_py_gel.I3DTree_new()
|
|
15
|
+
def __del__(self):
|
|
16
|
+
lib_py_gel.I3DTree_delete(self.obj)
|
|
17
|
+
def insert(self,p: ArrayLike, v: int):
|
|
18
|
+
""" Insert v at 3D point given by p. Insert should be called before
|
|
19
|
+
calling build. """
|
|
20
|
+
lib_py_gel.I3DTree_insert(self.obj, p[0],p[1],p[2],v)
|
|
21
|
+
def build(self):
|
|
22
|
+
""" Build the tree. This function call makes the tree searchable. It is
|
|
23
|
+
assumed that all calls to insert come before calling this function."""
|
|
24
|
+
lib_py_gel.I3DTree_build(self.obj)
|
|
25
|
+
def closest_point(self, p: ArrayLike, r: float) -> tuple[list[float], int]|None:
|
|
26
|
+
""" Search for point closest to p within a max radius r.
|
|
27
|
+
This function should only be called after build. """
|
|
28
|
+
key = (ct.c_double * 3)()
|
|
29
|
+
val = ct.c_size_t()
|
|
30
|
+
n = lib_py_gel.I3DTree_closest_point(self.obj, p[0],p[1],p[2],r,ct.byref(key),ct.byref(val))
|
|
31
|
+
if n==1:
|
|
32
|
+
return ([key[0],key[1],key[2]],val.value)
|
|
33
|
+
return None
|
|
34
|
+
def in_sphere(self, p: ArrayLike, r: float) -> tuple[Vec3dVector, IntVector]:
|
|
35
|
+
""" Retrieve all points within a radius r of p.
|
|
36
|
+
This function should only be called after build. """
|
|
37
|
+
keys = Vec3dVector()
|
|
38
|
+
vals = IntVector()
|
|
39
|
+
n = lib_py_gel.I3DTree_in_sphere(self.obj, p[0],p[1],p[2],r,keys.obj,vals.obj)
|
|
40
|
+
return (keys,vals)
|
|
@@ -0,0 +1,159 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: PyGEL3D
|
|
3
|
+
Version: 0.8.0
|
|
4
|
+
Summary: PyGEL 3D (Python Bindings for GEL) contains tools for polygonal mesh based geometry processing
|
|
5
|
+
Author-email: Andreas Baerentzen <janba@dtu.dk>
|
|
6
|
+
License-Expression: MIT
|
|
7
|
+
Project-URL: Homepage, https://github.com/janba/GEL
|
|
8
|
+
Project-URL: Repository, https://github.com/janba/GEL
|
|
9
|
+
Classifier: Programming Language :: Python :: 3
|
|
10
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
11
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
12
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
13
|
+
Classifier: Programming Language :: Python :: 3.14
|
|
14
|
+
Classifier: Operating System :: Microsoft :: Windows
|
|
15
|
+
Classifier: Operating System :: MacOS
|
|
16
|
+
Classifier: Operating System :: POSIX :: Linux
|
|
17
|
+
Requires-Python: >=3.11
|
|
18
|
+
Description-Content-Type: text/markdown
|
|
19
|
+
License-File: LICENSE.md
|
|
20
|
+
Requires-Dist: numpy
|
|
21
|
+
Requires-Dist: plotly<6,>=5.24.1
|
|
22
|
+
Requires-Dist: scipy
|
|
23
|
+
Dynamic: license-file
|
|
24
|
+
|
|
25
|
+
# GEL
|
|
26
|
+
GEL is a C++ library of geometry processing tools mostly intended for computer graphics applications. Python bindings for GEL are found in the included PyGEL library which is also available from PyPI under the package name PyGEL3D.
|
|
27
|
+

|
|
28
|
+
|
|
29
|
+
GEL contains
|
|
30
|
+
- a fairly mature half-edge based polygonal mesh data structure which includes functions for traversing a mesh and a rich library of methods for modifying meshes,
|
|
31
|
+
- a graph data structure which is also specialized for spatial graphs,
|
|
32
|
+
- voxel grid data structures,
|
|
33
|
+
- spatial data structures for triangles and points: BSP tree, bounding box hierarchy, and a kD-Tree in particular,
|
|
34
|
+
- a linear algebra library for small vectors and matrices (2D, 3D, and 4D),
|
|
35
|
+
- tools for visualization based on OpenGL and tools based on Plotly for visualization in Jupyter notebooks, and
|
|
36
|
+
- various utilities.
|
|
37
|
+
|
|
38
|
+
Unique functionality includes
|
|
39
|
+
- Local Separator Skeletonization: our graph-based skeletonization method that works on both meshes, voxel data, and point clouds, although you need to specify the connectivity for the latter two.
|
|
40
|
+
- Inverse skeletonization: Face extrusion quad meshes (FEQ) from graphs.
|
|
41
|
+
- Rotation System Reconstruction: a combinatorial method for reconstruction from point clouds.
|
|
42
|
+
|
|
43
|
+
There are several less unique but important features:
|
|
44
|
+
- Garland-Heckbert simplification of triangle meshes,
|
|
45
|
+
- signed distance field (SDF) computation from triangle meshes,
|
|
46
|
+
- iso-surface polygonization for regular voxel grids: can produce both dual and primal connectivity,
|
|
47
|
+
- edge flipping-based optimization for triangle meshes,
|
|
48
|
+
- mesh smoothing: we include anisotropic smoothing, Taubin smoohing, and more.
|
|
49
|
+
- topological analysis: a single (Python) function splits a mesh into components and analyses each.
|
|
50
|
+
|
|
51
|
+
GEL requires a recent C++ compiler but has very few dependencies. For visualization, OpenGL and GLFW are required, but these dependencies can be omitted if visualization is not needed. The basic philosophy is that GEL should have few dependencies itself since it is better that projects which use GEL can choose for themselves, say, which linear algebra package to use.
|
|
52
|
+
|
|
53
|
+
### PyGEL
|
|
54
|
+
PyGEL is a set of Python bindings for a _subset_ of the features in GEL. In particular, PyGEL covers almost all the mesh features. In addition PyGEL has its own viewer based on OpenGL, and PyGEL can be used from Jupyter notebooks. In this case, it is possible to visualize meshes using a plotly widget. A significant benefit here is that when the notebook is exported to HTML, the 3D view comes along. In fact, this makes PyGEL a useful tool for teaching geometry processing since work can be carried out in a Jupyter notebook and assignments submitted as HTML files. Moreover, PyGEL works in Google [colab](https://colab.research.google.com) notebooks.
|
|
55
|
+
|
|
56
|
+
## DOCUMENTATION
|
|
57
|
+
Some installation instructions below. But for more documentation please see the doc directory. There is a doxygen script for creating a reference manual and a latex file intro.tex which explains the basics. Please doxygen or pdflatex your documentation. A license is also found in the intro document.
|
|
58
|
+
|
|
59
|
+
## INSTALLING PYGEL WITH PIP
|
|
60
|
+
|
|
61
|
+
PyGEL is on PyPI and can be installed with pip. For most potential users, there is no reason to look further than:
|
|
62
|
+
```
|
|
63
|
+
pip install PyGEL3D
|
|
64
|
+
```
|
|
65
|
+
The PyPI package is called PyGEL3D and not PyGEL. pip installs a wheel for your platform:
|
|
66
|
+
|
|
67
|
+
- Linux x86_64 and ARM64 (manylinux, glibc 2.28+: Ubuntu 20.04, Debian 10, RHEL 8, Fedora, Colab, and similar)
|
|
68
|
+
- macOS 11+ (universal2: Intel and Apple Silicon)
|
|
69
|
+
- 64-bit Windows
|
|
70
|
+
|
|
71
|
+
The compiled library links against OpenGL (`libGL`). A normal desktop already has this. A minimal Linux system (container, CI, server, Colab) usually does not, and `import pygel3d` will then fail even though pip succeeded.
|
|
72
|
+
|
|
73
|
+
On Ubuntu/Debian install the OpenGL runtime:
|
|
74
|
+
```
|
|
75
|
+
sudo apt-get install libgl1
|
|
76
|
+
```
|
|
77
|
+
`libgl1` is a virtual package. Apt will pull in whatever implementation the distribution ships — typically Mesa. That is not a request to use software rendering; your GPU driver still provides the actual OpenGL implementation.
|
|
78
|
+
|
|
79
|
+
On Google Colab, use this as the first cell:
|
|
80
|
+
```
|
|
81
|
+
!apt-get install libgl1
|
|
82
|
+
!pip install PyGEL3D
|
|
83
|
+
```
|
|
84
|
+
If there is no wheel for your platform (for example Alpine/musl), build from source as discussed below.
|
|
85
|
+
|
|
86
|
+
## BUILDING AND INSTALLING GEL AND PYGEL
|
|
87
|
+
|
|
88
|
+
If you need or wish to build GEL/PyGEL from source, please download or clone it from [https://github.com/janba/GEL](https://github.com/janba/GEL). Below you will find instructions for how to build and create a package for PyGEL that can be installed via pip. If you look around you will find some other build options for Windows, Mac and Linux. Since GEL is primarily developed on Mac OS, the Xcode projects are actively maintained and cover everything. **The two last build options are not actively maintained**. However, they may prove of some use and hence not removed.
|
|
89
|
+
|
|
90
|
+
### Building with CMake
|
|
91
|
+
If you are using a unix-like command line, build and install with
|
|
92
|
+
```
|
|
93
|
+
cmake -S . -B build
|
|
94
|
+
cmake --build build -j 8
|
|
95
|
+
cmake --install build
|
|
96
|
+
```
|
|
97
|
+
This installs the GEL library, headers, and a CMake package config into
|
|
98
|
+
`~/.local` (`~/.local/include/GEL`, `~/.local/lib`) so other projects can
|
|
99
|
+
locate GEL with `find_package(GEL)`. No sudo is required. Override the
|
|
100
|
+
location with `-DCMAKE_INSTALL_PREFIX=<prefix>` if needed.
|
|
101
|
+
|
|
102
|
+
Note that this process is automated by the `build_install.sh` script.
|
|
103
|
+
|
|
104
|
+
### Using GEL from CMake
|
|
105
|
+
After installing GEL, a consumer project only needs:
|
|
106
|
+
|
|
107
|
+
```cmake
|
|
108
|
+
find_package(GEL REQUIRED HINTS "$ENV{HOME}/.local")
|
|
109
|
+
target_link_libraries(my_app PRIVATE GEL::GEL)
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
If GEL is not in `~/.local` or another default search path, point CMake at
|
|
113
|
+
the install (or build) tree:
|
|
114
|
+
|
|
115
|
+
```
|
|
116
|
+
cmake -S . -B build -DCMAKE_PREFIX_PATH=<gel-install-prefix>
|
|
117
|
+
```
|
|
118
|
+
### Creating a PyGEL3D package and installing it
|
|
119
|
+
From a source checkout, build a **platform** wheel (it compiles `libPyGEL` with CMake and tags the wheel for this OS/architecture):
|
|
120
|
+
```
|
|
121
|
+
python -m build --wheel
|
|
122
|
+
pip install dist/pygel3d-*.whl
|
|
123
|
+
```
|
|
124
|
+
You need CMake ≥ 3.25, a C++20 compiler, and the Python packages `build` and `setuptools`. Isolated builds also pull in the `cmake` and `ninja` packages automatically.
|
|
125
|
+
|
|
126
|
+
Alternatively,
|
|
127
|
+
```
|
|
128
|
+
pip install .
|
|
129
|
+
```
|
|
130
|
+
or the one-stop script
|
|
131
|
+
```
|
|
132
|
+
sh build_install.sh
|
|
133
|
+
```
|
|
134
|
+
builds GEL, installs the C++ library to `~/.local`, and pip-installs a local PyGEL3D wheel (replacing any previous install).
|
|
135
|
+
|
|
136
|
+
PyPI releases are produced by GitHub Actions (`.github/workflows/wheels.yml`). Pushing a tag `v*` builds manylinux, macOS, and Windows wheels plus an sdist and publishes them. There is no local step of downloading binaries from CI.
|
|
137
|
+
|
|
138
|
+
## Compilation of Demos and Tests
|
|
139
|
+
|
|
140
|
+
GEL comes with some test scripts and also demos. You can find these in `GEL/src/test` and `GEL/src/demo`. Tests are optional and built with the main project when `BUILD_TESTING` is on.
|
|
141
|
+
|
|
142
|
+
The philosophy behind the demos is that they require GEL and PyGEL3D (for the Python demos) have been installed and do not try to find header files, binaries, or Python packages in the GEL source tree.
|
|
143
|
+
|
|
144
|
+
In fact, the C++ demos are standalone CMake projects. They call `find_package(GEL)` and therefore expect an installed GEL package rather than a library sitting in the source tree. After a standard install to `~/.local`:
|
|
145
|
+
|
|
146
|
+
```
|
|
147
|
+
cmake -S src/demo/MeshDistance -B src/demo/MeshDistance/build
|
|
148
|
+
cmake --build src/demo/MeshDistance/build
|
|
149
|
+
```
|
|
150
|
+
|
|
151
|
+
All C++ demos can also be configured together from `src/demo` and there is a script `run_demos.py` that runs all of them. Since many are interactive, you will frequently need to hit escape or quit a program if you run this script.
|
|
152
|
+
|
|
153
|
+
|
|
154
|
+
## Practical Issues
|
|
155
|
+
Compiling both GEL and PyGEL requires that you have OpenGL installed unless you choose not to compile graphics support which you can do by setting `Use_GLGraphics` to `OFF` in the CMake file. GLFW is also needed, but CMake fetches GLFW from github and compiles it along with the GEL code. If you compile in some of the other ways (e.g. using XCode, Visual Studio) there is no simple way to avoid the dependency on graphics libraries. Thus, if you need to avoid the OpenGL requirements, CMake is the way to go.
|
|
156
|
+
|
|
157
|
+
GEL comes with a few demo applications. In addition to the requirements above, several of these also require GLUT to be installed. Going forward, we should remove the GLUT dependency and move to GLFW for the applications.
|
|
158
|
+
|
|
159
|
+
PyGEL has a module called `jupyter_display` which produces graphics suitable for Jupyter notebooks. This module is based on `plotly` which must then be installed for it to work. You will also need `numpy`. However, if you use `pip`, these required libraries will be downloaded automatically when you install PyGEL.
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
pygel3d/PyGEL.dll,sha256=jf-DpGxkuLOkaaRmzhYG90Z1j6KlKzK7z3H22hdLt1k,1549312
|
|
2
|
+
pygel3d/__init__.py,sha256=cBpKf2rLu7rmAKzO7jh-U2egpZAKlJn2YmtCKn2GFkc,21978
|
|
3
|
+
pygel3d/gl_display.py,sha256=pyysHcBZnDqrk9blJ_exiqdVV7XJtOA01a8IAnIqI6g,7186
|
|
4
|
+
pygel3d/graph.py,sha256=pkab-kSVx5FEGjm3A-B25sQNwyYFTJIonKLY4TktZtA,15966
|
|
5
|
+
pygel3d/hmesh.py,sha256=Mmz5rqPmL5G8aYF6nmVoAA8Q8jWSu_7spmhDTLuzGq8,57082
|
|
6
|
+
pygel3d/jupyter_display.py,sha256=F7O4tmbVm22VvXdTP-MSqJ7wJ4CuDsTtp9M3juQz6nU,4175
|
|
7
|
+
pygel3d/spatial.py,sha256=Io1bQ-VH6iCMQQ9QENvx1YOkzwieapvWuYoG4tNUayU,2179
|
|
8
|
+
pygel3d/experimental/__init__.py,sha256=UmdwRLH-0hGQoTeMZJphtVuZ-lyaB_mnuQndjIDWYzM,19
|
|
9
|
+
pygel3d/experimental/hmesh.py,sha256=_wlj1uBY4TUbchvMxQolLQc-l1MVA-EW-4jAU6rkaYA,1755
|
|
10
|
+
pygel3d-0.8.0.dist-info/licenses/LICENSE.md,sha256=wcDXR6yYNWAp8M7EDKTxPgLYuWkNxh2VpjyNfOiX_k4,1388
|
|
11
|
+
pygel3d-0.8.0.dist-info/METADATA,sha256=I2Wf9DPokCCmOyuYXyHV618Hw4x6EcY3UkKMdE0MZ_Q,9874
|
|
12
|
+
pygel3d-0.8.0.dist-info/WHEEL,sha256=Zx98gwb_dQKckJK3HEOVKnxxD52EfU_PXDG_usMJ2ng,98
|
|
13
|
+
pygel3d-0.8.0.dist-info/top_level.txt,sha256=XYT44w7XBWjKeQ6N329yLcEd-Y8TmcBDTnTx43-yPJk,8
|
|
14
|
+
pygel3d-0.8.0.dist-info/RECORD,,
|
|
@@ -0,0 +1,27 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2025 Andreas Bærentzen
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
**Acknowledgment**: Contributions to this project are documented in the CONTRIBUTORS.md file.
|
|
16
|
+
|
|
17
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
18
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
19
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
20
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
21
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
22
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
23
|
+
SOFTWARE.
|
|
24
|
+
|
|
25
|
+
---
|
|
26
|
+
|
|
27
|
+
**Note**: This project was previously licensed under a different license that was functionally equivalent to the MIT License. The change to the MIT License was made on February 23, 2025.
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
pygel3d
|