RapidLib issueshttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues2017-05-02T14:07:05Zhttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/46Decide which model types the API should support2017-05-02T14:07:05ZMichael ZbyszyńskiDecide which model types the API should support#45 and #44 exist for random forest and svm.
Which other model types should be part of the API.#45 and #44 exist for random forest and svm.
Which other model types should be part of the API.API v0.2https://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/47Virtual train in modelSet2017-05-02T14:07:05ZMichael ZbyszyńskiVirtual train in modelSetMarco reported:
"I just noticed that the method train of modelSet isn't virtual. Looks like it is supposed to be."
Marco reported:
"I just noticed that the method train of modelSet isn't virtual. Looks like it is supposed to be."
API v0.2Michael ZbyszyńskiMichael Zbyszyńskihttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/48Initialize variables in header?2017-05-02T14:07:05ZMichael ZbyszyńskiInitialize variables in header?C++11 lets use initialize variables in the header. That might streamline code in some places (eg the modelSet constructor).
C++11 lets use initialize variables in the header. That might streamline code in some places (eg the modelSet constructor).
Future APIhttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/49Put class-specific JSON into classes2017-05-02T14:07:05ZMichael ZbyszyńskiPut class-specific JSON into classesI put a bunch of the JSON writing code into the modelSet class, but the model-specific stuff should be in the actual models.
Fix it.I put a bunch of the JSON writing code into the modelSet class, but the model-specific stuff should be in the actual models.
Fix it.API v0.2Michael ZbyszyńskiMichael Zbyszyńskihttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/50Document C++ JSON api2017-05-02T14:07:05ZMichael ZbyszyńskiDocument C++ JSON apiThe C++ JSON api seems to have all of the necessary functions.
It needs to be documented, and new DOxygen documentation needs to go on our website.The C++ JSON api seems to have all of the necessary functions.
It needs to be documented, and new DOxygen documentation needs to go on our website.API v0.2Michael ZbyszyńskiMichael Zbyszyńskihttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/54Test Tiaga integration2017-05-02T14:07:05ZMichael ZbyszyńskiTest Tiaga integrationI made this to test taigaI made this to test taigaAPI v0.2Michael ZbyszyńskiMichael Zbyszyńskihttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/55test taiga 22017-05-02T14:07:05ZMichael Zbyszyńskitest taiga 2trying again to trigger taigatrying again to trigger taigaAPI v0.2Michael ZbyszyńskiMichael Zbyszyńskihttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/56Get this project organized in Taiga2017-05-02T14:07:05ZMichael ZbyszyńskiGet this project organized in Taiga@francisco I'm going to try to get these issues in Taiga today.@francisco I'm going to try to get these issues in Taiga today.API v0.2Michael ZbyszyńskiMichael Zbyszyńskihttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/59Build Essentia with Emscripten2017-05-02T14:07:05ZMichael ZbyszyńskiBuild Essentia with EmscriptenIf we want to use Essentia features in our API, we need to get it into JavaScriptIf we want to use Essentia features in our API, we need to get it into JavaScriptFuture APIhttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/63Rapid-Myo v1.0.02017-05-02T14:07:05ZFrancisco BernardoRapid-Myo v1.0.0Francisco BernardoFrancisco Bernardohttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/66MFCC example2017-05-02T14:07:05ZMichael ZbyszyńskiMFCC exampleI'm sick of examples that are fancy interpolation. It's hard to get around that with just mouse input.
Make a demo using MFCC from Maxi.I'm sick of examples that are fancy interpolation. It's hard to get around that with just mouse input.
Make a demo using MFCC from Maxi.API v0.3Michael ZbyszyńskiMichael Zbyszyńskihttps://gitlab.doc.gold.ac.uk/rapid-mix/RapidLib/-/issues/67Improve handling of "k"2017-05-02T14:07:05ZMichael ZbyszyńskiImprove handling of "k"MZ just added getK() and setK() to the kNN model. This brings up some interesting issues:
1. I can't think of a case where k == 2 is better than k == 1. Disallow it?
1. Ties go to the first class found. Find a better metric? Dista...MZ just added getK() and setK() to the kNN model. This brings up some interesting issues:
1. I can't think of a case where k == 2 is better than k == 1. Disallow it?
1. Ties go to the first class found. Find a better metric? Distance? Average distance?
1. If setK() asks for a k that is greater than the current number of neighbours, then k is set to the number of neighbours. Maybe kNN should remember the number that the user requested so that k can be increased if new neighbours are added?
1. Using getK() and setK() in a modelSet required casting a baseModel* down the inheritance chain. Is this bad design? How will this work if more parameters are exposed in more models?
This issue should probably be broken up into sub-issues.
Future APIMichael ZbyszyńskiMichael Zbyszyński