Replies: 2 comments
-
could you add full code with imports? Feel free to use dummy data if you cannot share your actual data (this is preferred in any case, since then we can copy-paste code). |
Beta Was this translation helpful? Give feedback.
0 replies
-
I found the issue :), somehow I had hardcoded min_encoding_length to half of the max encoding. putting both the same the output from index is as expected, starting from 8 and ending without duplicates. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to use the library but I have an issue on how to handle the output from a model prediction, the index shows time_idx starting from 36 and repeating the last values at the last time_idx (encoding_length 72 and prediction_length is 1). If I change the enconding_length half of it goes as start point and the other with repeating values at the end. I can share the full code but it is few thousands lines mostly to handle a yaml interface to define the features targets etc, I can share logs otherwise, so tell me what you think is best. I am not familiar with the library so it could be something in the tsds that is set not properly (I can share the output of these). but the prog is running a training, saving the model and the tsds then running a prediction from the saved model and tsds. what I saw i that after reloading the tsds it is not exactly as the original, it shows this which it was not set for the training:
this is the output from the index after the predict (encoding length 8, prediction length 1):
all came out as I am trying to mapping back the datetime to the predicted output.
Beta Was this translation helpful? Give feedback.
All reactions