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

Cannot reproduce README.md graphs/results on copy task [Commit: 5c5ce66] #2

Closed
jagleeso opened this issue Mar 15, 2018 · 1 comment
Closed
Assignees

Comments

@jagleeso
Copy link

Hello,

I'm just trying to reproduce the results/graphs shown in the README.md for the "copy" task.

I am running this on the latest master branch:
Commit 5c5ce66376e8032c38ef4327ca381fee145f4d0f

How I trained my model:

./train.py --seed 1000 --task copy --checkpoint_interval 500 --checkpoint-path ./notebooks/copy -pbatch_size=15

NOTE: I used a batch_size of 15 instead of the default of 1, since it seems to lead to more stable convergence rates.

I then used the python notebook to generate 3 graphs shown in the README.md.
For convenience when comparing, I've included both the graphs I got, and the graph I expect (taken from the README.md).

Graph 1: Training convergence

I got:
image
I expect:
image

Graph 2: Training convergence (per sequence length)

I got:
image
I expect:
image

Graph 3: Evaluate

I got:
image

(The expected graph being that Outputs matches the Targets)

Setup information

My setup is:

  • OS: Ubuntu 16.04.4 LTS
  • Python version: 3.6.4
  • PyTorch is installed using Anaconda, pip freeze reports the version as:
    torch==0.3.0.post4
  • CUDA/cuDNN versions/libraries in use by pytorch at runtime:
/usr/lib/x86_64-linux-gnu/libcuda.so.384.111
/usr/local/cuda-9.0/lib64/libcublas.so.9.0.176
/usr/local/cuda-9.0/lib64/libcudart.so.9.0.176
/usr/local/cuda-9.0/lib64/libcudnn.so.7.0.5
/usr/local/cuda-9.0/lib64/libcurand.so.9.0.176
/usr/local/cuda-9.0/lib64/libcusparse.so.9.0.176
/usr/local/cuda-9.0/lib64/libnvrtc.so.9.0.176
/usr/local/cuda-9.0/lib64/libnvToolsExt.so.1.0.0

Let me know if there is any other information I can provide.

@loudinthecloud
Copy link
Owner

Thanks for reporting it @jagleeso, the same issue was reported to me earlier this week and the fix was to use earlier commit d8fedf6 for now which seemed to work. I plan to fix it in the coming days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants