| Contents | Index |
| ID: Title | cgsl_0102: Evenly spaced breakpoints in lookup tables | ||
|---|---|---|---|
| Description | When you use Lookup Table and Prelookup blocks, | ||
| A | With non-fixed-point data types, use evenly spaced data breakpoints for the input axis | ||
| B | With fixed-point data types, use power of two spaced breakpoints for the input axis | ||
| Notes | Evenly-spaced breakpoints can prevent generated code from including division operations, resulting in faster execution. | ||
| Rationale | A | Improve ROM usage and execution speed. | |
| B | Improve execution speed. When compared to unevenly-spaced data, power-of-two data can
Compared to an evenly-spaced data set, there should be minimal cost in memory or accuracy. | ||
| Model Advisor Checks | Embedded Coder > Identify questionable fixed-point operations | ||
| See Also | Formulation of Evenly Spaced Breakpoints in the Simulink documentation | ||
| Last Changed | R2010b | ||
![]() | cgsl_0101: Zero-based indexing | cgsl_0103: Precalculated signals and parameters | ![]() |

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |