Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Create class for intrinsic triangulation without correspondence?

Abierto
#180 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
cpp

Línea de trabajo

No files or tests are named. Start by comparing EdgeLengthGeometry, the existing flip(Edge) logic in the GC implementation, and the mutation manager; determine whether edge-flip queries, direct mutation, or edge-based mutators best support intrinsic triangulations without correspondence data. Done means providing a decided, maintainable API for flipping or evaluating edges.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

design-decision enhancement

There are situations where one wants to work with intrinsic triangulations that do not correspond to an extrinsic mesh, and hence where no correspondence data structure is needed.

Currently, one option is to use an EdgeLengthGeometry, but (if I understand correctly) this class does not support flipping. So, one possibility is to add edge flip methods to this class, though this would break with parallel structure of other geometry classes (e.g., VertexPositionGeometry also does not support edge flips). Alternatively, we could add methods to this class that allow one to query (i) whether an edge is flippable, and (ii) the flipped edge length, without actually performing the flip.

Another option, which I currently adopt, is to re-implement flip(Edge) locally in my project, i.e., a method that mutates the surface mesh associated with an EdgeLengthGeometry, using this geometry to do convexity checks, etc. The drawback here is that I duplicate a bunch of code (diamond layout, convexity checks, flipping logic) locally in my project by copy-pasting it from within the GC implementation.

A third option would be to extend the mutation manager to support mutations of edge-based quantities, and provide some mutators suitable for intrinsic triangulation options.

@MarkGillespie has talked through this with me a bit, but may have additional thoughts…

Lenguaje dominante
C++
Estrellas
1.3k
Forks
183
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nmwsharp/geometry-central

Todos los issues de nmwsharp/geometry-central

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.