Closed nopbyte closed 6 years ago
Hello
Thanks for the feedback!
I probably did not build the wasm module with the right options, forgetting to include the virtual file system. I pretty sure this scenario works with the asm version though. Could you test that?
If you data is big you could run into some known issues with the FS (https://github.com/mljs/libsvm/issues/6) . Using a precomputed kernel will avoid that. Here is an example of using a precomputed kernel with libsvm-js: https://github.com/jajoe/tutorial-nodejs/blob/4931ad30b282416f174951f59971dae9e409c426/image-classification/index.js
I'll have a look at the FS issue later this week, probably during the week-end.
Hi @stropitek I tested with the asm version and it works. I get a string back without any problems. I will look into the precomputed kernel example and try this out. Thanks a lot for your pointers.
@nopbyte I released v0.1.3 with the fix
Hi,
first of all. Congrats! This tool seems to be really useful. I have a problem with many features and I tried another svm library before (https://github.com/karpathy/svmjs). libsvm is performing much better, as expected.
I am having an issue when I try to get the result of serlializeModel to port my model from the server to the browser since I only want to do training once. Here is a minimal example that reproduces the error:
The output I get from the algorithm is the following:
There seems to be an issue with fs somewhere?
I am using Node v8.1.2 with NVM. Which is the same node version you have in your README file.
Thanks a lot for your help,