This release is a pre-release and may not be stable for production use.
OpenGeode-Inspectorby Geode-solutions
OpenGeode module for inspecting meshes and models
Introduction
OpenGeode-Inspector is a module of OpenGeode providing ways of inspecting your meshes and models and verifying their validity.
Documentation
Go check out the online documentation at [docs.geode-solutions.com].
[docs.geode-solutions.com] https://docs.geode-solutions.com
Installing OpenGeode-Inspector is done:
- either by compiling the C++ source.
- or by installing the python library using the pip command
pip install opengeode-inspector.
Usage
To use OpenGeode-Inspector, several options are available:
- If you installed and compiled the C++ source code, you can use the executable binaries to apply an inspection of your meshes/models and toggle on/off the various checks directly.
- or use the API functions (check the tests to see how it is done) if you want to go further or use the resulting errors to repair your meshes/models.
- If you installed the python library, you can add
import opengeode_inspectorin your Python script to use the available API functions. Check this documentation page for more details. Examples are also procured in theexamplesfolder.
The available checks for each mesh type are:
- PointSet:
- Colocation of vertices
- EdgedCurve:
- Colocation of vertices
- Degeneration of edges
- SurfaceMesh:
- Adjacency of polygons
- Colocation of vertices
- Degeneration of edges
- Degeneration of polygons
- Intersection of triangles (for triangulated surfaces)
- Manifold of vertices
- Manifold of edges
- SolidMesh:
- Adjacency of polyhedra
- Colocation of vertices
- Degeneration of edges
- Degeneration of polyhedra
- Manifold of vertices
- Manifold of edges
- Manifold of facets The available checks for each model type are:
- Section:
- Validity of the topology
- Checks on each component mesh: all the previous mesh checks depending on the component mesh type
- Checks on the validity of the unique vertices (linking to vertices, colocation of unique vertices points, un-colocation of points with same unique vertices)
- Intersection of the component mesh surfaces between each other
- BRep:
- Validity of the topology
- Checks on each component mesh: all the previous mesh checks depending on the component mesh type
- Checks on the validity of the unique vertices (linking to vertices, colocation of unique vertices points, un-colocation of points with same unique vertices)
- Intersection of the component mesh surfaces between each other
Questions
For questions and support please use the official slack and go to the channel #inspector. The issue list of this repo is exclusively for bug reports and feature requests.
License
Copyright (c) 2019 - 2026, Geode-solutions
1 maintainer
Metadata
1 maintainer
Release files for OpenGeode-Inspector 6.14.0rc1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opengeode_inspector-6.14.0rc1-cp314-cp314-manylinux_2_28_x86_64.whl | CPython 3.14 | CPython 3.14 | Linux glibc 2.28+ x86-64 | Details |
Release files / opengeode_inspector-6.14.0rc1-cp314-cp314-manylinux_2_28_x86_64.whl
| Download URL | opengeode_inspector-6.14.0rc1-cp314-cp314-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 996.8 kB |
| Tags | CPython 3.14 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
197ec2103f612414d553db4b4645f5e274131e9a4e315fd1495ca89c9339132e
|
|
BLAKE2b-256 checksum How to use checksums |
4ac3b6d1fe951267953fe038b4adf496d154ae5581b519128e7b29c149979217
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for OpenGeode-Inspector 6.14.0rc1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
