| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to replace it.
This change prepares `tf.data` for TensorFlow 2.0, where `tf.contrib` will no longer exist. It retains the pre-existing endpoints in `tf.contrib.data` with deprecation warnings.
Note there are some exceptions to the move:
* Deprecated symbols in `tf.contrib.data` have not been moved to `tf.data.experimental`, because replacements already exist.
* `tf.contrib.data.LMDBDataset` has not been moved, because we plan to move it to a SIG-maintained repository.
* `tf.contrib.data.assert_element_shape()` has not yet been moved, because it depends on functionality in `tf.contrib`, and it will move in a later change.
* `tf.contrib.data.AUTOTUNE` has not yet been moved, because we have not yet determined how to `tf_export()` a Python integer.
* The stats-related API endpoints have not yet appeared in a released version of TensorFlow, so these are moved to `tf.data.experimental` without retaining an endpoint in `tf.contrib.data`.
In addition, this change includes some build rule and ApiDef refactoring:
* Some of the "//third_party/tensorflow/python:training" dependencies had to be split in order to avoid a circular dependency.
* The `tf.contrib.stateless` ops now have a private core library for the generated wrappers (and accordingly are hidden in their ApiDef) so that `tf.data.experimental.sample_from_datasets()` can depend on them.
PiperOrigin-RevId: 215304249
|
|
|
|
| |
PiperOrigin-RevId: 214985873
|
|
|
|
| |
PiperOrigin-RevId: 214824023
|
|
|
|
| |
PiperOrigin-RevId: 214495925
|
|
|
|
|
|
|
| |
Besides just general resilience to general user code, another motivation is that it
still makes sense to use the hook when there are no summaries in the graph for the side effect of writing out the graph summary.
PiperOrigin-RevId: 210975165
|
|
|
|
|
|
|
|
| |
self.test_session() has been deprecated in 9962eb5e84b15e309410071b06c2ed2d6148ed44 as its name confuses readers of the test. Moving to cached_session() instead which is more explicit about:
* the fact that the session may be reused.
* the session is not closed even when doing a "with self.test_session()" statement.
PiperOrigin-RevId: 209839032
|
|
|
|
|
|
| |
self.test_session() has been deprecated in cl/208545396 as its behavior confuses readers of the test. Moving to self.session() instead.
PiperOrigin-RevId: 209696110
|
|
|
|
|
|
|
|
|
|
| |
This change contains no code changes. Only doc-strings.
We can't use relative links in code files, so we don't have much choice but to link to tensorflow.org/
The deleted links were to docs that no longer exist.
PiperOrigin-RevId: 209019572
|
|
|
|
| |
PiperOrigin-RevId: 208495685
|
|\
| |
| |
| | |
PiperOrigin-RevId: 208244350
|
| |
| |
| |
| | |
PiperOrigin-RevId: 208126204
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Back-ticks are now converted to links in the api_docs generator. With the new docs repo we're moving to simplify the docs pipeline, and make everything more readable.
By doing this we no longer get test failures for symbols that don't exist (`tf.does_not_exist` will not get a link).
There is also no way, not to set custom link text. That's okay.
This is the result of the following regex replacement (+ a couple of manual edits.):
re: @\{([^$].*?)(\$.+?)?}
sub: `\1`
Which does the following replacements:
"@{tf.symbol}" --> "`tf.symbol`"
"@{tf.symbol$link_text}" --> "`tf.symbol`"
PiperOrigin-RevId: 208042358
|
| |\
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
Pure refactor, in preparation for adding a higher level checkpoint management utility. This utility will also need to work with the Checkpoint proto, and globbing it on to saver.py seems dirty.
PiperOrigin-RevId: 207179646
|
| |
| |
| |
| |
| |
| | |
TowerLocalVariables.
PiperOrigin-RevId: 203520287
|
|/ |
|
|\ |
|
| |
| |
| |
| | |
PiperOrigin-RevId: 201004909
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, we accepted the `padded_shapes` argument without validating that
it was compatible with the `input_dataset.output_shapes`. In many cases, we have
enough static shape information to do this, and so we now raise an actionable
error at the point where the mistake is committed, rather than at runtime.
PiperOrigin-RevId: 199800348
|
|\| |
|
| |
| |
| |
| |
| |
| | |
This is in preparation for removing the _USE_C_API toggle altogether.
PiperOrigin-RevId: 196920481
|
|\| |
|
| |
| |
| |
| |
| |
| |
| | |
"hparams.parse('a.b=1.0')"), which would previously raise an error. This will correspond to an attribute name with an embedded '.' symbol (e.g. 'a.b'), which can only be accessed indirectly (e.g. through getattr and setattr). To set this up the user will first need to explicitly add the variable to the hparam object (e.g. "hparams.add_hparam(name='a.b', value=0.0)").
NOTE: the use of '.' in variable names is now allowed, but it is not recommended.
PiperOrigin-RevId: 196278660
|
|\| |
|
| |
| |
| |
| | |
PiperOrigin-RevId: 194711291
|
| |
| |
| |
| | |
PiperOrigin-RevId: 194031845
|
|\| |
|
|\ \
| | |
| | | |
contrib: minor spelling tweaks
|
| | |
| | |
| | |
| | |
| | |
| | | |
Also its helper method "enqueue_in_queue_dataset".
PiperOrigin-RevId: 193458095
|
| | | |
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 192981122
|
|\ \ \
| | |/
| |/| |
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 192694244
|
| | |
| | |
| | |
| | |
| | |
| | | |
variables.get_or_create_global_step().
PiperOrigin-RevId: 192476077
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 192388250
|
|\| | |
|
| | |
| | |
| | |
| | | |
PiperOrigin-RevId: 192184000
|
| |/
|/|
| |
| |
| |
| |
| | |
packages:
data
training
tensor_forest
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It turns out the error can depend on what sequence comes first in the
input dict. This change internally sorts the input to make the error
predictable (this is useful for this test, as well as any users who
may run into this).
PiperOrigin-RevId: 191449214
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
tf.metrics.accuracy (#18154)
* Replace deprecated tf.contrib.metrics.streaming_accuracy with tf.metrics.accuracy
As tf.contrib.metrics.streaming_accuracy (tf.contrib.metrics.streaming_mean_squared_error) has been deprecated and
has been replaced with tf.metrics.accuracy, this fix
replaces deprecated tf.contrib.metrics.streaming_accuracy with tf.metrics.accuracy
in tensorflow/contrib/training/python/training/evaluation.py.
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Replace streaming_accuracy with tf.metrics.accuracy in tests
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Fix additional WARNING in evaluation_test.py
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
* Fix pylint issue
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
|
| |
| |
| |
| |
| |
| |
| | |
The C API improves static shape inference, making more errors caught
at graph construction time instead of runtime.
PiperOrigin-RevId: 191260634
|
|\| |
|
| |
| |
| |
| | |
PiperOrigin-RevId: 190878279
|
|\| |
|
| |
| |
| |
| |
| |
| | |
https://www.tensorflow.org/api_docs/python/tf/contrib/training/HParams to show that it allows '=' in the values.
PiperOrigin-RevId: 190470578
|
|\| |
|
| | |
|
|\| |
|