Open adrienpacifico opened 1 year ago
@adrienpacifico you are right, labels should be changed to validation.
For test data there should be separate function score
or evaluate
Do you think documentation/docstring (e.g. line 90) should also be modified?
For test data there should be separate function score or evaluate
Why so? Users could have an very easy way to separate train, val and test that way?
Do you think documentation/docstring (e.g. line 90) should also be modified?
Yes, all confusing places should be updated.
Why so? Users could have an very easy way to separate train, val and test that way?
evaluate()
function might be a little simpler than extending the training function with new arguments.
Hi, I think that there are some elements that creates confusion (at least to me) between different sets in mljar.
One example are graphs created by mljar:![image](https://user-images.githubusercontent.com/6614121/194285188-cbcb98b5-c8cd-437f-8fe4-9868ef7057d0.png)
The "test" set from the learning curve is actually the validation set (or cross-validation set)! That might be to some extent confusing.
It would be nice to:
Such an option could be nice to have on all the metrics produced with the validation set on the test set.
it could be done as such:
ps: it could also be nice to give a X_val, y_val option such in addition to cv (i.e. cv seems to provide a lot more flexibility, but it is not user friendly if you just want to use a validation set.