Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • hypertiling hypertiling
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 32
    • Issues 32
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • hypertilinghypertiling
  • hypertilinghypertiling
  • Issues
  • #49
Closed
Open
Issue created Jun 20, 2022 by Felix Dusel@fduselMaintainer

Possibly wrong tiling for (5, 4, 3) in kernelmanu and kernelflo?

For the (5, 4, 3) lattice, 'our' kernels produce the following lattice with 46 polygons: lattice In my opinion there are five polygons missing in the third layer at roughly 12, 2, 4, 7, and 9 o'clock (if the disk was a watch). The following image is what I would expect to be the right tiling (produced by a revised version of kerneldunham): latticeright I noticed this when checking the logs of the tests that my revised version of kerneldunham failed to pass. kernelflo and kernelmanu are the reference in those tests.

Assignee
Assign to
Time tracking