Css-methodSelection

[sevisal]

Purpose

Let user specify which methods they want to use.

In brief

• Changed XML files to include the functions within a plugin
• Adapted GUI to let user indicate which methods to use
• Allow changaing any methods and plugin's options from the library

Method selection

Each plugin can have multiple functions in it. Besides, each method can have its own options, which are directly read from the plugin's original library.

XML changes

The tag method is now available. This can be added to each plugin to indicate which function from the plugin needs to be executed by passing it's name in type. It's order sensitive as the methods will be executed in the same order they are defined. You can now use the tag options rigth inside the plugin or inside a method, defining the plugin's initialisation options or the method's options, respectively.

    <Modelling name="Modelling">
        <plugin type="SVR">
            <options>
                <C>
                     0.01
                </C>
            </options>
            <method type="fit">
                <options>
                    <X>
                         X
                    </X>
                    <Y>
                         Y
                    </Y>
                </options>
            </method>            
            <method type="predict">
                <options>
                    <X>
                         X_test
                    </X>
                </options>
            </method>
        </plugin>
    </Modelling>

Plugin GUI

When indicating the plugin for each module it also asks if you want to add a method to the plugin. To do so, there is a dropdown menu with all the available functions* along with some buttons to add, delete or move each method. There's a default __init__ method that contains all options available when loading a model. Upon adding a new method, the options available for that method are also displayed and can be modified.

*Note: as of right now we are only offering the functions that are defined in both the template and the original library. This should be changed in the future.

When an option's name is either X or Y**, the GUI creates a dropdown menu for it's value, displaying the uploaded data. This data will then be approprately passed to the method.

**Note: This should be changed in the future to account for different data names.

Progress tracker

The progress tracker functionaility has been adapted to load the methods from the XML as well as the preloaded options. This allows the user to modify not only the base options of the model, but also which methods need to be executed and in which order. Furthermore, it loads any previously defined options for each method to facilitate the modification of any of them.