Skip to Main Content Skip to Search
Product Documentation

fi Object Properties

The properties associated with fi objects are described in the following sections in alphabetical order.

bin

Stored integer value of a fi object in binary.

data

Numerical real-world value of a fi object.

dec

Stored integer value of a fi object in decimal.

double

Real-world value of a fi object stored as a MATLAB® double.

fimath

fimath properties associated with a fi object. fimath properties determine the rules for performing fixed-point arithmetic operations on fi objects. fi objects can get their fimath properties from a local fimath object or the global fimath. The factory-default configuration of the global fimath has the following settings:

             RoundMode: nearest
          OverflowMode: saturate
           ProductMode: FullPrecision
  MaxProductWordLength: 128
               SumMode: FullPrecision
      MaxSumWordLength: 128

To learn more about fimath objects and the global fimath, refer to Working with fimath Objects. For more information about each of the fimath object properties, refer to fimath Object Properties.

hex

Stored integer value of a fi object in hexadecimal.

int

Stored integer value of a fi object, stored in a built-in MATLAB integer data type. You can also use int8, int16, int32, int64, uint8, uint16, uint32, and uint64 to get the stored integer value of a fi object in these formats.

NumericType

The numerictype object contains all the data type and scaling attributes of a fixed-point object. The numerictype object behaves like any MATLAB structure, except that it only lets you set valid values for defined fields. For a table of the possible settings of each field of the structure, see Valid Values for numerictype Structure Properties in the Fixed-Point Toolbox™ User's Guide.

oct

Stored integer value of a fi object in octal.

  


Free Early Verification Kit

Learn how to apply early verification to your development process through these technical resources.

How much time do you spend on testing to ensure implementation meets system-level requirements?

 © 1984-2012- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS