geode-solutions/opengeode

Open source framework for representing and manipulating geometric models

OpenGeode^{by Geode-solutions}

Open source framework for representing and manipulating geometric models

---

Introduction

OpenGeode is an open source framework for representing and manipulating geometric models, from simple meshes to complex boundary representations. The framework is easy to use thanks to its readable API and its Python bindings for quick prototyping. It is the industrialization of a 5-year research prototype platform RINGMesh.

Ecosystem

Project	Version	Description
OpenGeode-IO		Implementation of input and output formats
OpenGeode-Geosciences		Custom objects and algorithms tailored for Geosciences
OpenGeode-GeosciencesIO		Implementation of input and output formats for Geosciences
OpenGeode-ModuleTemplate		Template for creating your own OpenGeode modules
OpenGeode-Inspector		Inspecting meshes and models
Geode		Open-source software for visualization, modeling and much more

Documentation

Code and API are fully documented inside the code itself. To check out our live documentation, visit docs.geode-solutions.com.

Installing OpenGeode is done:

• either, by compiling the C++ source. Check this documentation page for more details.
• or, by using pip command pip install OpenGeode-core and add import opengeode in your Python script. Check this documentation page for more details.

Questions

For questions and support please use the official slack. The issue list of this repo is exclusively for bug reports and feature requests.

Changelog

Detailed changes for each release are documented in the release notes.

License

MIT

Copyright (c) 2019 - 2024, Geode-solutions

opengeode's Issues

New class Identifier

Add an Identifer class holding at least a name and a uuid.
This class could be a new mixin used in a lot of places.

Migrate basic_objects to its folder & move Position/Side

Factory input should return read object

Change interger types

https://en.cppreference.com/w/cpp/types/integer

new_normal needs to be handle correctly

New model mixin for random/physical group of Component

Add AttributeManager on model components?

@mparquer suggested to add attributes directly on the Components.

One way to add this feature could be to add an AttributeManager on the Graph storing the topology.

Return Mesh/Model when loading them

Return loaded mesh or model instead of tkaing them by reference.

Unified Relationships edge meaning

Relationships edges have two types: hard coded relation type or generic type.

Read/Write attributes

The objective is to removed the non-const reference access in Attribute methods

Library geometry

Migrate RegularGrid into Mesh hierarchy

Review naming between embedded and embedding

OrientedVertexCycle

Create OrientedVertexCycle and use it in queries like polyhedron_facet_from_vertices

Remove SolidMesh (and others ) static methods XX::type_name_static()

Improve mesh inheritance diagram

Separate generic interface for Solid and Surface from type of mesh interface (Polyhedral, Triangulated, ...)

Homogeneize relationship method names for embeddings / embedded_surfaces

Adding a generic_string() function to GenericAtributeBase

In order to be able to have a string output whatever the type of the attribute, such as it is currently possible to get a float whatever the type of the attribute.

EOL Python 3.6

EOL is 12/2021, so remove its support for v10

Remove deprecated Index, Indices and cell_size(dimension) for RegularGrids

BRep and Section loading

Remove isolated vertices

Add a function to remove vertices that are used in any elements

wrong corner index.

OpenGeode/include/geode/model/helpers/simplicial_section_creator.h

Line 52 in a48a6e2

std::vector< uuid > create_lines( absl::Span< const uuid > corners,

This function assumes that all corners are given first in the std::vector.

Rename aabb_triangulated_surface_helpers.h

This file uses SurfaceMesh and not just TriangulatedSurface

Move some impl files in private

Ex: mesh/code/detail/xxx.h

global_epsilon value

What value should we assign to global_epsilon?

Allow several types of internal/embedding

Using ComponentID instead of uuid in Relationships

• New CollectionRanges using ComponentID
• Update tests on CollectionRanges and ItemRanges (number of relations, ...)
• Update warning message "Relation already exists" using component type

absl::nullopt instead of geode::NO_ID

Remove as much as possible the use of NO_ID in OpenGeode interface (an maybe implémentation), for example in meshes and attributes

Compute or update new attribute value

When editing an attribute, newly added values could be initialized with smart values according the context (copy old one, inrerpolate,...)

Rename Tetra into Tetrahedron

EOL Github VS2017

RegularGrids should not have cell_size smaller than epsilon

Enable backward compatibility

Improve Surface and Solid cloning

• Copy of Surface edge attributes is missing
• Copy of Solid edge attributes is missing
• Copy of Solid facet attributes is missing
• Solid edges are ordered during cloning of TetrahedralSolid
• Check order of Solid facet during cloning of TetrahedralSolid
• Check order of Surface edge during cloning of TrigulatedSurface

Rename Mesh::isolated_XXX => is_isolated_XXX

Factory output should take object in write method

Grid indices to unsigned long int

Should we change the grid indices type from index_t (unsigned int) to unsigned long int (16bits to 32 bits)

Move facet and edge usage in interface classes

Today, Surface and Solid implementation classes should manage operations (add, remove, etc.) of facets and edges. This should be moved up into interface classes. As an example, do_create_edges should be final in TetrahedralSolidBuilder and PolyhedralSolidBuilder

EOL Centos

Modify Grid Index accessors

GridCellIndex -> GridCellIndices
GridVertexIndex -> GridVertexIndices
GridCellIndices -> GridCellsAroundVertex

differentiate index (index_t) and indices (Grid*Indices) in the methods

Clean the methods which do cell_index(index) or cell_indices(index), to clarify which method is preferred in terms of input and computation speed.

Make Edges and Facets optional

Move Edges and Facets storage/impl in optional mixins

Refactor aabb files

Refactor includes, implementation position, ...

Delete vertices => delete elements whithout notice

Complete Surface and Solid API using edge/facet indices

Allow setting/modification of basic objects vertices

Today you cannot modify a Segment, Triangle, Tetra after its creation.

mapping_after_deletion should return a FixedArray

Save and load of edge/facet attributes

Rename BRep::items()

For derived classes (e.g. Structural Model), we should avoid overloading methods such as items()

Change signature of relationships methods

The objective is to clearly make appear the type of relationships (boundary, internal, ...)

Review FixedArray usage

Check when to use it or stick to avector