LTPDA Graphic User Interface summary and status

1
LTPDA Graphic User Interfacesummary and status
N. Tateo 26/06/2007
2
GUI summary

• The analysis software is composed by3 different
  elements

3
The elements in the GUI
1. The functions library
2. The AO array
3. The Parameters array
4. The Simulink window
4
1. The functions library
The package consists of many functions,each
accepting as input the data to be analyzedand
the proper parameters
Matlab

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 isan univocal number assigned by Simulink.
Matlab
Simulink
6
2. The GUI
When the user starts the GUI, two arrays are
created
These are defined as global variables, so they
areentirely and freely accessible by any
function.
7
The AO Array
1
2
3
4
5
8
The Parameters Array
Block handle
Block handle
Block handle
Block handle
Block handle
9
Where everything goes
10
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.
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.
This provides each functionwith 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.
1
Thus every function retrieves by itselfall its
data and parameters.
13
Consequences

• The entire parameters list is saved and
  keptoutside 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
  savedtogether, data parameters diagram, thus
  ensuring excellent traceability and a simple data
  analysis management.

15
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 functionsin 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
  consistencyof the parameters set by the user
  prior to the executionof 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
  downtheir feelings.