| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
than object.
variables_to_restore ensured that duplicate variables weren't added to the return map by comparing python variable object. Normally there is only one Variable object for each underlying variable, so this wasn't a problem. But when one initializes a graph by importing a GraphDef, duplicate python Variable objects are created for each occurrence of a variable in a collection (say, global variables and moving average variables).
This change fixes variables_to_restore to work with an imported graph def by not comparing Variable objects.
PiperOrigin-RevId: 174861804
|
|
|
|
|
|
| |
Uses Eigen's unsupported implementation.
PiperOrigin-RevId: 174858966
|
|
|
|
| |
PiperOrigin-RevId: 174846842
|
|
|
|
|
|
|
|
|
|
|
| |
After this change we can specify a list of parameters to it and if we
specify enough then it will do the computation.
The primary goal of this change is to make the HloEvaluator usable
with ComputationBuilder from tests through ComputeConstant in cases
where the input is a parameter (fed by a literal).
PiperOrigin-RevId: 174845108
|
|
|
|
| |
PiperOrigin-RevId: 174814136
|
|
|
|
| |
PiperOrigin-RevId: 174813300
|
|
|
|
|
|
|
|
|
|
| |
These tests permute the tuple elements of a 3-tuple in each iteration in the following cyclic manner (132), i.e. a shift to the left.
The first test just return the result tuple, the second returns the sum of all tuple elements (which is expected to be constant 6, no matter which permutation)
Both tests are disabled for now because they fail on all back-ends.
PiperOrigin-RevId: 174806092
|
|
|
|
| |
PiperOrigin-RevId: 174799735
|
|
|
|
|
|
| |
Keras 2.0.9.
PiperOrigin-RevId: 174796893
|
|
|
|
| |
PiperOrigin-RevId: 174796480
|
|
|
|
| |
PiperOrigin-RevId: 174795864
|
|
|
|
| |
PiperOrigin-RevId: 174788331
|
|
|
|
| |
PiperOrigin-RevId: 174787397
|
|
|
|
| |
PiperOrigin-RevId: 174787363
|
|
|
|
|
|
|
|
|
| |
element_shape is given.
This allows one to write to only some indices of a TensorArray before calling stack.
Elements that were not written to are treated as all zero tensors.
PiperOrigin-RevId: 174783569
|
|
|
|
|
|
|
|
|
| |
a proto.
This makes the buffer assignment's proto dump deterministic.
RELNOTES: BufferAssignment's protocol buffer dump is now deterministic.
PiperOrigin-RevId: 174783549
|
|
|
|
| |
PiperOrigin-RevId: 174781987
|
|
|
|
|
|
| |
was used during the checkpoint creation (as is allowed in FeatureColumn._VocabularyListCategoricalColumn).
PiperOrigin-RevId: 174781749
|
|
|
|
|
|
| |
This fixes #14243.
PiperOrigin-RevId: 174772870
|
|
|
|
|
|
| |
directly addressable from tf.contrib.data.
PiperOrigin-RevId: 174771870
|
|
|
|
| |
PiperOrigin-RevId: 174770787
|
|
|
|
| |
PiperOrigin-RevId: 174770444
|
|
|
|
|
|
| |
In ASBSQueue::Schedule, when a new batch is created, it was added to the scheduler outside of the queue's lock. This was done to prevent any unforeseen interactions between the queue lock and scheduler lock. However, this wasn't being done in a thread safe way.
PiperOrigin-RevId: 174769383
|
|
|
|
| |
PiperOrigin-RevId: 174769308
|
|
|
|
|
|
|
|
| |
It was creating reference cycles.
Adds a test that TensorArrays create no reference cycles in eager mode.
PiperOrigin-RevId: 174768765
|
|
|
|
| |
PiperOrigin-RevId: 174768741
|
|
|
|
| |
PiperOrigin-RevId: 174767565
|
|
|
|
| |
PiperOrigin-RevId: 174765540
|
|
|
|
|
|
| |
to use of constant_op.constant(..., shape=p.shape), where sometimes p was a Tensor of unknown shape.
PiperOrigin-RevId: 174764744
|
|
|
|
|
|
| |
Fold ConjugateTranspose in BatchMatmul.
PiperOrigin-RevId: 174750173
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previous tf.flags implementation is based on argparse. It contains -h/--help flags, which displays all flags.
absl.app's --help flag only displays flags defined in the main module. There is a --helpfull flag that displays all flags.
So added --helpshort --helpfull flags.
app.run now raises SystemError on unknown flags (fixes #11195).
Accessing flags before flags are parsed will now raise an UnparsedFlagAccessError, instead of causing implicit flag parsing previously.
PiperOrigin-RevId: 174747028
|
|
|
|
| |
PiperOrigin-RevId: 174745329
|
|
|
|
| |
PiperOrigin-RevId: 174735029
|
|
|
|
| |
PiperOrigin-RevId: 174734277
|
|
|
|
| |
PiperOrigin-RevId: 174733491
|
|
|
|
|
|
|
| |
ResourceVariables enter graph mode to get a handle. We should probably revisit
that, but in the meantime we can break the resulting reference cycles.
PiperOrigin-RevId: 174732964
|
|
|
|
|
|
|
| |
o. move input pipeline analyzer related proto for grpc between red and green VMs
o. rename perftools.gputools.profiler.collector::TfStatsHelperResult to tensorflow::tpu::TfOpStats.
PiperOrigin-RevId: 174730411
|
|
|
|
| |
PiperOrigin-RevId: 174726228
|
|
|
|
| |
PiperOrigin-RevId: 174724070
|
|
|
|
| |
PiperOrigin-RevId: 174719222
|
|
|
|
| |
PiperOrigin-RevId: 174719153
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add -march=native to host_copts and host_cxxopts in configure.py
- Make string.h for abstracting string differences at core interpreter level
- Use tensorflow special arg parse instead of flags
- Switch to using tool instead of data for dependency
- Fix python3 compatibility
+ Use six.StringIO instead of StringIO.StringIO
+ Use print_function
+ Properly set binary flags on TempFile's used in toco_convert
- Misc other path fixes
PiperOrigin-RevId: 174717673
|
|
|
|
|
|
| |
and different hash string.
PiperOrigin-RevId: 174715563
|
|
|
|
|
|
| |
This change avoids a potential use-after-free error if the resource is concurrently serialized and destroyed (e.g. by a DestroyResourceOp or Session::Reset()).
PiperOrigin-RevId: 174713115
|
|
|
|
| |
PiperOrigin-RevId: 174708213
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
def replicate_model_fn(model_fn, optimizer_fn, devices=None):
"""Replicate `Estimator.model_fn` over GPUs.
...
I tested that it seems to give the right result on cnn_mnist.py on 1 CPU, 1 real GPU, 4 allow_soft_placement=True GPUs.
Some measurements on CNN MNIST across steps 19300-20000:
1) no replicate_model_fn call:
global_step/sec: 156.254
global_step/sec: 155.074
global_step/sec: 155.74
global_step/sec: 153.636
global_step/sec: 157.218
global_step/sec: 159.644
2) replicate across one hardware GPU:
global_step/sec: 158.171
global_step/sec: 165.618
global_step/sec: 162.773
global_step/sec: 159.204
global_step/sec: 162.289
global_step/sec: 167.173
3) replicate across 4 software GPUs on one hardware GPU (soft placement):
global_step/sec: 75.47
global_step/sec: 76.16
global_step/sec: 75.18
Loss numbers didn't change across the three configurations.
PiperOrigin-RevId: 174704385
|
|
|
|
| |
PiperOrigin-RevId: 174682772
|
|
|
|
|
|
|
|
|
| |
The downloads directory for the make build is within the source tree seen by bazel,
which means that BUILD files (by whatever name) without those downloaded trees
must all be valid in their new location, or not recognized by bazel as being BUILD files.
The new version of nsync handles that, and this change pulls in that new version.
PiperOrigin-RevId: 174652898
|
|
|
|
|
|
|
| |
If the output is being squashed then we want control output 0, except where the
input is a control dependency.
PiperOrigin-RevId: 174633829
|
|
|
|
|
|
| |
Comparable to np.sort, but their "kind" parameter is not implemented (only one sort algorithm) and "order" is not applicable (tensors do not have fields).
PiperOrigin-RevId: 174588000
|