Skip to content

deserialize_fft_optimization_dataDeserializeFftOptimizationDataDeserializeFftOptimizationDatadeserialize_fft_optimization_dataT_deserialize_fft_optimization_data🔗

Short description🔗

deserialize_fft_optimization_dataDeserializeFftOptimizationDataDeserializeFftOptimizationDatadeserialize_fft_optimization_dataT_deserialize_fft_optimization_data — Deserialize FFT speed optimization data.

Signature🔗

deserialize_fft_optimization_data( serialized_item SerializedItemHandle )void DeserializeFftOptimizationData( const HTuple& SerializedItemHandle )static void HOperatorSet.DeserializeFftOptimizationData( HTuple serializedItemHandle )def deserialize_fft_optimization_data( serialized_item_handle: HHandle ) -> None

Herror T_deserialize_fft_optimization_data( const Htuple SerializedItemHandle )

static void HMisc::DeserializeFftOptimizationData( const HSerializedItem& SerializedItemHandle )

static void HMisc.DeserializeFftOptimizationData( HSerializedItem serializedItemHandle )

Description🔗

deserialize_fft_optimization_dataDeserializeFftOptimizationData deserializes data, that was serialized by serialize_fft_optimization_dataSerializeFftOptimizationData, for optimizing the runtime of the FFT (see fwrite_serialized_itemFwriteSerializedItem for an introduction of the basic principle of serialization). The serialized data is defined by the handle SerializedItemHandleserializedItemHandleserialized_item_handle. The optimization data must have been determined previously with optimize_fft_speedOptimizeFftSpeed and must have been serialized with serialize_fft_optimization_dataSerializeFftOptimizationData. If the serialized data has been determined for the image sizes to be used in the application, calling optimize_fft_speedOptimizeFftSpeed is unnecessary. Note that the data should only be used on the same machine on which they were determined with optimize_fft_speedOptimizeFftSpeed. Otherwise, the runtimes will not be optimal. Also note that optimization data that were created with Standard HALCON cannot be used with Parallel HALCON and vice versa.

deserialize_fft_optimization_dataDeserializeFftOptimizationData 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🔗

SerializedItemHandleserializedItemHandleserialized_item_handle (input_control) serialized_item → (handle)HTuple (HHandle)HSerializedItem, HTuple (IntPtr)HHandleHtuple (handle)

Handle of the serialized item.

Result🔗

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

Combinations with other operators🔗

Combinations

Possible predecessors

fread_serialized_itemFreadSerializedItem, receive_serialized_itemReceiveSerializedItem, serialize_fft_optimization_dataSerializeFftOptimizationData

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

serialize_fft_optimization_dataSerializeFftOptimizationData

Module🔗

Foundation