Andreas Mueller
Andreas Mueller
I think the real issue here is the design. The flow is basically made to mirror the OpenML schema, so going from sklearn estimator to flows mostly makes things strings....
Well, the OpenMLFlow class is not really the schema, right? The layer would be a python API to the OpenML flow, which is what ``openml-python`` is supposed to be, right?
Hm I think I need to come up with an actual example to make this more clear.
@janvanrijn says the reason it's not there is that the times are currently on a fold basis, and he wasn't sure if having the mean makes sense. I think it...
In the meantime, you can get the information via ```python import openml openml.runs.get_run(10398294).fold_evaluations['usercpu_time_millis_training'][0] ``` That gets you per-fold time (same exists for wallclock)
Also, it looks like the R interface uploads this: https://www.openml.org/t/31 This raises the question whether this should be done in the language bindings or the backend. If we do it...
Actually, thinking about it now, it might be easier to do this on the openml-python side if R is already doing it. We can always get the old data from...
The XML send by the client code is ``` '\ntimestampcylinder_numberjob_number' ``` Not sure if that is correct? @joaquinvanschoren ?
Do you mean passing all values at once as a string? I tried that before opening the issue, the server-side validation didn't seem to like it the way I did...