Boost decoupling of MLAir and data handlers
Some parameters that are related to our data handlers could be removed from MLAir's workflow and run_module to serve as a more general workflow. This refers for example to the parameters window_history_length
and window_lead_time
which may have no influence for custom data handlers. These parameters are only used to build the data handler, but this could be also done by default values inside the data handler. If these parameters should be adjusted, it would be still possible to add the key value pair in the workflow's init call. All kwargs will be also stored in the data store and are therefore available for the data handler.
Create a list of parameters, that are candidates for removal:
-
window_history_length
-
window_lead_time
-
interpolation_method
-
interpolation_limit
-
data_origin
-
variables
-
statistics_per_var
-
extreme_values
-
extremes_on_right_tail_only
-
neighbors
-
overwrite_local_data
(<- discussion on this parameter) -
sampling
(<- discussion on this parameter, used in postprocessing - for what?) -
store_data_locally
-
store_processed_data
(<- discussion on this parameter, actually I forgot the meaning of this) -
target_dim
(<- discussion on this parameter, this could be required for all postprocessing routines, but is currently not used in fact! - is there still too much hardcoded? - solved in #272 (closed)) -
target_var
(<- discussion on this parameter)
It is not easy to remove parameters, that change for subsets like start
and min_length
. How to deal with this?
Next indicate which parameters are going to be removed!
Further tasks
-
decouple make prediction in postprocessing (solved in #272 (closed))