rahul003 commented on a change in pull request #9869: Exception handling 
documentation
URL: https://github.com/apache/incubator-mxnet/pull/9869#discussion_r170736736
 
 

 ##########
 File path: docs/tutorials/basic/exception_handling.md
 ##########
 @@ -0,0 +1,111 @@
+# Exception Handling in MXNet
+
+This tutorial explains the exception handling support in MXNet, 
+and provides examples on how to throw and handle exceptions when in a 
multithreaded context.
+Although, the examples are in Python, they can be easily extended to MXNet
+language bindings.
+
+MXNet exceptions can be thrown from two areas:
+- MXNet main thread. For eg. Infershape and InferType.
+- Spawned threads:
+    * By dependency engine for operator execution in parallel
+    * By the iterators, during the data loading, text parsing phase etc.
+
+In the first case, the exception is thrown and can be handled in the main 
thread.
+In the second case, the exception is thrown in a spawned thread, caught and 
transported to the
+main thread, where it is rethrown. This tutorial will give more explanation 
and examples on how 
+to handle exceptions for the second case.
+
+## Prerequisites 
+
+To complete this tutorial, we need:
+- MXNet 
[7b24137](https://github.com/apache/incubator-mxnet/commit/7b24137ed45df605defa4ce72ec91554f6e445f0).
 See Instructions in [Setup and 
Installation](http://mxnet.io/install/index.html).
+
+## Exception Handling for Iterators
+
+The below example shows how to handle exceptions for iterators. In this 
example, 
+we populate a data and a labels file with lesser number of labels compared to 
the 
+number of samples. This should throw an exception. 
+
+The CSVIter uses the PrefetcherIter for loading and parsing data. 
+The PrefetcherIter spawns a producer thread in the background which prefetches
+the data while the main thread consumes the data. The exception is thrown in 
the spawned
+producer thread during the prefetching, when the label is not found 
corresponding to a specific sample. 
+
+The exception is transported to the main thread, where it is rethrown when 
Next is 
+called as part of the following line: `for batch in iter(data_train)`.
+
+In general, Exception may be rethrown as part of `Next` and `BeforeFirst` 
calls which correspond to `reset()` and `next()` methods in `MXDataIter` for 
Python language bindings.
+
+```python
+import os
+import mxnet as mx
+
+cwd = os.getcwd()
+data_path = os.path.join(cwd, "data.csv")
+label_path = os.path.join(cwd, "label.csv")
+
+with open(data_path, "w") as fout:
+    for i in range(8):
+        fout.write("1,2,3,4,5,6,7,8,9,10\n")
+
+with open(label_path, "w") as fout:
+    for i in range(7):
+        fout.write("label"+str(i))
+
+try:
+    data_train = mx.io.CSVIter(data_csv=data_path, label_csv=label_path, 
data_shape=(1, 10),
+                               batch_size=4)
+
+    for batch in iter(data_train):
+        print(data_train.getdata().asnumpy())
+except mx.base.MXNetError as ex:
+    print("Exception handled")
+    print(ex)
+```
+
+### Limitation
+
+There is a race condition when your last `next()` call doesnt reach the batch 
in your dataset where exception occurs. Exception may or may not be thrown in 
this case depending on which thread wins the race. To avoid this situation, you 
should try and iterate through your full dataset if you think it can throw 
exceptions which need to be handled.
+
+
+## Exception Handling for Operators
+
+The below example shows how to handle exceptions for operators in the 
imperative mode.
+
+For the operator case, the dependency engine spawns a number of threads if it 
is running in the `ThreadedEnginePool` or `ThreadedEnginePerDevice` mode. The 
final operator is executed in one of the spawned threads. 
+
+If an operator throws an exception during execution, this exception is 
propagated
+down the dependency chain. Once there is a synchronizing call i.e. WaitToRead 
for a variable, in the dependency chain, the propagated exception is rethrown. 
+
+In the below example, I illustrate how an exception that occured in the first 
line is propagated down the dependency chain, and finally is rethrown when we 
make a synchronizing call to WaitToRead.
+
+```python
+import mxnet as mx
+a = mx.nd.random.normal(0, 1, (2, 2))
+b = mx.nd.random.normal(0, 2, (2, 2))
+c = mx.nd.dot(a, b)
+d = mx.nd.random.normal(0, -1, (2, 2))
+e = mx.nd.dot(c, d)
+e.wait_to_read()
+```
+
+Although, the above exception occurs when executing the operation which writes 
to the variable d in one of the child threads, it surfaces only when the 
synchronizing `wait_to_read`.
 
 Review comment:
   remove comma after although
   variable `d`
   rephrase 'when the synchronizing `wait_to_read'

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to