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
Thanks for a wonderful product. The more I read the source code, the more impressed I am by the quality of this development.
In our problem, the model must be able to predict only some points in the time series that satisfy the conditions. We would like to have a filtering method based on which we could determine whether a given window should be used for training / validation or not.
Use case
I saw that one of the selection mechanisms is available_mask, but its use does not completely solve our problem. Masks can be more specific. May be the library already has a solution for my problem, but I couldn't find it.
I will give an example of a task where window filtering is required. In the simplest case, let us be given vector y. But we would like to be able to make a forecast not for all ('unique_id', 'ds') points, but for those that satisfy some criteria. I mean we have to select some time periods for prediction, which are specific to every individual client. The criterion can filter out a very large number of windows from training. This criterion can be calculated in advance by the user (calculated before training and provided by the user to the model).
Suggested solution:
I suggest to enter another reserved name for the column (like 'unique_id', 'ds', 'available_mask'). For the example below I'm using the name 'is_used'.
If the last value in the input_size-part of this column is 1, we select the window, otherwise not.
I am convinced that the implementation of this functionality will greatly increase the capabilities of the library. I will provide you with any information you need to resolve this issue.
Thanks for your hard work. I do not rule out that someday me and my team will be able to join the contributors to your project.
The text was updated successfully, but these errors were encountered:
Were you able to understand the idea described above? I, in fact, completed the implementation locally and, it seems, is ready for the pull request.
ISPritchin
changed the title
Ability to select some specific windows to train by mask (BaseWindows)
Ability to select some specific windows to train / valid / predict by mask (BaseWindows)
Mar 5, 2024
Description
Thanks for a wonderful product. The more I read the source code, the more impressed I am by the quality of this development.
In our problem, the model must be able to predict only some points in the time series that satisfy the conditions. We would like to have a filtering method based on which we could determine whether a given window should be used for training / validation or not.
Use case
I saw that one of the selection mechanisms is
available_mask
, but its use does not completely solve our problem. Masks can be more specific. May be the library already has a solution for my problem, but I couldn't find it.I will give an example of a task where window filtering is required. In the simplest case, let us be given vector
y
. But we would like to be able to make a forecast not for all ('unique_id'
,'ds'
) points, but for those that satisfy some criteria. I mean we have to select some time periods for prediction, which are specific to every individual client. The criterion can filter out a very large number of windows from training. This criterion can be calculated in advance by the user (calculated before training and provided by the user to the model).Suggested solution:
'unique_id'
,'ds'
,'available_mask'
). For the example below I'm using the name'is_used'
.input_size
-part of this column is 1, we select the window, otherwise not.Example:
Currently the following windows would be obtained:
But using the new column we would like to get:
[[3, 4, 5, 6, 7], [5, 6, 7, 8, 9], [6, 7, 8, 9, 10]
The windows were selected because
is_used[input_size - 1]
is 1I am convinced that the implementation of this functionality will greatly increase the capabilities of the library. I will provide you with any information you need to resolve this issue.
Thanks for your hard work. I do not rule out that someday me and my team will be able to join the contributors to your project.
The text was updated successfully, but these errors were encountered: