machinelearnjs / machinelearnjs/libsvm-ts
Deserialise model is not exposed
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
At the moment, it is not possible to load a model..... only to save one. This seems very disadvantageous if you pre-train models. The only way to get my models to work with this library is to train every time someone loads my application.
It also appears, that the WASM is served from what ever route you are currently on.
i.e. If i have a ReactJS app with multiple routes and i enter the application at localhost:3000 then i can load the wasm, provided it is in the public folder. However, if i go to my login page first at localhost:3000/auth/login then it tries to load the wasm from localhost:3000/auth/libsvm.wasm.
There doesn't appear to be much activity on this project, which is a real shame. ML and the Web are going to explode even more than they already have.
@JasonShin @stropitek
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the model serialization API and the WASM loading entry point; the issue names no files or tests. Verify the library can load a previously saved model and that WASM resolution works when the application starts on a nested route such as /auth/login.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript, wasm
- Domain
- machine-learning, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100