| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
Change: 138531687
|
|
|
|
|
| |
when experimenting with quantized graphs.
Change: 138529416
|
|
|
|
| |
Change: 138529294
|
|
|
|
| |
Change: 138526951
|
|
|
|
| |
Change: 138518927
|
|
|
|
|
| |
This fixes a failure where a non-function is used as a metric, fails, but raises an exception during error logging, hiding the real exception.
Change: 138488393
|
|
|
|
| |
Change: 138483426
|
|
|
|
| |
Change: 138481437
|
|
|
|
| |
Change: 138478269
|
|
|
|
|
| |
Also introduces a scaffold in tf.contrib.training for load-balanced placement strategies
Change: 138476980
|
|
|
|
|
|
| |
download/extract step is unnecessary.
Change: 138475677
|
|
|
|
| |
Change: 138473617
|
|
|
|
|
|
| |
which can do cleanups such as closing gRPC streams
Change: 138472618
|
|
|
|
|
| |
This uncovered a silly bug during idx calculation in the gradient checker which is fixed in this CL.
Change: 138471470
|
|
|
|
| |
Change: 138471362
|
|
|
|
|
| |
edge of the unit cube and points on the cube were getting clipped.
Change: 138470802
|
|
|
|
| |
Change: 138467240
|
|
|
|
| |
Change: 138466309
|
|
|
|
|
| |
Also added a few more array ops.
Change: 138456760
|
|
|
|
| |
Change: 138456486
|
|
|
|
| |
Change: 138455935
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is one step towards having a stable C API by the time we get to TensorFlow
1.0. A follow-up step will involve renaming TF_SessionWithGraph to TF_Session.
We want to encourage all client languages to use TF_SessionRun,
TF_GraphImportGraphDef etc. (instead of TF_Run and TF_ExtendGraph), hence
the choice of names. Ideally, all client languages will use these
functions, but it is likely that Python will continue to use
TF_DeprecatedSession for a while.
Change: 138454433
|
|
|
|
|
|
|
|
|
|
| |
* Rewrite CPU impl to be single-threaded and use vectorization; avoids race conditions. Removes use of the generator.
* Remove scatter_nd_mul and scatter_nd_div to reduce binary size until
we figure out a better way to reduce the templating pain
* Modify scatter_nd to add for repeated indices as opposed to update
(this is the appropriate gradient for gather_nd, for example)
* Clean up docstrings.
Change: 138452341
|
|
|
|
| |
Change: 138451572
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Float32Array of data point positions, and passes it into onPointPositionsChanged. Overhaul the visualizer interface, change 'onRecreateScene' to 'setScene', change 'removeAll' to 'dispose', change 'onUpdate' to 'onPointPositionsChanged', delete 'onDataSetChanged' entirely.
Remove 'sceneIs3D' and 'backgroundColor' from onRecreateScene, they never really belonged there. The scene is /always/ 3D, the visualizers are really interested in the camera projection method, so now they query that. backgroundColor moved into the RenderContext, where it probably always belonged.
Sprite visualizer now observes new point arrays and creates the WebGL representation only if one doesn't already exist, or its buffers are too small to hold the current point array.
ScatterPlot directly uses THREE.AxesHelper, delete scatterPlotVisualizerAxes. (we might add it back later when scatter plot becomes more of a general-purpose reusable component, but it will need lots of work anyway).
Add 'util.vector3FromPackedArray', which loads array[i], array[i+1], array[i+2] into a THREE.Vector3 and replaces 'util.getProjectedPointFromIndex'.
Projector no longer automatically renders the scatter plot when the positions / attributes change.
Break the trace visualizer's dependency on the selection context, it was causing problems when dataset filtering was being canceled. Add various Float32Array buffers for opacity and line width, generate them in the scatter plot adapter, and pass them into the render context with the rest of the 'attribute' data.
When switching between sprites + labels mode, always add the trace visualizer.
Change: 138426641
|
|
|
|
| |
Change: 138425944
|
|
|
|
|
| |
between TF and Eigen). Add tests covering the unequal stride case.
Change: 138421428
|
|
|
|
|
|
| |
mouse cursor.
Change: 138418340
|
|
|
|
|
|
|
| |
The embedding projector plugin caches the checkpoint reader, which is pointing to the latest checkpoint when TensorBoard was started. But after some time, the saver will remove that old checkpoint file (keeps only N latest checkpoints), while the reader is still pointing to it.
Also add more tests regarding the V1 and V2 checkpoint versions.
Change: 138416977
|
|
|
|
| |
Change: 138409704
|
|
|
|
| |
Change: 138409090
|
|
|
|
|
| |
Address a few pylint warnings.
Change: 138407267
|
|
|
|
|
|
| |
or out degree (depending on whether the bridge path is in or out bound) above 4. This prevents too many bridge paths from emanating out of a subhierarchy (metagraph) and crowding up.
Change: 138403730
|
|
|
|
|
| |
0 (index of the first point) evaluates to false in JS, which resulted in the false conclusion that there was no selection
Change: 138387835
|
|
|
|
| |
Change: 138337381
|
|
|
|
| |
Change: 138332522
|
|
|
|
| |
Change: 138332031
|
|
|
|
|
|
| |
Aims to address recently flakiness in the tutorial test. See example failure log at:
http://ci.tensorflow.org/view/Nightly/job/nightly-matrix-cpu/TF_BUILD_IS_OPT=OPT,TF_BUILD_IS_PIP=PIP,TF_BUILD_PYTHON_VERSION=PYTHON3,label=mac-slave/281/console
Change: 138300959
|
|
|
|
|
|
|
| |
localhost_cluster_performance_test and
sync_replicas_optimizer_test.
Change: 138253057
|
|
|
|
|
|
| |
memory allocator returns same addresses for graph objects when the graph mgr is being used repeatedly.
Change: 138251588
|
|
|
|
| |
Change: 138246915
|
|
|
|
| |
Change: 138240000
|
|
|
|
|
|
| |
in CameraActivity.
Change: 138238290
|
|
|
|
| |
Change: 138238179
|
|
|
|
| |
Change: 138237011
|
|
|
|
| |
Change: 138233065
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Three bug fixes:
(1) There was a thread-unsafe access to runs_ which could result in the
queue close operation being invoked multiple times.
(2) The Run() loop would not exit when there were multiple threads
and the queue was closed (i.e., the enqueue failed with a
queue_closed_exception_types_ error).
Without this fix, the changed QueueRunnerTest.QueueCloseCode
test would fail with a timeout since qr->Join() would be blocked
on the never-exiting Run() call
(3) Errors in invoking the close operation were being ignored.
Without this fix, the added QueueRunnerTest.QueueCloseFails
test would fail as Join() would return OK instead of NOT_FOUND
Two other minor changes:
- Slight simplification to QueueRunner::Run() so that
runs_ is manipulated only once and the body of the loop
is clearer
- Avoid starting an extra thread which will not be used
when there is no Coordinator. (Though in practice I
suppose we always intend to have a coordinator).
Change: 138228243
|
|
|
|
|
|
|
|
|
|
|
| |
Also done separately by @llhe at github.com/tensorflow/tensorflow/pull/5370. We needed to do this change internally to fix all callers.
Motivation: The existing FileExists interface doesn't allow callers to distinguish between file not found vs. filesystem errors.
Semantics changes:
- gfile.Exists in Python now throws an exception for filesystem errors. It continues to return true/false if it can accurately determine whether a file exists.
- RecursivelyCreateDir now returns errors for filesystem errors when calling FileExists.
Change: 138224013
|
|
|
|
| |
Change: 138215748
|
|
|
|
| |
Change: 138215608
|