You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Status Quo
A benchmark instance or experiment instance receives various parameters as input. Currently, the input is given by defining parameters in a dataset_list and in a model_classes_and_params list.
Example:
Subsequently, they are assigned to the attributes of different classes and/ or separated into further categories. Currently, this happens partly in the __post_init__() of the Experiment(ABC) class and the __post_init__() of the Model(ABC). So far, we separate the params into _data_params and model_params.
Problem
It would be great, to have one dedicated part to post-process, split and assign the input params. In my eyes, this should be on the experiment level.
It's great to distinguish between _data_params and model_params. Further, I think we should introduce pred_params, which saves all prediction task-related information.
The text was updated successfully, but these errors were encountered:
Status Quo
A benchmark instance or experiment instance receives various parameters as input. Currently, the input is given by defining parameters in a
dataset_list
and in amodel_classes_and_params
list.Example:
Subsequently, they are assigned to the attributes of different classes and/ or separated into further categories. Currently, this happens partly in the
__post_init__()
of theExperiment(ABC)
class and the__post_init__()
of theModel(ABC)
. So far, we separate the params into_data_params
andmodel_params
.Problem
_data_params
andmodel_params
. Further, I think we should introducepred_params
, which saves all prediction task-related information.The text was updated successfully, but these errors were encountered: