You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Matt Juntunen (Jira)" <ji...@apache.org> on 2020/01/03 16:43:00 UTC

[jira] [Updated] (GEOMETRY-34) SubHyperplane Optimized Implementations

     [ https://issues.apache.org/jira/browse/GEOMETRY-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Juntunen updated GEOMETRY-34:
----------------------------------
    Fix Version/s: 1.0

> SubHyperplane Optimized Implementations
> ---------------------------------------
>
>                 Key: GEOMETRY-34
>                 URL: https://issues.apache.org/jira/browse/GEOMETRY-34
>             Project: Apache Commons Geometry
>          Issue Type: Improvement
>            Reporter: Matt Juntunen
>            Priority: Major
>             Fix For: 1.0
>
>
> There are currently only generic implementations of the {{SubHyperplane}} interface for each dimension. These implementations use the {{(n-1)}} dimension {{Region}} class in order to implement the {{SubHyperplane}} methods. This means that each operation on a {{SubHyperplane}} of dimension {{n}} involves operations on {{Region}} instances of each {{k<n}} dimension. This is incredibly inefficient. In many situations, most of the methods of the {{SubHyperplane}} interface can be implemented directly in the {{n}} dimension. Optimized subclasses should be created for each of these situations.
>  * 2D
>  ** {{SubLine}} (generic implementation)
>  ** {{LineSegment}} (convex region)
>  * 3D
>  ** {{SubPlane}} (generic implementation)
>  ** {{ConvexSubPlane}} (convex region)
>  ** {{Triangle3D}} (convex region with 3 points)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)