[go: nahoru, domu]
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Septation of Generalised DAG / Data Flow Programming Framework and ML Components #84

Closed
sirinath opened this issue Nov 10, 2015 · 4 comments
Closed

Septation of Generalised DAG / Data Flow Programming Framework and ML Components #84

sirinath opened this issue Nov 10, 2015 · 4 comments

Comments

@sirinath
Copy link

Can you make a clear separation between DAG / Data Flow Programming Framework and the ML framework. The former can have more applications than ML and will open more avenues for its use.
@sirinath sirinath changed the title META: Septation of Generalised DAG / Data Flow Programming Framework and ML META: Septation of Generalised DAG / Data Flow Programming Framework and ML Components Nov 10, 2015
@sirinath sirinath changed the title META: Septation of Generalised DAG / Data Flow Programming Framework and ML Components Septation of Generalised DAG / Data Flow Programming Framework and ML Components Nov 10, 2015
@datnamer
Copy link

If you want generalized DAG programming in python you can use Dask and Blaze from the Blaze Project

@sirinath
Copy link
Author

I like to use the same features but in other languages.

@sirinath
Copy link
Author

You can have have the following break up of the project:

  • Dataflow Computation Framework
  • Dataflow Computation Framework Tools
  • Tool Development Framework
  • ML Framework
  • ML Framework Tools

@martinwicke
Copy link
Member

We have no plans to break up tensorflow, or separate out components for independent distribution.

ilblackdragon added a commit to ilblackdragon/tensorflow that referenced this issue Mar 9, 2016
@ilblackdragon
Fixes tensorflow#84: Reshaping the labels for regression to compute c…
207578c 
…orrectly cost for batch_size>1. Also started working on class_weights.
@bluezone2015 bluezone2015 mentioned this issue Mar 8, 2017
Closed
lissyx added a commit to lissyx/tensorflow that referenced this issue Oct 16, 2018
@lissyx
Merge pull request tensorflow#84 from lissyx/master-gcc72
3747d2d 
Use GCC7.2 for ARMv7 and Aarch64
tensorflow-copybara pushed a commit that referenced this issue Aug 20, 2019
@bondhugula @tensorflower-gardener
Fix AffineExpr::simplifyAdd bug
b240a5b 
- fix missing check while simplifying an expression with floordiv to a
  mod
- fixes issue #82

Signed-off-by: Uday Bondhugula <uday@polymagelabs.com>

Closes #84

COPYBARA_INTEGRATE_REVIEW=tensorflow/mlir#84 from bondhugula:quickfix 26d0d70d4aeaa909e0ad93094fe15b385a618b80
PiperOrigin-RevId: 264338353
@chengdianxuezi chengdianxuezi mentioned this issue Nov 1, 2019
Closed
@yanceyblog yanceyblog mentioned this issue Nov 28, 2019
Closed
cjolivier01 pushed a commit to Cerebras/tensorflow that referenced this issue Dec 6, 2019
@whchung
Merge pull request tensorflow#84 from ROCmSoftwarePlatform/refactor-a…
c4de7e7 
…lgorithm-config

Refactor AlgorithmConfig
@fachu000 fachu000 mentioned this issue Jul 30, 2020
Closed
antkillerfarm pushed a commit to antkillerfarm/tensorflow that referenced this issue Mar 30, 2022
@ZongwuYang
Upload lenet dist training test (tensorflow#84)
1f79321 
Signed-off-by: Zongwu Yang <zongwu.yang@verisilicon.com>
copybara-service bot pushed a commit that referenced this issue May 17, 2022
@mihaimaruseac @tensorflower-gardener
Add security advisory for vuln #84 in 2022
8428500 
PiperOrigin-RevId: 449124266
@polarbbb polarbbb mentioned this issue Mar 17, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@martinwicke @sirinath @datnamer