merge

doc/advanced/debug_faq.txt

@@ -38,11 +38,12 @@ Theano provides a 'Print' Op to do this.
 Since Theano runs your program in a topological order, you won't have precise
 control over the order in which multiple Print() Ops are evaluted.  For a more
 precise inspection of what's being computed where, when, and how, see the
-:ref:`Stepping through a compiled function with the WrapLinker`.
+:ref:`wraplinker_faq`.
 
 
 
 
+.. _wraplinker_faq:
 
 How do I step through a compiled function with the WrapLinker?
 --------------------------------------------------------------
@@ -50,10 +51,11 @@ How do I step through a compiled function with the WrapLinker?
 WRITEME
 
 
-I wrote a new Op, and weird stuff is happening...
--------------------------------------------------
+I wrote a new Op/Type, and weird stuff is happening...
+------------------------------------------------------
 
-First, check the :ref:`Op Contract` and make sure you're following the rules.
+First, check the :ref:`op_contract` and the :ref:`type_contract` 
+and make sure you're following the rules.
 Then try running your program in :ref:`debugmode`.  DebugMode might catch
 something that you're not seeing.
 

doc/advanced/debugmode.txt

@@ -18,7 +18,7 @@ cluster.
 
 DebugMode is easy to use:
 
-.. code-block::
+.. code-block:: python
 
     x = theano.dvector('x')
 

doc/advanced_tutorial/ex1/op.txt

@@ -7,6 +7,8 @@ Now that we have a ``double`` type, we have yet to use it to perform
 computations. We'll start by defining multiplication.
 
 
+.. _op_contract:
+
 Op's contract
 =============
 

doc/advanced_tutorial/ex1/type.txt

@@ -5,6 +5,8 @@ Making the double type
 ======================
 
 
+.. _type_contract:
+
 Type's contract
 ===============
 

theano/compile/debugmode.py

@@ -1152,6 +1152,28 @@ class DebugMode(Mode):
     `_VariableEquivalenceTracker` classes.
 
     """
+
+    stability_patience = 10
+    """
+    When checking for the stability of optimization, recompile the graph this many times.
+    """
+
+    check_c_code = True
+    """
+    Should we evaluate (and check) the `c_code` implementations?
+    """
+
+    check_py_code = True
+    """
+    Should we evaluate (and check) the `perform` implementations?
+    """
+
+    diagnostic = None
+    """
+    Log diagnostic information to this file.
+    """
+
+
     # This function will be used to create a FunctionMaker in 
     # function_module.function
     def function_maker(self, i,o,m, *args, **kwargs):