A.I.M.S algorithms


front.h File Reference
Include dependency graph for front.h:
This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Classes

class  AimsData< T >
 
class  aims::BucketMap< T >
 

Namespaces

 aims
 

Functions

template<typename T >
void AimsDistanceFrontPropagation (AimsData< T > &vol, T val_domain, T val_outside, int xm, int ym, int zm, float mult_factor, bool divide)
 
template<typename T >
void AimsDistanceFrontPropagation (aims::BucketMap< T > &vol, T val_domain, T val_outside, int xm, int ym, int zm, float mult_factor, bool divide)
 Chamfer front propagation distance map on a bucket. More...
 

Function Documentation

template<typename T >
void AimsDistanceFrontPropagation ( AimsData< T > &  vol,
val_domain,
val_outside,
int  xm,
int  ym,
int  zm,
float  mult_factor,
bool  divide 
)
template<typename T >
void AimsDistanceFrontPropagation ( aims::BucketMap< T > &  vol,
val_domain,
val_outside,
int  xm,
int  ym,
int  zm,
float  mult_factor,
bool  divide 
)

Chamfer front propagation distance map on a bucket.

Parameters
volboth input and output
val_domainvalue where the distance can propagate in the input bucket
val_outsidevoxels of this value are ignored, the front cannot propagate on this value. In buckets it is generally unused, so provide an unused value (negative for instance). Input voxels of other values are considered fixed at their given distance. Use at least one voxel with a given distance (0 typically) to start the propagation.
xmsize of the kernel on x (in voxels)
ymsize of the kernel on y (in voxels)
zmsize of the kernel on z (in voxels)
mult_factorall distances are internally multiplied by this factor to overcome precision issues (typically when using int values)
dividetells whether the multiplied distances should be re-divided to millimeters values at the end of the operation