RapidLib issueshttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues2018-01-19T14:11:31Zhttps://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 Bernardohttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/93Minimum number of hidden nodes?2017-08-18T10:53:48ZMichael ZbyszyńskiMinimum number of hidden nodes?I've noticed that a one input neural network isn't very effective. It can't express a very complex curve, since it only has a series of two sigmoid nodes to work with.
Maybe the hidden layer should have a minimum number of nodes?I've noticed that a one input neural network isn't very effective. It can't express a very complex curve, since it only has a series of two sigmoid nodes to work with.
Maybe the hidden layer should have a minimum number of nodes?https://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/90RapidLib: Classifiers with string labels2017-08-30T12:05:37ZMichael ZbyszyńskiRapidLib: Classifiers with string labelsRapidLib classifiers should natively deal with strings as labels, rather than rely on the unordered_map in the facade.RapidLib classifiers should natively deal with strings as labels, rather than rely on the unordered_map in the facade.Future APIMichael ZbyszyńskiMichael Zbyszyńskihttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/87DTW "normalisation"2017-08-30T11:52:39ZMichael ZbyszyńskiDTW "normalisation"This is probably more complex than can be addressed in RapidLib.
Some kinds of normalisation could be useful for certain DTW matching. Shifting a gesture in space and/or in size will increase the matching cost in DTW. Location and siz...This is probably more complex than can be addressed in RapidLib.
Some kinds of normalisation could be useful for certain DTW matching. Shifting a gesture in space and/or in size will increase the matching cost in DTW. Location and size could be normalized. For example, a user might want to match the letter "Z" no matter where it is drawn on a canvas, or whether it's big or small.Future APIhttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/61Wekinator-like output limits2017-08-16T13:17:22ZMichael ZbyszyńskiWekinator-like output limitsWekinator has some options for limiting the output. Duplicate those in our API.Wekinator has some options for limiting the output. Duplicate those in our API.Future API