llnl / llnl/axom

Additional geometry primitives

Open
#1,702 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

App Integration Klee Primal
Dominant language
C++
Stars
196
Forks
34
Avg merge
4d 1h
Merged PRs (30d)
11

Description

For shaping, where should additional primitives go? I feel like the most general should go in Primal, but perhaps there is a better place for the more specialized ones, and perhaps stuff like "Generalized Cylinder" belongs in Klee rather than Primal.

Current Primal geometry primitives include
- Cone
- Sphere
- Tetrahedron
- Plane (half-space)
- Hexahedron

These map pretty well to the shaping primitives used by a code that could adopt Axom Klee for shaping. But that code has additional primitives, some easy, some fairly baroque:
- Cylinder
- Ellipsoid
- Elliptic Paraboloid
- Helix (defined by axis, tube radius, coil radius, coil pitch)
- Torus

There are a few more, fairly powerful operators in common use:
- Multi-faced Grain (intersection of half-spaces)
- Generic (a level set: "paint where the (lazy) N-D table evaluates < 0")
- Volume of revolution, defined by
- axis AB
- polyline AB that revolves around the axis
- Generalized Cylinder
- a plane with embedded closed polyline (the base)
- an axis of extrusion, not necessarily normal to the base
- Generalized Cone
- a plane with embedded closed polyline (the base)
- an apex

Where should these go (if at all)?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing geometry primitives in Primal and how Klee uses shaping primitives. Compare the listed cylinders, ellipsoids, operators, and generalized shapes, then document which belong in Primal, which belong in Klee, and which should not be added.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.