kdu_analysis( kdu_resolution resolution, kdu_sample_allocator * allocator, bool use_shorts, float normalization=1.0F, kdu_roi_node * roi=NULL)
Java: Kdu_analysis( Kdu_resolution resolution, Kdu_sample_allocator allocator, boolean use_shorts, float normalization, Kdu_roi_node roi)
[Declared in "../coresys/common/kdu_sample_processing.h"]
Constructing an instance of this class for the highest visible resolution level of a tile-component, will cause the constructor to recursively create instances of the class for each successive DWT stage and also for the block encoding process.
Interface to the resolution level for which the analysis object is being created. The analysis stage decomposes the image at that resolution into LL, LH, HL and HH subbands, where LH, HL and HH subbands are the resolution object's member subbands, as identified by resolution.access_subband and the LL subband corresponds to the next lower resolution level, if one exists, as returned by resolution.access_next
A kdu_sample_allocator object whose finalize member function has not yet been called must be supplied for pre-allocation of the various sample buffering arrays. This same allocator will be shared by the entire DWT tree and by the kdu_encoder objects at its leaves.
Indicates whether 16-bit or 32-bit data representations are to be used. The same type of representation must be used throughput the DWT processing chain and line buffers pushed into the DWT engine must use this representation.
Ignored for reversibly transformed data. In the irreversible case, it indicates that the nominal range of data pushed into the kdu_push_ifc::push function will be from -0.5*R to 0.5*R, where R is the value of the normalization argument. This capability is provided primarily to allow normalization steps to be skipped or approximated with simple powers of 2 during lifting implementations of the DWT; the factors can be folded into quantization step sizes. The best way to use the normalization argument will generally depend upon the implementation of the DWT.
If non-NULL, this argument points to an appropriately derived ROI node object, which may be used to recover region of interest mask information for the present tile-component. In this case, the present function will automatically construct an ROI processing tree to provide access to derived ROI information in each individual subband. The roi::release function will be called when the present object is destroyed — possibly sooner (if it can be determined that ROI information is no longer required).