Changes between Version 4 and Version 5 of GSoC/2014/ImplementationOf3DRasterFlowLine


Ignore:
Timestamp:
Jun 13, 2014, 7:46:00 PM (10 years ago)
Author:
annakrat
Comment:

week 4

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2014/ImplementationOf3DRasterFlowLine

    v4 v5  
    9999
    100100Also I will look at implementation of Runge Kutta method with adaptive step size  which might help with the flowlines near a singular point.
     101
     102=== Week 4 ===
     103I implemented flow accumulation (number of flowlines traversing through voxel) in a naive way where I count that a flowline transects a voxel only when there is at least one point of the flowline in the voxel (cell). This doesn't work very well unless the integration step is very small. So I started to implement a voxel traversal algorithm which should say precisely which voxels are traversed (based on this [http://www.cse.yorku.ca/~amana/research/grid.pdf article]). I have it working now although I am not sure how to reliably test it. I will incorporate it in the flow accumulation computation.
     104
     105[[Image(flowacc_simple.png, 250px)]]
     106
     107Currently the module supports different combinations of input and output. Input can be vector map of points from which the flowlines are generated, or when not providing this vector, the flowlines are generated from centers of voxels taking into account skip parameter to reduce the number of flowlines. Output can be flowaccumulation or flowlines or both. Computation of flowaccumulation takes more time since the flowlines have to be generated from each voxel (although they are not stored in the output vector map if not specified).