Skip to content

read_fft_optimization_dataReadFftOptimizationDataReadFftOptimizationDataread_fft_optimization_dataread_fft_optimization_data🔗

Short description🔗

read_fft_optimization_dataReadFftOptimizationDataReadFftOptimizationDataread_fft_optimization_dataread_fft_optimization_data — Load FFT speed optimization data from a file.

Signature🔗

read_fft_optimization_data( filename.read FileName )void ReadFftOptimizationData( const HTuple& FileName )static void HOperatorSet.ReadFftOptimizationData( HTuple fileName )def read_fft_optimization_data( file_name: str ) -> None

Herror read_fft_optimization_data( const char* FileName )

Herror T_read_fft_optimization_data( const Htuple FileName )

static void HMisc::ReadFftOptimizationData( const HString& FileName )

static void HMisc::ReadFftOptimizationData( const char* FileName )

static void HMisc::ReadFftOptimizationData( const wchar_t* FileName ) (Windows only)

static void HMisc.ReadFftOptimizationData( string fileName )

Description🔗

read_fft_optimization_dataReadFftOptimizationData loads data for optimizing the runtime of the FFT from the file given by FileNamefileNamefile_name. The optimization data must have been determined previously with optimize_fft_speedOptimizeFftSpeed and must have been stored with write_fft_optimization_dataWriteFftOptimizationData. If the stored data have been determined for the image sizes to be used in the application, a call to optimize_fft_speedOptimizeFftSpeed is unnecessary. It should be noted that the data should only be used on the same machine on which they were determined with optimize_fft_speedOptimizeFftSpeed. If this is not observed the runtimes will not be optimal. Furthermore, it should be noted that optimization data that were created with Standard HALCON cannot be used with Parallel HALCON and vice versa.

read_fft_optimization_dataReadFftOptimizationData influences the runtime of the following operators, which use the FFT: fft_genericFftGeneric, fft_imageFftImage, fft_image_invFftImageInv, sfs_pentlandSfsPentland, sfs_mod_lrSfsModLr, sfs_orig_lrSfsOrigLrwiener_filterWienerFilter.

Execution information🔗

Execution information
  • Multithreading type: reentrant (runs in parallel with non-exclusive operators).

  • Multithreading scope: global (may be called from any thread).

  • Processed without parallelization.

Parameters🔗

FileNamefileNamefile_name (input_control) filename.read → (string)HTuple (HString)HTuple (string)strHtuple (char*)

File name of the optimization data.

Default: 'fft_opt.dat'"fft_opt.dat"

Result🔗

read_fft_optimization_dataReadFftOptimizationData returns 2 (H_MSG_TRUE) if all parameters are correct. If necessary, an exception is raised.

Combinations with other operators🔗

Combinations

Possible successors

fft_genericFftGeneric, fft_imageFftImage, fft_image_invFftImageInv, rft_genericRftGeneric, wiener_filterWienerFilter, wiener_filter_niWienerFilterNi, photometric_stereoPhotometricStereo, sfs_pentlandSfsPentland, sfs_mod_lrSfsModLr, sfs_orig_lrSfsOrigLr

Alternatives

optimize_fft_speedOptimizeFftSpeed, optimize_rft_speedOptimizeRftSpeed

See also

write_fft_optimization_dataWriteFftOptimizationData

Module🔗

Foundation