-
Notifications
You must be signed in to change notification settings - Fork 17
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
fit_curve return schema #425
Comments
Likewise, the openeo-processes/proposals/predict_curve.json Lines 19 to 26 in 0dd3ab0
|
@clausmichele Do you agree? I think we made it a data cube to allow large scale fitting on data cubes? |
@m-mohr yes indeed. If we would modify the process as @soxofaan seggests, I guess that then it should be called inside a Maybe let's check also if @ValentinaHutter has an opinion on this, since she was the last one working on the implementation of it. |
reduce_dimension doesn't work, but apply_dimension may work. |
(related to other "ml" tickets like e.g. #396 (comment))
fit_curve
currently returns a datacube:openeo-processes/proposals/fit_curve.json
Lines 79 to 84 in f8f6731
But I think it should return the array of "trained" parameters. It should basically correspond (in number of items) to the
parameters
parameter of thefunction
callbackopeneo-processes/proposals/fit_curve.json
Lines 52 to 59 in f8f6731
Unlessfit_curve
is intended to do the "training" and "prediction" within the same process: you provide a input data cube and a model (least squares cure fitting), the model is trained and immediately applied to the same input data to "smooth" it in some way?The text was updated successfully, but these errors were encountered: