JuliaGeometry / JuliaGeometry/RegionTrees.jl

Allow heterogenous cell data types?

Open
#9 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Julia
Stars
114
Forks
22
PR merge metrics
No merged PRs in 30d

Description

I've been implementing my own version of Dual Contouring (http://faculty.cs.tamu.edu/schaefer/research/dualcontour.pdf) and I noticed that if all the cell data types returned by refine_data are not identical, then split! fails because the child data gets returned as Tuple{Tuple{...}} instead of just Tuple{...}. Having this ability could be useful to leverage multiple dispatch on the cell data, as well as making the package easier to experiment with. Is there a reason the types need to be identical, or might this even be a bug?

Contributor guide

No contributing guide indexed for this repository

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 reading the split! implementation and the refine_data entry point, then reproduce the failure with cell data of different types. Determine whether heterogeneous child data can be supported without breaking existing behavior; done means split! handles the requested return shape and has coverage for mixed cell data types.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.