Theano 0.4.1rc1

Optimizing compiler for evaluating mathematical expressions on CPUs and GPUs.

Theano is a Python library that allows you to define, optimize, and efficiently evaluate mathematical expressions involving multi-dimensional arrays. It is built on top of NumPy. Theano features:

• tight integration with NumPy: a similar interface to NumPy’s. numpy.ndarrays are also used internally in Theano-compiled functions.

• transparent use of a GPU: perform data-intensive computations up to 140x faster than on a CPU (support for float32 only).

• efficient symbolic differentiation: Theano can compute derivatives for functions of one or many inputs.

• speed and stability optimizations: avoid nasty bugs when computing expressions such as log(1+ exp(x) ) for large values of x.

• dynamic C code generation: evaluate expressions faster.

• extensive unit-testing and self-verification: includes tools for detecting and diagnosing bugs and/or potential problems.

Theano has been powering large-scale computationally intensive scientific research since 2007, but it is also approachable enough to be used in the classroom (IFT6266 at the University of Montreal).

Modifications in the 0.4.1 release candidate 1(28 July 2011)

Deprecation:

• The string mode (accepted only by theano.function()) FAST_RUN_NOGC. Use Mode(linker=’c|py_nogc’) instead.

• The string mode (accepted only by theano.function()) STABILIZE. Use Mode(optimizer=’stabilize’) instead.

• Scan interface change…RP what are these changes? I think you deprecated AND removed them… TODO

Bugs fixed:

• In one case an AdvancedSubtensor1 could be converted to a GpuAdvancedIncSubtensor1 insted of GpuAdvancedSubtensor1. It probably didn’t happen due to the order of optimizations, but that order is not guaranteed to be the same on all computers.

• Derivative of set_subtensor was wrong.

• Derivative of Alloc was wrong.

Crash fixed:

• On an unusual Python 2.4.4 on Windows

• When using a C cache copied from another location

• On Windows 32 bits when setting a complex64 to 0.

• Compilation crash with CUDA 4

• When wanting to copy the compilation cache from a computer to another * This can be useful for using Theano on a computer without a compiler.

GPU:

• Compilation crash fixed under Ubuntu 11.04

• Compilation crash fixed with CUDA 4.0

• PyCUDA/Theano bridge and documentation. * New function to easily convert pycuda GPUArray object to and from CudaNdarray object * Fixed a bug if you crated a view of a manually created CudaNdarray that are view of GPUArray.

• Removed a warning when nvcc is not available and the user did not requested it.

• renamed config option cuda.nvccflags -> nvcc.flags

New features:

• R_op macro like theano.tensor.grad * Not all tests are done yet (TODO)

• Added alias theano.tensor.bitwise_{and,or,xor,not}. They are the numpy names.

• Updates returned by Scan (you need to pass them to the theano.function) are now a new Updates class. That allow more check and easier work with them. The Updates class is a subclass of dict

• Scan can now work in a “do while” loop style. * We scan until a condition is met. * There is a minimum of 1 iteration(can’t do “while do” style loop)

• The “Interactive Debugger” (compute_test_value theano flags) * Now should work with all ops (even the one with only C code) * In the past some errors were caught and re-raised as unrelated errors (ShapeMismatch replaced with NotImplemented). We don’t do that anymore.

• The new Op.make_thunk function(introduced in 0.4.0) is now used by constant_folding and DebugMode

• Added A_TENSOR_VARIABLE.astype() as a way to cast. NumPy allows this syntax.

• New BLAS GER implementation.

• Insert GEMV more frequently.

• Added new ifelse(scalar condition, rval_if_true, rval_if_false) Op. * This is a subset of the elemwise switch (tensor condition, rval_if_true, rval_if_false). * With the new feature in the sandbox, only one of rval_if_true or rval_if_false will be evaluated.

Optimizations:

• Subtensor has C code

• {Inc,Set}Subtensor has C code

• ScalarFromTensor has C code

• dot(zeros,x) and dot(x,zeros)

• IncSubtensor(x, zeros, idx) -> x

• SetSubtensor(x, x[idx], idx) -> x (when x is a constant)

• subtensor(alloc,…) -> alloc

• Many new scan optimization (TODO, list them)

• Lower scan execution overhead with a Cython implementation

• Removed scan double compilation (by using the new Op.make_thunk mechanism)

Sandbox:

• MRG random generator now implements the same casting behavior as the regular random generator.

Sandbox New features(not enabled by default):

• New Linkers (theano flags linker={vm,cvm}) * The new linker allows lazy evaluation of the new ifelse op, meaning we compute only the true or false branch depending of the condition. This can speed up some types of computation. * Uses a new profiling system (that currently tracks less stuff) * The cvm is implemented in C, so it lowers Theano’s overhead. * The vm is implemented in python. So it can help debugging in some cases. * In the future, the default will be the cvm.

• Some new not yet well tested sparse ops: theano.sparse.sandbox.{SpSum, Diag, SquareDiagonal, ColScaleCSC, RowScaleCSC, Remove0, EnsureSortedIndices, ConvolutionIndices}

Documentation:

• How to compute the Jacobian, Hessian, Jacobian times a vector, Hessian times a vector.

• Slide for a 3 hours class with exercises that was done at the HPCS2011 Conference in Montreal.

Others:

• Logger name renamed to be consistent.

• Logger function simplified and made more consistent.

• Fixed transformation of error by other not related error with the compute_test_value Theano flag.

• Compilation cache enhancements.

• Made compatible with NumPy 1.6 and SciPy 0.9

• Fix tests when there was new dtype in NumPy that is not supported by Theano.

• Fixed some tests when SciPy is not available.

• Don’t compile anything when Theano is imported. Compile support code when we compile the first C code.

• Python 2.4 fix: * Fix the file theano/misc/check_blas.py * For python 2.4.4 on Windows, replaced float(“inf”) with numpy.inf.

Core:

• there is a new mechanism that lets an Op permit that one of its inputs to be aliased to another destroyed input. This will generally result in incorrect calculation, so it should be used with care! The right way to use it is when the caller can guarantee that even if these two inputs look aliased, they actually will never overlap. This mechanism can be used, for example, by a new alternative approach to implementing Scan. If an op has an attribute called “destroyhandler_tolerate_aliased” then this is what’s going on. IncSubtensor is thus far the only Op to use this mechanism.Mechanism