Accélération des algorithmes DSP

Accélération avec le multithreading Dataflow ou les fonctions MEX générées

Il est possible d’améliorer le débit de simulation des fonctions MATLAB^® en utilisant la fonction dspunfold pour générer un fichier MEX multithread.

Dans Simulink^®, les domaines Dataflow partitionnent automatiquement votre modèle et simulent le système en utilisant plusieurs threads. En ajoutant une latence algorithmique à votre système, vous pouvez accroître la simultanéité et améliorer le débit de simulation de votre modèle.

Fonctions

`dspunfold`	Generates a multi-threaded MEX file from a MATLAB function
`codegen`	Generate C/C++ code from MATLAB code

Blocs

Dataflow Subsystem

Subsystem whose execution domain is set to Dataflow

Rubriques

Dépliage

Workflow for Generating a Multithreaded MEX File using dspunfold
This section discusses the recommended workflow of generating the multithreaded MEX and verifying the results using the analyzer.
Multithreaded MEX File Generation
This example shows how to use the dspunfold function to generate a multithreaded MEX file from a MATLAB® function using unfolding technology.
Signal Processing Algorithm Acceleration in MATLAB
Accelerate signal processing algorithm with codegen and dspunfold.
How Is dspunfold Different from parfor?
This page should detail the users on when to use dspunfold and when to use parfor.

Dataflow

Dataflow Domain
Simulate a system using synchronous dataflow.
Multicore Simulation and Code Generation of Dataflow Domains
Types of parallelism. Simulation and code generation of dataflow domains using multiple threads.
Model Multirate Signal Processing Systems Using Dataflow
Use a Dataflow Subsystem to automatically calculate frame sizes in multirate systems.
Perform Multicore Analysis for Dataflow
When a system is configured to use a dataflow execution domain, the Multicore tab is activated on the Simulink toolstrip.

Résolution des problèmes

Why Does the Analyzer Choose the Wrong State Length?

This section discusses the example where the state length depends on the input which causes verification failure. Debugging steps are also included.

Why Does the Analyzer Choose a Zero State Length?

This section discusses the example where the input does not have an immediate effect on the output. Hence, state length of 0 is considered in spite of the algorithm containing states.