Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
development:wizard [2018/10/21 15:01] 42.49.180.224 [Implement a graphical user interface as a wizard for certain analysis protocols] |
development:wizard [2017/08/17 11:21] (current) 127.0.0.1 external edit |
||
---|---|---|---|
Line 6: | Line 6: | ||
</note> | </note> | ||
- | ====== Implement a graphical user interface as a "wizard" for certain analysis protocols ====== | + | ====== Implement a graphical user interface as a "wizard" for certain analysis protocols ====== |
//This project has been completed, the documentation below is only provided for future reference.// | //This project has been completed, the documentation below is only provided for future reference.// | ||
Line 12: | Line 12: | ||
The idea is to make a graphical user interface that allows the user to step through a sequence of functions, where for example each block consists of a computation with the associated graphical feedback. E.g. consider the following analysis protocol: | The idea is to make a graphical user interface that allows the user to step through a sequence of functions, where for example each block consists of a computation with the associated graphical feedback. E.g. consider the following analysis protocol: | ||
- | <code matlab> | + | <code matlab> |
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | ||
% Step 1: do the preprocessing | % Step 1: do the preprocessing | ||
Line 59: | Line 59: | ||
cfg.layout = 'CTF151.lay'; | cfg.layout = 'CTF151.lay'; | ||
multiplotTFR(cfg, TFRhann); | multiplotTFR(cfg, TFRhann); | ||
- | </code> | + | </code> |
Using the wizard on this analalysis protocol would result in a graphical user interface like this: | Using the wizard on this analalysis protocol would result in a graphical user interface like this: | ||
Line 66: | Line 66: | ||
{{:development:wizard:wizard2.png|}} | {{:development:wizard:wizard2.png|}} | ||
- | Pressing the "next" button would result in the snippet of matlab code inside the edit box to be executed, pressing the "previous" button results in going one step back. The code would be executed in the main Matlab workspace as if it were a normal script, which means that the variable names are also defined in the wizard. Loading and saving data from/to files would also be easy to implement using the standard Matlab "uigetfile" function. | + | Pressing the "next" button would result in the snippet of matlab code inside the edit box to be executed, pressing the "previous" button results in going one step back. The code would be executed in the main Matlab workspace as if it were a normal script, which means that the variable names are also defined in the wizard. Loading and saving data from/to files would also be easy to implement using the standard Matlab "uigetfile" function. |
+ | |||
+ | The wizard would have to read and parse the matlab script that contains the documentation and the code, and it would have to detect the sections by the "%%%%%" separators. To make a usefull wizard using this graphical interface would then only require making example matlab scripts with a well-defined structure with comments and with code. | ||
- | The wizard would have to read and parse the matlab script that contains the documentation and the code, and it would have to detect the sections by the "%%%%%" separators. To make a usefull wizard using this graphical interface would then only require making example matlab scripts with a well-defined structure with comments and with code. | ||
===== Ideas for further refinement ===== | ===== Ideas for further refinement ===== | ||