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

 ##########
 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 
 
 Review comment:
   populate files for data and labels with _fewer_ number of labels...

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

Reply via email to