| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
statically known and their values are equal (i.e. no overlap). #tf-signal
PiperOrigin-RevId: 208002136
|
|
|
|
|
|
| |
This was causing portability problems for platforms that do not support float64. Callers who want higher precision can simply pass tf.float64 as the dtype.
PiperOrigin-RevId: 205457007
|
|
|
|
| |
PiperOrigin-RevId: 201095811
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prior this change, we were using the C API for everything except
Tensor.shape calls, which returned the result from the original Python
shape inference code. With this change, we use the C API in this case
as well. The C API has better shape inference, so this has the effect
of returning more precise shapes in some cases.
This change can be disabled by setting the environment variable
TF_C_API_GRAPH_CONSTRUCTION_SHAPES=0. However, this toggle will
be removed altogether in the near future.
This also fixes a bug in the SWIG that could cause large shape dimensions
to be incorrect.
PiperOrigin-RevId: 200783822
|
|
|
|
|
|
|
| |
Revert #18413. Too many internal test failures due to the name scope change caused by this change.
Revert #18192. Cannot use re2::StringPiece internally. Need alternative for set call. Will pull and clean this up in a separate change.
PiperOrigin-RevId: 197991247
|
|
|
|
| |
PiperOrigin-RevId: 194972934
|
|
|
|
| |
PiperOrigin-RevId: 194031845
|
|
|
|
|
|
| |
the shape of all the outputs is the same.
PiperOrigin-RevId: 190879600
|
|
|
|
| |
PiperOrigin-RevId: 190651873
|
|
|
|
| |
PiperOrigin-RevId: 186674197
|
|
|
|
|
|
| |
mfccs_from_log_mel_spectrograms.
PiperOrigin-RevId: 184400783
|
|
|
|
|
|
|
|
| |
Prior to this change if upper_edge_hertz is larger than sample_rate / 2 (the highest frequency present in the linear spectrogram), the returned matrix would contain columns that are all zeros.
This is likely a surprising result for those that are unfamiliar with signal processing, so it seems safer to raise an exception on such a misconfiguration than to silently allow users to generate poorly behaved features.
PiperOrigin-RevId: 181407176
|
|
|
|
| |
PiperOrigin-RevId: 180746153
|
|
|
|
|
|
|
|
|
|
|
|
| |
To reconstruct an original waveform, a complimentary window function should
be used in inverse_stft. Such a window function can be constructed with
tf.contrib.signal.inverse_stft_window_fn.
Inlines and refactors the test for equivalence of inverse_stft and original
waveform. Adds a test case that shows a large difference between inverse stft
with and without complimentary window function.
PiperOrigin-RevId: 174530978
|
|
|
|
|
|
| |
of a private implementation.
PiperOrigin-RevId: 170943986
|
|
|
|
|
|
| |
foldable for constant inputs.
PiperOrigin-RevId: 170777731
|
|
|
|
|
|
| |
session_run_hooks.py talks about "monitors", but I'm guessing what's meant is in fact "hooks". Am I right?
PiperOrigin-RevId: 170753935
|
| |
|
|
|
|
| |
PiperOrigin-RevId: 170753517
|
|
|
|
|
|
|
|
|
|
| |
inverse_stft.
Also add tests for stft/inverse_stft when the shape/rank of the inputs are unknown.
Fixes GitHub Issue #13363.
PiperOrigin-RevId: 170662530
|
|
|
|
|
|
| |
known statically.
PiperOrigin-RevId: 170358086
|
|
|
|
| |
PiperOrigin-RevId: 170350852
|
|
|
|
|
|
| |
The Great Models Move (a.k.a. the research subfolder)
PiperOrigin-RevId: 169763373
|
|
|
|
| |
PiperOrigin-RevId: 168560255
|
|
|
|
| |
PiperOrigin-RevId: 164728247
|
|
|
|
|
|
| |
flakiness on macOS.
PiperOrigin-RevId: 163426631
|
|
|
|
| |
PiperOrigin-RevId: 163127500
|
|
|
|
|
|
| |
gradient test.
PiperOrigin-RevId: 163092423
|
|
|
|
| |
PiperOrigin-RevId: 162748291
|
|
|
|
| |
PiperOrigin-RevId: 162658696
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
END_PUBLIC
---
Commit daa67ad17 authored by Jonathan Hseu<vomjom@vomjom.net>
Committed by Frank Chen<frankchn@gmail.com>:
Remove unittest import (#11596)
---
Commit 491beb74c authored by A. Unique TensorFlower<gardener@tensorflow.org>
Committed by TensorFlower Gardener<gardener@tensorflow.org>:
BEGIN_PUBLIC
Automated g4 rollback of changelist 162423171
PiperOrigin-RevId: 162541442
|
|
|
|
|
|
| |
tf.contrib.signal.frame.
PiperOrigin-RevId: 162523648
|
|
|
|
|
|
|
|
| |
tf.contrib.signal.
These are implemented using GPU-capable ops and have gradient support.
PiperOrigin-RevId: 162511440
|
|
|
|
|
|
| |
This is the inverse operation of tf.contrib.signal.frame. This is implemented using GPU-capable ops and supports gradients.
PiperOrigin-RevId: 162017464
|
|
|
|
|
|
|
|
|
|
|
| |
- Support arbitrary rank tensors.
- Add an `axis` parameter for framing any axis.
- Add a `pad_end` and `pad_value` parameter for controlling the signal padding. Padding is disabled by default to avoid a copy of a potentially large Tensor.
- Support shape inference of resulting framed tensor.
- Expand the tests, including tests for the gradients.
- Since `frames` is a noun and not a verb, rename `frames` to `frame`.
PiperOrigin-RevId: 161998921
|
|
|
|
| |
PiperOrigin-RevId: 161891114
|
|
Change: 155209832
|