Merge branch 'master' into master

Author: brianjo

.jenkins/build.sh

@@ -15,6 +15,9 @@ export PATH=/opt/conda/bin:$PATH
 rm -rf src
 pip install -r $DIR/../requirements.txt
 
+# For Tensorboard. Until 1.14 moves to the release channel.
+pip install tb-nightly  
+
 export PATH=/opt/conda/bin:$PATH
 pip install sphinx==1.8.2 pandas
 
@@ -30,10 +33,16 @@ pip install -e git+git://github.com/pytorch/pytorch_sphinx_theme.git#egg=pytorch
 pip install sphinx-gallery==0.3.1 tqdm matplotlib ipython pillow==4.1.1
 
 # Install torchaudio from source
-# git clone https://github.com/pytorch/audio --quiet
-# pushd audio
-# python setup.py install
-# popd
+git clone https://github.com/pytorch/audio --quiet
+pushd audio
+python setup.py install
+popd
+
+# Install torchaudio from source
+git clone https://github.com/pytorch/text --quiet
+pushd text
+python setup.py install
+popd
 
 aws configure set default.s3.multipart_threshold 5120MB
 
@@ -185,4 +194,4 @@ else
 fi
 
 rm -rf vision
-# rm -rf audio
+rm -rf audio

_static/imagenet_class_index.json

@@ -13,6 +13,6 @@ Advanced Tutorials
 	Custom C Extensions for PyTorch
 	https://pytorch.org/tutorials/advanced/c_extension.html
 
-4. super_resolution_with_caffe2.py
-	Transfering a Model from PyTorch to Caffe2 and Mobile using ONNX
-	https://pytorch.org/tutorials/advanced/super_resolution_with_caffe2.html
+4. super_resolution_with_onnxruntime.py
+    Exporting a Model from PyTorch to ONNX and Running it using ONNXRuntime
+	https://pytorch.org/tutorials/advanced/super_resolution_with_onnxruntime.html

_static/img/cat_output1.png

@@ -147,23 +147,22 @@ For the "ahead of time" flavor, we build our C++ extension by writing a
 ``setup.py`` script that uses setuptools to compile our C++ code. For the LLTM, it
 looks as simple as this::
 
-  from setuptools import setup
-  from torch.utils.cpp_extension import CppExtension, BuildExtension
+  from setuptools import setup, Extension
+  from torch.utils import cpp_extension
 
   setup(name='lltm_cpp',
-        ext_modules=[CppExtension('lltm', ['lltm.cpp'])],
-        cmdclass={'build_ext': BuildExtension})
-
+        ext_modules=[cpp_extension.CppExtension('lltm_cpp', ['lltm.cpp'])],
+        cmdclass={'build_ext': cpp_extension.BuildExtension})
 
 In this code, :class:`CppExtension` is a convenience wrapper around
 :class:`setuptools.Extension` that passes the correct include paths and sets
 the language of the extension to C++. The equivalent vanilla :mod:`setuptools`
 code would simply be::
 
-  setuptools.Extension(
+  Extension(
      name='lltm_cpp',
      sources=['lltm.cpp'],
-     include_dirs=torch.utils.cpp_extension.include_paths(),
+     include_dirs=cpp_extension.include_paths(),
      language='c++')
 
 :class:`BuildExtension` performs a number of required configuration steps and
@@ -413,7 +412,7 @@ see::
 If we call ``help()`` on the function or module, we can see that its signature
 matches our C++ code::
 
-  In[4] help(lltm.forward)
+  In[4] help(lltm_cpp.forward)
   forward(...) method of builtins.PyCapsule instance
       forward(arg0: torch::Tensor, arg1: torch::Tensor, arg2: torch::Tensor, arg3: torch::Tensor, arg4: torch::Tensor) -> List[torch::Tensor]
 
@@ -473,6 +472,8 @@ small benchmark to see how much performance we gained from rewriting our op in
 C++. We'll run the LLTM forwards and backwards a few times and measure the
 duration::
 
+  import time
+
   import torch
 
   batch_size = 16