-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Readme example does not seem correct #11
Comments
I'm sorry, the docs currently only reflect the master branches of the corresponding packages. Installing both |
There's still an issue with Maybe you want to avoid MLJ altogether in your "local" API. I don't see anything wrong with using matrices there, but if you want to allow generic tables input, then you could use Of course, if you don't care to have a separate local API at all, then these comments are not relevant. |
Good point, I didn't know that |
@davnn I wonder if it wouldn't be timely to make some sort of doc update, now that the detector models are MLJ-discoverable and the API has stabilised somewhat. It needn't too comprehensive just now, but correct would be good 😉 |
I'm working on it 👍 Edit: One reason why the docs are not finished yet is that I'm not happy with the API as it is right now, see JuliaAI/MLJ.jl#780. |
The README and documentation is up to date now. EDIT: @ablaom MLJ docs will follow shortly. |
Looks great, thanks! |
I guess
X[train,:]'
was meant here?And
score
does not appear to be defined:The text was updated successfully, but these errors were encountered: