Opened 14 years ago

Closed 14 years ago

#310 closed enhancement (fixed)

have multiple resolution versions of quadtree stored at one time

Reported by: chrfi Owned by: chrfi
Priority: alpha 5 Milestone:
Component: LAG Keywords: resolution
Cc: Other processors:


basically the quad tree will contain buckets containing different resolutions. the quadtree will still be built at full resolution (or whatever resolution is specified in the constructor. the user will be able to request buckets from subset that contain a lower resolutions. This will mitigate the fact that as buckets are chached as a whole the entire bucket must be cached to access only a single or few points.

Change History (5)

comment:1 Changed 14 years ago by chrfi

the solution i plan to use is rather than having different point buckets each point bucket will contain multiple serlizedinnerbuckets each at a different resolution. a new attribute will be added to keep track of which resolution the pointbucket should behave as. the meta data returned from the point bucket will be changed based on which serilizedinnerbucket it is providing access to.

comment:2 Changed 14 years ago by chrfi

  • Status changed from new to assigned

comment:3 Changed 14 years ago by chrfi

  • Status changed from assigned to accepted

comment:4 Changed 14 years ago by chrfi

upon further investigation i can find no way to implement the above plan that doesn't require heavy rewrites of the cache minder class along with others.

comment:5 Changed 14 years ago by chrfi

  • Resolution set to fixed
  • Status changed from accepted to closed

joy, a way was found, in part due to the prior removal of the serilizedinnerbucket and moving from using boost to serialize to manually reading and writing data.

Note: See TracTickets for help on using tickets.