RapidLib issueshttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues2018-01-19T14:11:33Zhttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/107Classification/regression model training - Progress and termination feedback2018-01-19T14:11:33ZFrancisco BernardoClassification/regression model training - Progress and termination feedbackUsers have found the training process cumbersome mainly concerning visibility of system status. This is a major usability problem that has been observed across different user interventions.
In many occurrences in which the users recor...Users have found the training process cumbersome mainly concerning visibility of system status. This is a major usability problem that has been observed across different user interventions.
In many occurrences in which the users recorded a medium-to-large amount of data, they could not understand whether the training process was crashing or just taking to long. In some cases it led them to terminated the browser window.
Recommendation: Implement asynchronous event notification in the training method (e.g., client code should subscribe to an event with a handler that reports progress and/or termination)Future APIhttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/106Thread hogging behaviour when training a classification/regression model2018-01-19T14:11:31ZFrancisco BernardoThread hogging behaviour when training a classification/regression modelThe "thread hogging" behaviour of the JS client API is problematic as it blocks the whole interface. This is a problem with a severity level between Major Usability problem and Usability catastrophe (Nielsen), observed with high frequenc...The "thread hogging" behaviour of the JS client API is problematic as it blocks the whole interface. This is a problem with a severity level between Major Usability problem and Usability catastrophe (Nielsen), observed with high frequency between different actions and users.
For instance, one participant, decided to move away from using the JS client library to trying to use a server side implementation (which also was problematic on its own). It would be beneficial to explore a Web-worker implementation to surpass this problem.
Recommendation:
Pursue a design pattern in which there are two learning modules (i.e., two classification modules, or two regression modules) one on the regular JS client code, another on the web-worker code. The web worker code receives training data from regular code, trains the model, and exports the JSON model to the regular JS code model, that loads it and runs test data with it.Future APIFrancisco BernardoFrancisco Bernardo