Mercurial > hg > ltpda
comparison m-toolbox/html_help/help/ug/gui_gltpda_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 <h2>Introduction</h2> | |
2 | |
3 | |
4 <p> | |
5 The LTPDA package contains a sophisticated graphical programming interface which allows the user to construct and execute | |
6 data analysis pipelines entirely graphically. | |
7 </p> | |
8 | |
9 <img src="images/model_1.png" alt="A LTP Analysis in Simulink" border="1"> | |
10 <br> | |
11 <br> | |
12 <br> | |
13 <br> | |
14 <p> | |
15 The Simulink drawing interface is used to construct the analysis pipelines. The blocks that compose the analysis | |
16 pipelines are drawn from the LTPDA blockset. The LTPDA Analysis GUI then executes the commands represented by each | |
17 block in the appropriate order in order to achieve the desired analysis pipeline. | |
18 <br><br> | |
19 To start the LTPDA GUI use the command <tt>ltpdagui</tt> . | |
20 | |
21 <div class="fragment"><pre> | |
22 >> ltpdagui | |
23 </pre></div> | |
24 <br> | |
25 If there's no open LTPDA GUI window, the user will be asked to log in:<br><br> | |
26 <img src="images/login.png" alt="A simple analysis" border="1"><br><br> | |
27 These data are not mandatory, as long as the user do not want to connect to a LTPDA Repository, for example to retrieve previous | |
28 analyses or to send in his own work. If the user just wants to use the software to compile trials or personal analyses, not meant to | |
29 be shared with others, he can leave these fields empty: the GUI will identify him as anonymous ('<tt>JohnDoe</tt>'), and this name | |
30 will be stored into every produced model.<br> | |
31 On the contrary, if the GUI has to produce shared results, i.e. if the user want to submit/retrieve from an LTPDA Repository, | |
32 these login and password are those necessary to access the repository database. The user must possess a valid account, which | |
33 can be requested to the database administrator.<br> | |
34 The username will be used also to ensure better traceability, storing the name itself into a short description created using | |
35 the LTPDA GUI.<br><br> | |
36 However, it's possible at anytime to log off and re-log in, using different data, so it will be possible to type in valid | |
37 credentials to access a repository only when needed. | |
38 <br><br><br> | |
39 | |
40 <hr> | |
41 The first appearance of the GUI is:<br><br> | |
42 <img src="images/ltpdagui_1.png" alt="A simple analysis" border="1"> | |
43 <br><br> | |
44 The upper part of the window lists all the possible panels: clicking on the corresponding tab the proper panel | |
45 will be drawn below.<br><br> | |
46 The help associated to each panel will be dealt into different pages. | |
47 <br><br><br> | |
48 | |
49 </p> | |
50 |