question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Moving forward the idea is to have two APIs:

  • a high level API as close as possible to keras:

    • allowing user to more clearly express what they want to achieve with secure computation (along the lines of how TF2 wraps distribution up into a DistributionStrategy object)

    • making it easier for us to guide users in how to get good performance out of TFE, in some sense making it harder for them to shoot themselves in the foot

  • a low level API similar to what exists currently:

    • gives full power but also the ability to shoot yourself in the foot by eg naively using expensive operations everywhere

See also Standardizing on Keras: Guidance on High-level APIs in TensorFlow 2.0

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:10 (10 by maintainers)

github_iconTop GitHub Comments

2reactions
mortendahlcommented, May 7, 2019

Note: let’s make sure that tfe.keras matches tf.keras as much as possible, ideally such that one can simply replace tf with tfe.

1reaction
mortendahlcommented, May 14, 2019

One small note: it seems safe to follow design patterns that users will be familiar with from TF already, even if there might potentially be better ways of doing things. One concrete example is how to make this Keras implementation agnostic to the underlying computation protocol, which can be done in at least two ways:

  • define abstract Keras elements that can be created without knowing the computation protocol and later instantiated in an explicit call; one issue here is the Keras functional API which might require us to replicate a lot of dummy elements and patch up;

  • an alternative is to take inspiration from TF distribution strategies and allow the use of contexts; to still be agnostic to the computation protocol the user can wrap model creation in a function

One potential issue with the second approach is how to know the entire model before committing to the protocol, which might be useful as part of picking techniques or (crypto) parameters. One solution that fits with the function-pointer approach is to have a special context (with dummy tensors etc) in which the model is constructed and from which a protocol suggestion can be derived.

cc @yanndupis @jvmancuso

Read more comments on GitHub >

github_iconTop Results From Across the Web

HighLevel API
An authorized API key will allow you to pass data between software automatically using applications like Zapier, Pabbly, Integrately, Make ( ...
Read more >
API 2.0 Overview | Integrations API - highlevel | Stoplight
API 2.0 Overview. These APIs use OAuth 2.0 flow for authentication. To get started, you would need to register an app with us...
Read more >
GoHighLevel API Overview - SyncWith
High level has 12 API endpoints which are logically grouped into the various objects that HighLevel stores, eg contacts, campaigns, appointments are all ......
Read more >
The High Level API - Unity - Manual
The High Level API (HLAPI) is a system for building multiplayer capabilities for Unity games. It is built on top of the lower...
Read more >
High level API - Post Affiliate Pro Support Portal
High level API provides objects for easy manipulation with common entities, like affiliates, commissions, etc. For every entity there are two main objects: ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found