This project is mirrored from https://github.com/tensorflow/federated.
Pull mirroring failed .
Last successful update .
Last successful update .
- 10 Nov, 2020 1 commit
-
-
Michael Reneer authored
PiperOrigin-RevId: 341461167
-
- 09 Oct, 2020 1 commit
-
-
Galen Andrew authored
get_estimate returns the result of some computation performed on the process state. PiperOrigin-RevId: 336199570
-
- 02 Oct, 2020 1 commit
-
-
Michael Reneer authored
This module is being excluded from the Python package based on its name, but it should not be. By default `setuptools` is configured so that file ending in "test.py" are tests and tests are excluded from the Python package. PiperOrigin-RevId: 334625499
-
- 10 Sep, 2020 1 commit
-
-
Michael Reneer authored
PiperOrigin-RevId: 330940593
-
- 09 Sep, 2020 1 commit
-
-
Keith Rush authored
Moves remote executor construction into remote executor factory fn, renames from worker_pool_executor_factory. PiperOrigin-RevId: 330650101
-
- 08 Sep, 2020 1 commit
-
-
Michael Reneer authored
See https://github.com/bazelbuild/rules_python#migrating-from-the-bundled-rules for more informaiton. PiperOrigin-RevId: 330508704
-
- 29 Aug, 2020 2 commits
-
-
Michael Reneer authored
PiperOrigin-RevId: 329012995
-
Michael Reneer authored
* Moved to `computation_wrapper_instances_tests` as unit tests. * Removed duplicate tests. PiperOrigin-RevId: 329007119
-
- 28 Aug, 2020 1 commit
-
-
Keith Rush authored
PiperOrigin-RevId: 328811232
-
- 21 Aug, 2020 1 commit
-
-
Keith Rush authored
The debug execution context is defined to be the simplest execution context that can handle the full generality of the local executor. PiperOrigin-RevId: 327682231
-
- 18 Aug, 2020 1 commit
-
-
Michael Reneer authored
These tests should still be refactored or moved to not require a dependency on testing the entire stack, but the boilerplate plus the narrowly focused visibility rules is better than breaking the visibility rules. This is a follow up to cl/324705661. PiperOrigin-RevId: 327084465
-
- 05 Aug, 2020 1 commit
-
-
Michael Reneer authored
PiperOrigin-RevId: 324859055
-
- 04 Aug, 2020 2 commits
-
-
Taylor Cramer authored
Previously, the default context included a local execution stack, but did not include the compiler built to optimize for this native backend. This meant that users of TFF were not getting the advantages of compilation-for-native unless they explicitly set `set_local_execution_context`. Additionally, this change moves the integration tests inside `core` to use this same local execution stack, including the native compiler. These tests are designed to exercise the local execution stack, and shouldn't be testing against a different environment than the one users experience. PiperOrigin-RevId: 324705661
-
Taylor Cramer authored
PiperOrigin-RevId: 324687422
-
- 16 Jul, 2020 1 commit
-
-
Keith Rush authored
PiperOrigin-RevId: 321423023
-
- 15 Jul, 2020 1 commit
-
-
Michael Reneer authored
This change adds a compiler function to the `ExecutionContext` object. Conceptually a `Context` can be thought of as an "environment" which owns compilation and owns execution for a given computation. Additionally, this change replaces `set_default_executor` with higher level functions in order to simplify how contexts are constructed. * Added compiler function to the `ExecutionContext`. * Deprecated `set_default_executor`. * Removed all usage of `set_default_executor` internally. * Added convenience high level functions that set an execution context: * tff.backends.native.set_local_execution_context * Updated `set_default_executor` call-sites to either use the convenience high level functions or to manually construct a context and use `set_default_context`. Note that we should consider creating the following convenience high level functions: * tff.backends.native.set_remote_execution_context * tff.backends.native.set_sizing_execution_context * tff.backends.iree.set_iree_execution_context PiperOrigin-RevId: 321263709
-