Mercurial > hg > ltpda
comparison m-toolbox/html_help/help/ug/gui_gltpda_1_content.html @ 0:f0afece42f48
Import.
| author | Daniele Nicolodi <nicolodi@science.unitn.it> |
|---|---|
| date | Wed, 23 Nov 2011 19:22:13 +0100 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| -1:000000000000 | 0:f0afece42f48 |
|---|---|
| 1 <p><br> | |
| 2 <h2>Data handling in Simulink</h2><hr> | |
| 3 | |
| 4 Since SIMULINK can only send among blocks a limited set of object types (that is, inside Simulink lines can only travel numbers, | |
| 5 vectors or Simulink defined signals), <b>the main concept about LTPDA GUI and LTPDA Simulink models is that what's passed among | |
| 6 blocks is not a true LTPDA object (an AO, a filter, a specwin or so), but rather a pure number, intended as an index inside a | |
| 7 given array of objects.</b><br><br> | |
| 8 | |
| 9 Every analysis block in a LTPDA model produces the output of its calculation, then stores this output into a global array - which will be | |
| 10 accessible by all following functions/blocks - and send back to Simulink just the index of this newly added object inside the array. | |
| 11 <br><br> | |
| 12 For example:</p><br><br> | |
| 13 <img src="images/model_2.png" alt="A simple analysis" border="1"> | |
| 14 <br> | |
| 15 <br> | |
| 16 <p> | |
| 17 <b>The first block</b> load create an AO from a file on disk. This AO is saved in a global array: assuming the array was empty, this is | |
| 18 the 1st object, so '1' is the number sent by the first block into Simulink.<br> | |
| 19 <b>The second block</b> receives this '1': the corresponding (1st) object is retrieved from the array, then the analysis function (<tt>pwelch</tt>) is applied. | |
| 20 The output is appended back into the array, as 2nd element. So, '2' is the content of the signal leaving the second block.<br> | |
| 21 <b>The third block</b> receives '2', retrieves the corresponding (2nd) object from the array and produces a plot of it. | |
| 22 <br><br> | |
| 23 Thus, during the analysis cycle the array of objects becomes populated: unless differently set, all the temporary objects created | |
| 24 during the analysis will be canceled at the end of the analisys itself. | |
| 25 | |
| 26 <br><br><br> | |
| 27 | |
| 28 The LTPDA GUI is based on two global arrays: | |
| 29 <ul> | |
| 30 <li> The aforementioned '<b>Input array</b>', which encloses all the LTPDA objects created by the user (for example, | |
| 31 loading from file) and the objects generated during the analysis.<br>This is shown into the main panel of the LTPDA GUI.<br></li> | |
| 32 <li> The '<b>Output array</b>', meant as a way to separate primary objectives of the analysis from the | |
| 33 other - working - objects, contained in the Input array.<br>This is shown into its own panel, the Output panel.</li> | |
| 34 </ul> | |
| 35 | |
| 36 The only way to save an object into the Output array is using the proper 'Send to Output' block, which will copy the object | |
| 37 passed from the Input to the Output array.<br> | |
| 38 <br><br> | |
| 39 <h2>Parameters</h2><hr> | |
| 40 | |
| 41 In order to enclose all the parameters of each block together with the Simulink model file, each parameters list is converted | |
| 42 into a string and saved into the Block Description, a specific field of every block in Simulink.<br> | |
| 43 Every time the user selects a block inside a valid LTPDA model the LTPDA GUI will automatically read this description to convert | |
| 44 it back to a proper plist. 'Valid' LTPDA models are those created by the GUI, thus containing the short annotation with the | |
| 45 author's name, time and date of creation and so on.<br><br> | |
| 46 | |
| 47 For more information on parameters handling, see the paragraph regarding the Parameters panel. <br><br><br> | |
| 48 | |
| 49 </p> | |
| 50 |