Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
ALF
ALF
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 71
    • Issues 71
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 13
    • Merge Requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ALF
  • ALFALF
  • Issues
  • #174

Closed
Open
Created Nov 30, 2020 by Florian Goth@fgothOwner0 of 5 tasks completed0/5 tasks

More Use cases for the ContainerElementBase Object Hierarchy

Now with the ContainerElementBase Object Hierarchy in place and a dynamic container present that is able to take up these objects in some "dynamic" way we can think about extensions.

Approximate techniques

  • Minimum Split Checkerboard + Higher Order Checkerboard #175
  • Lanczos

Exact techniques

  • Block techniques #176
  • FFT techniques

Use cases in other places

  • Op_V is not that much different. Get rid of the various types?
Edited Dec 03, 2020 by Florian Goth
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None