edit notebook

Signed-off-by: Vinh Nguyen <[email protected]>

Author: vinhngx

Dockerfile.notebook

@@ -18,4 +18,4 @@ RUN bazel build //:libtrtorch --compilation_mode opt
 WORKDIR /workspace/TRTorch/py
 RUN python3 setup.py install
 
-
+WORKDIR /workspace/TRTorch/notebooks

notebooks/LeNet-example.ipynb

@@ -232,7 +232,11 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "### Tracing"
+    "When compiling your module to TorchScript, there are two paths: Tracing and Scripting.  \n",
+    " \n",
+    "### Tracing\n",
+    "\n",
+    "Tracing follows the path of execution when the module is called and records what happens. This recording is what the TorchScript IR will describe. To trace an instance of our LeNet module, we can call torch.jit.trace  with an example input. "
    ]
   },
   {
@@ -300,7 +304,9 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "### Scripting"
+    "### Scripting\n",
+    "\n",
+    "Scripting actually inspects your code with a compiler and  generates an equivalent TorchScript program. The difference is that since tracing simply follows the execution of your module, it cannot pick up control flow for instance, it will only follow the code path that a particular input triggers. By working from the Python code, the compiler can include these components. We can run the script compiler on our LeNet  module by calling torch.jit.script.\n"
    ]
   },
   {