1. LTPDA Graphic User Interface summary and status
N. Tateo
26/06/2007

2. GUI in Matlab Workspace LTPDA functions package
GUI summary
The analysis software is composed by 3 different elements:
Simulink Window
GUI in Matlab Workspace
LTPDA functions package
Simulink Window
Parameters Array
AO Array
Library

3. The elements in the GUI 4. The Simulink window 3. The Parameters array
2. The AO array
1. The functions library

4. 1. The functions library …
The package consists of many functions, each accepting as input the data to be analyzed and the proper parameters:
Matlab
ltpda_lpsd (data, parameters)
ltpda_pwelch (data, parameters)
ltpda_cohere (data, parameters) …

5. 1. The functions library To work in Simulink all these functions
are “converted” into Simulink blocks:
Each block is identified by a (visible) tag, which is the function name, and by a (invisible) handle, which is an univocal number assigned by Simulink.
Matlab
Simulink
ltpda_lpsd data, parameters)
ltpda_pwelch (data, parameters)
ltpda_cohere (data, parameters)
ltpda_lpsd
ltpda_pwelch
ltpda_cohere

6. 2. The GUI Analysis Objects (the data) name: AnOb
When the user starts the GUI, two arrays are created:
Matlab Workspace
Analysis Objects (the data) name: AnOb
Parameters (the parameters) name: Parameters
These are defined as global variables, so they are entirely and freely accessible by any function.

7. Analysis Objects Array name: AnOb
The AO Array
Analysis Objects Array name: AnOb
AO1 name, provenance, data, history…
AO2 name, provenance, data, history…
AO3 name, provenance, data, history…
AO4 name, provenance, data, history… … 1 2 3 4 5

8. Parameters Array name: Parameters
The Parameters Array
Parameters Array name: Parameters
Paramlist1 param1, param2, param3,…
Paramlist2 param1, param2, param3,…
Paramlist3 param1, param2, param3,…
Paramlist4 param1, param2, param3,… …
Block handle
Block handle
Block handle
Block handle
Block handle

9. Where everything goes AO1 name, provenance, data, history… 1
ltpda_pwelch (data, parameters)
Paramlist1 param1, param2, param3,…
Block handle
AO2 name, provenance, data, history… 2
ltpda_cohere (data, parameters)
AO3 name, provenance, data, history… 3
Paramlist2 param1, param2, param3,…
Block handle
AO4 name, provenance, data, history… 4
ltpda_pwelch (data, parameters)
Paramlist3 param1, param2, param3,…
Block handle

10. When the user select a block, the GUI retrieves the block handle.
Parameters setting
When the user select a block, the GUI retrieves the block handle.
If no paramlist is associated to that handle, a new list is created and the panel let the user to compile its values.
Paramlist1 param1, param2, param3,…
Block handle

11. function(data,parameters)
When the user starts the analysis, each function retrieves the handle of its own block and by that the proper paramlist from the Parameters array in memory.
Block handle
Paramlist1 param1, param2, param3,…
This provides each function with the correct relative parameters.

12. function(data,parameters)
Each function similarly retrieves the data from the AO array in memory, by the pointer which is sent in the Simulink diagram.
AO1 name, provenance, data, history… 1
Thus every function retrieves by itself all its data and parameters.

13. Consequences
The entire parameters list is saved and kept outside Simulink: this makes easier to modify previous analysis and to run nested loops, ie. multiple analyses varying one parameter at the time.
No delay is introduced by Simulink, since no real data are sent inside its diagram (ie, its workspace). There is only one copy of AOs and parameters saved in memory, and every function can retrieve them using the correct pointer (the AO ordinal number for data, the block handle for parameters).

14. Consequences
The analysis speed is maximized, since everything which could slow it down (such as GUI control cycle) is stopped when the analysis is started.
The analysis results can easily be gathered and saved together, data + parameters + diagram, thus ensuring excellent traceability and a simple data analysis management.

15. Complete the implementation of functions in the Simulink library.
Future steps
Convert the GUI into a true operative tool, implementing the ability to save and load analysis (ie, to import and export data parameters and diagrams).
Enable it to deal with multiple analysis at once, ie. more than a single Simulink window at the time.
Complete the implementation of functions in the Simulink library.
Turn the library into a Simulink toolbox, with a tree structure which will make it easier and faster to use.

16. Future steps Add the Color Control Panel.
Implement a validation cycle, to check the consistency of the parameters set by the user prior to the execution of the analysis.
Implement the code to enable nested loops (do we want some kind of optimization system?).
Let the people in the labs to use it, and mark down their feelings.