MotoHawk:Lookup Tables Overview - Revision history

Wendy.Bolakowski: /* MotoHawk Lookup Table Blocks */

2013-04-09T13:28:43Z

‎MotoHawk Lookup Table Blocks

Wendy.Bolakowski: /* MotoHawk Lookup Table Blocks */

2013-04-09T13:27:53Z

‎MotoHawk Lookup Table Blocks

Wendy.Bolakowski: /* MotoHawk Lookup Table Blocks */

2013-04-09T13:24:55Z

‎MotoHawk Lookup Table Blocks

Wendy.Bolakowski: /* Prelookup and Interpolation Blocks */

2013-04-09T13:07:49Z

‎Prelookup and Interpolation Blocks

Wendy.Bolakowski: /* Prelookup and Interpolation Blocks */

2013-04-09T13:06:38Z

‎Prelookup and Interpolation Blocks

Wendy.Bolakowski: /* Prelookup and Interpolation Blocks */

2013-04-09T13:03:57Z

‎Prelookup and Interpolation Blocks

Wendy.Bolakowski: /* MotoHawk 1D Lookup Table */

2013-04-09T12:56:59Z

‎MotoHawk 1D Lookup Table

Wendy.Bolakowski: /* Convert Prelookup Index Type (Index_T) to Double */

2013-04-09T12:56:04Z

‎Convert Prelookup Index Type (Index_T) to Double

Wendy.Bolakowski: /* Adapt Table */

2013-04-09T12:55:23Z

‎Adapt Table

Wendy.Bolakowski: /* Lookup Reference Blocks */

2013-04-09T12:54:38Z

‎Lookup Reference Blocks

@@ Line 11: / Line 11: @@
 Valid Matlab expressions such as Ones(1,5), or [1:.5:25] can be used for the breakpoints or the table data.
-[[Image: Lookup_Table_Interface.png ]]
+[[Image: Lookup_Table_Interface.png|500px ]]
 In a simple example, if the row breakpoint has two points [1,2] and the column breakpoint has two points [3,4].  Table Data is [10 10; 30 40].  Then, given row and column inputs of 1 and 4 as shown below, the output of the table is 20.

← Older revision		Revision as of 13:27, 9 April 2013
Line 21:		Line 21:
	Similarly, inputing r=1.7 and c=3.4 interpolates between the breakpoints to give an output of 27.99 as shown.		Similarly, inputing r=1.7 and c=3.4 interpolates between the breakpoints to give an output of 27.99 as shown.

−	[[Image: ~~Lookup_Ex1~~.png]]	+	[[Image: Lookup_Ex2.png]]

← Older revision		Revision as of 13:24, 9 April 2013
Line 2:		Line 2:

	MotoHawk provides a library of lookup table blocks that provide functionality similar to the native Simulink lookup table blocks, but also allow for calibration in MotoTune. The blockset provides 1D and 2D maps, as well as adaptive tables. Pre-lookup and Interpolation tables can be used to split up the breakpoints and table data separately. Reference tables can be used to access a table defined by a data store (Data Storage Blockset) somewhere else in the model. Data for the lookup tables can be stored in Volatile or Non-Volatile storage.		MotoHawk provides a library of lookup table blocks that provide functionality similar to the native Simulink lookup table blocks, but also allow for calibration in MotoTune. The blockset provides 1D and 2D maps, as well as adaptive tables. Pre-lookup and Interpolation tables can be used to split up the breakpoints and table data separately. Reference tables can be used to access a table defined by a data store (Data Storage Blockset) somewhere else in the model. Data for the lookup tables can be stored in Volatile or Non-Volatile storage.
		+
		+	The use of tables in the application is a means to save on CPU throughput. The results of complex equations are pre-computed and made available to the application through a fast lookup mechanism. Characterization of sensors is another common use of tables.
		+
		+	The '''Breakpoint Data''' is the "axis" of the table. 2D tables have a row axis and a column axis.
		+
		+	The '''Table Data''' is the calculation given the axis point(s) as the input.
		+
		+	Valid Matlab expressions such as Ones(1,5), or [1:.5:25] can be used for the breakpoints or the table data.
		+
		+	[[Image: Lookup_Table_Interface.png ]]
		+
		+	In a simple example, if the row breakpoint has two points [1,2] and the column breakpoint has two points [3,4]. Table Data is [10 10; 30 40]. Then, given row and column inputs of 1 and 4 as shown below, the output of the table is 20.
		+
		+	[[Image: Lookup_Ex1.png]]
		+
		+
		+
		+	Similarly, inputing r=1.7 and c=3.4 interpolates between the breakpoints to give an output of 27.99 as shown.
		+
		+	[[Image: Lookup_Ex1.png]]
		+
		+
		+

	== 1D and 2D Lookup Table Blocks ==		== 1D and 2D Lookup Table Blocks ==

← Older revision		Revision as of 13:07, 9 April 2013
Line 29:		Line 29:
	The prelookup provides the interpolation between two points on the axis. This is then connected to the 1D or 2D interpolation table. The output of a prelookup can only be connected to the input port of an interplation block.		The prelookup provides the interpolation between two points on the axis. This is then connected to the 1D or 2D interpolation table. The output of a prelookup can only be connected to the input port of an interplation block.

−	[[Image: ~~Prelookup_and_Interpolation~~.png]]	+	[[Image: Prelookup_and_Interpolation_Ex.png]]

← Older revision		Revision as of 13:06, 9 April 2013
Line 29:		Line 29:
	The prelookup provides the interpolation between two points on the axis. This is then connected to the 1D or 2D interpolation table. The output of a prelookup can only be connected to the input port of an interplation block.		The prelookup provides the interpolation between two points on the axis. This is then connected to the 1D or 2D interpolation table. The output of a prelookup can only be connected to the input port of an interplation block.

−	[[Image: ~~Prelookup_Int~~.png]]	+	[[Image: Prelookup_and_Interpolation.png]]

← Older revision		Revision as of 13:03, 9 April 2013
Line 24:		Line 24:

	[[Image:Prelookup_and_Interpolation.png]]		[[Image:Prelookup_and_Interpolation.png]]
		+
		+	Using the Prelookup and Interpolation blocks separately allows for one Pre-lookup to be connected to multiple Interplation Tables (one pre-lookup into different table data sets).
		+
		+	The prelookup provides the interpolation between two points on the axis. This is then connected to the 1D or 2D interpolation table. The output of a prelookup can only be connected to the input port of an interplation block.
		+
		+	[[Image: Prelookup_Int.png]]
		+

	===[http://mcs.woodward.com/content/motohawk/Documentation/CurrentVersion/HTML/MotoHawk_lib_Blocks/PrelookupIndexSearch.html MotoHawk Prelookup Table (Prelookup Index Search)]===		===[http://mcs.woodward.com/content/motohawk/Documentation/CurrentVersion/HTML/MotoHawk_lib_Blocks/PrelookupIndexSearch.html MotoHawk Prelookup Table (Prelookup Index Search)]===

@@ Line 5: / Line 5: @@
 == 1D and 2D Lookup Table Blocks ==
-===[[http://mcs.woodward.com/content/motohawk/Documentation/CurrentVersion/HTML/MotoHawk_lib_Blocks/LookupTable1D.html|MotoHawk 1D Lookup Table]]===
+===[http://mcs.woodward.com/content/motohawk/Documentation/CurrentVersion/HTML/MotoHawk_lib_Blocks/LookupTable1D.html MotoHawk 1D Lookup Table]===
 [[Image:Table1D.PNG]]

@@ Line 90: / Line 90: @@
 '''Adapt Min/Max:''' Adapt Min and Adapt Max are the saturation values of Table Data. This is to set the limit of Table Data in case of continuous accumulation of the Adapt Quantity. Note that the Min and Max Values in the MotoHawk Lookup Table or Interpolation do not apply here since the adaptation occurs during runtime, while the Min and Max Values apply for MotoTune only
-== Convert Prelookup Index Type (Index_T) to Double ==
+== [http://mcs.woodward.com/content/motohawk/Documentation/CurrentVersion/HTML/MotoHawk_lib_Blocks/ConvertPrelookupIndexType.html Convert Prelookup Index Type (Index_T) to Double] ==
 [[Image:Index_T_to_Double.PNG]]
 This MotoHawk™ block converts the custom index_T data type, which is output from a MotoHawk Prelookup block, into a double.  The output can be connected to a probe for measurement or debugging.

@@ Line 78: / Line 78: @@
 This MotoHawk™ block performs the same operation as a MotoHawk Interpolation (2-D) block, but does not define any data or create any VarDecs visible from MotoTune.
-==Adapt Table ==
+==[http://mcs.woodward.com/content/motohawk/Documentation/CurrentVersion/HTML/MotoHawk_lib_Blocks/AdaptTable.html Adapt Table] ==
 [[Image:adapttable.jpg]]
@@ Line 89: / Line 89: @@
 '''Adapt Min/Max:''' Adapt Min and Adapt Max are the saturation values of Table Data. This is to set the limit of Table Data in case of continuous accumulation of the Adapt Quantity. Note that the Min and Max Values in the MotoHawk Lookup Table or Interpolation do not apply here since the adaptation occurs during runtime, while the Min and Max Values apply for MotoTune only
 == Convert Prelookup Index Type (Index_T) to Double ==

@@ Line 54: / Line 54: @@
 The reference blocks perform the same function as 'Non-reference' blocks, except they don't define any data, or create variables that can be viewed in MotoTune.
-The MotoHawk Data Definition block under MotoHawk Data Storage can be used to define the referenced data.  The storage class can then be selected of the data - ex.  Non-Volatile can be selected for the Data, and the table would reference NV data.  Breakpoints can similarly be referenced to the table Breakpoints using the Prelookup (1D/2D) Reference blocks.  The table values are referenced to the data storage through the MotoHawk Interpolation (1D/2D) Reference block.
+The [http://mcs.woodward.com/content/motohawk/Documentation/CurrentVersion/HTML/MotoHawk_lib_Blocks/DataDefinition.html MotoHawk Data Definition block] under MotoHawk Data Storage can be used to define the referenced data.  The storage class can then be selected of the data - ex.  Non-Volatile can be selected for the Data, and the table would reference NV data.  Breakpoints can similarly be referenced to the table Breakpoints using the Prelookup (1D/2D) Reference blocks.  The table values are referenced to the data storage through the MotoHawk Interpolation (1D/2D) Reference block.
 '''Note:''' Care needs to be taken to ensure the breakpoint and table dimensions match with the reference data definitions.  The reference blocks don’t have a check to prevent a dimension overrun.