1
0
Fork 0
mirror of https://github.com/tensorflow/haskell.git synced 2024-12-24 02:29:46 +01:00
tensorflow-haskell/tensorflow-mnist
Judah Jacobson d62c614695 Distinguish between "rendered" and "unrendered" Tensors. (#88)
Distinguish between "rendered" and "unrendered" Tensors.

There are now three types of `Tensor`:

- `Tensor Value a`: rendered value
- `Tensor Ref a`: rendered reference
- `Tensor Build a` : unrendered value

The extra bookkeeping makes it easier to track (and enforce) which tensors are
rendered or not.  For examples where this has been confusing in the past, see

With this change, pure ops look similar to before, returning `Tensor Build`
instead of `Tensor Value`.  "Stateful" (monadic) ops are unchanged.  For
example:

    add :: OneOf [..] t => Tensor v'1 t -> Tensor v'2 t -> Tensor Build t
    assign :: (MonadBuild m, TensorType t)
           => Tensor Ref t -> Tensor v'2 t -> m (Tensor Ref t)

The `gradients` function now requires that the variables over which it's
differentiating are pre-rendered:

    gradients :: (..., Rendered v2) => Tensor v1 a -> [Tensor v2 a]
              -> m [Tensor Value a]

(`Rendered v2` means that `v2` is either a `Ref` or a `Value`.)

Additionally, the implementation of `gradients` now takes care to render every
intermediate value when performing the reverse accumulation.  I suspect this
fixes an exponential blowup for complicated expressions.
2017-04-06 15:10:33 -07:00
..
app Distinguish between "rendered" and "unrendered" Tensors. (#88) 2017-04-06 15:10:33 -07:00
data Initial commit 2016-10-24 19:26:42 +00:00
src/TensorFlow/Examples/MNIST Initial commit 2016-10-24 19:26:42 +00:00
src-data/TensorFlow/Examples/MNIST Initial commit 2016-10-24 19:26:42 +00:00
tests Distinguish between "rendered" and "unrendered" Tensors. (#88) 2017-04-06 15:10:33 -07:00
Setup.hs Initial commit 2016-10-24 19:26:42 +00:00
tensorflow-mnist.cabal Initial commit 2016-10-24 19:26:42 +00:00