Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

example/rnn: Batch size must not cause errors in test #140

Open
drahnr opened this issue Apr 18, 2021 · 1 comment
Open

example/rnn: Batch size must not cause errors in test #140

drahnr opened this issue Apr 18, 2021 · 1 comment
Assignees
Labels
bug Something doesn't quite look right day-1 Issues encountered early on using juice

Comments

@drahnr
Copy link
Member

drahnr commented Apr 18, 2021

Describe the bug

Currently the rnn mackey glass example under ./juice-examples does not work, if train and test are run with different --batch-size arguments.

To Reproduce

Steps to reproduce the behaviour:

  1. Setting up preconditions with ...
  2. Run cargo +stable run -p example-rnn-regression --features cuda,native -- train --batch-size=23 foo.capnp
  3. Execute cargo +stable run -p example-rnn-regression --features cuda,native -- test --batch-size=1 foo.capnp

Expected behavior

batch_size must not influence success or failure in a sane range.

Please complete the following information:

  • System: Fedora 33 / Windows x64
  • Version: *
  • Rust: rustc 1.51.0 (2fd73fabe 2021-03-23)
  • Environment: CI env
  • Backends (if relevant):
    • opencl: CI env
    • cuda: CI env

Additional context

@drahnr drahnr added bug Something doesn't quite look right day-1 Issues encountered early on using juice labels Apr 18, 2021
@drahnr
Copy link
Member Author

drahnr commented Apr 19, 2021

As @lissahyacinth pointed out in direct comms, it's not related to RNN but to the Reshape layer which serializes all dimensions into the .capnp file, which in turn is restored for test runs of the example - which might have a different batch dimension size compared to the train run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something doesn't quite look right day-1 Issues encountered early on using juice
Projects
None yet
Development

No branches or pull requests

2 participants