Skip to content

[BUG] Native networks don't work with generated future equals to horizon #925

Closed
1 task done
Mr-Geekman opened this issue Sep 7, 2022 · 1 comment · Fixed by #936
Closed
1 task done

[BUG] Native networks don't work with generated future equals to horizon #925

Mr-Geekman opened this issue Sep 7, 2022 · 1 comment · Fixed by #936
Assignees
Labels
bug Something isn't working

Comments

@Mr-Geekman
Copy link
Contributor

🐛 Bug Report

If we change at this line future_steps=self.model.decoder_length with future_steps=self.horizon, then tests will fail:

  • test_pipeline_with_deepmodel.

Expected behavior

Tests don't fail.

How To Reproduce

  1. Replace at this line future_steps=self.model.decoder_length with future_steps=self.horizon, then tests will fail.
  2. Run tests for pipeline.

Environment

No response

Additional context

No response

Checklist

  • Bug appears at the latest library version
@Mr-Geekman Mr-Geekman added the bug Something isn't working label Sep 7, 2022
@Mr-Geekman Mr-Geekman changed the title [BUG] New networks don't work with generated future < decoder_length [BUG] New networks don't work with generated future equals to horizon Sep 7, 2022
@Mr-Geekman Mr-Geekman changed the title [BUG] New networks don't work with generated future equals to horizon [BUG] Native networks don't work with generated future equals to horizon Sep 7, 2022
@Mr-Geekman
Copy link
Contributor Author

It seems that the problem is with the line. We have a similar problem with mlp at the line.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant