Node.js (JavaScript) Wrapper API about tensorflow

[ZECTBynmo]

+1!

[dhritzkiv]

+1

[fiws]

👍

[mikealche]

+1

[ripper2hl]

please try use reactions button --> http://www.geekwire.com/2016/github-adds-reactions-keep-comments-track/ no more +1 comments xD

[nikhildaga]

Happy Anniversary TensorFlow !

https://research.googleblog.com/2016/11/celebrating-tensorflows-first-year.html

I notice TensorFlow is now accessible from Go, Rust and Haskell. Why ignore JavaScript ?

Really waiting for a machine library in JavaScript.

[jagandecapri]

Just what I was searching for. 👍

As quoted from the offical website http://www.tensorflow.org/

we’re hoping to entice you to contribute SWIG interfaces to your favorite language -- be it Go, Java, Lua, Javascript, or R.

I am new to this whole SWIG thing but searched around and found this. http://www.swig.org/Doc3.0/Javascript.html

Not really sure how this works. Do we need to write swig interface file specifically for Javascript or is it auto-generated when running some commands or is somebody already working on this (this would be awesome) ?

[imgntn]

+1 👍

[mattkosoy]

👍

[chenzxcvb]

+1

[prathamesh7pute]

+1

[dmitriykharchenko]

+1

[marcbaetica]

+1

[lowe0292]

👍

[nikhilk]

+1!

Just starting out on one, but new to writing a nodejs addon. Checking out the swig interface files to see if they're going to be helpful, or if I should just use the c++ API.

[vnglst]

+1

[peterbraden]

@martinwicke thanks for the encouragement. I made an initial stab at it here: #2206 - this is just a proof of concept that gets the version string into nodejs. I'll start work on adding the swig interfaces for the graph running stuff.

[jonchenn]

+10000

[martinwicke]

@peterbraden sorry for the prolonged silence. We are building out the C++ API, and it will grow over time. I expect the most useful bits to be the parts that are needed to run an existing graph. The C++ graph building API is being redone right now, so it's not particularly useful to spend much time on it.

I'd love it if you prepared a PR to put these bindings into contrib/nodejs.

[jalona]

+1

[Foorack]

+1

[tngan]

+1

[vincentvanhoucke]

This is something the core TensorFlow team is unlikely to tackle in the near future, so if you want to contribute it, please go ahead! I would recommend circulating a proposed implementation on the discuss mailing list early on, so that a consensus about where such API might live (in repo / off repo / in 'contrib' directory) can be reached ahead of time.

[dmcmorris]

Found this while looking into wether or not bindings existed already. Going to learn some tensor flow via the current python API before researching more, but I have built nodejs bindings for C++ libs before and can tell you from experience that swig is the wrong way.

If you simply use the swig bindings then you will have synchronous blocking code in an async environment. The swig bindings do not run things on IO threads, they execute on the main event loop from what I understand/experienced.

Once I have some basic tensor flow experience under my belt I'll likely be interested in building out proper bindings. So if anyone is serious about that and/or wants more details on working with v8 modules, let me know.

[qrpike]

+1

[marcbaetica]

@dmcmorris I am seriously interested in lending a hand! What resources do you recommend for working with v8 modules? We can assemble a team here and start diving into materials asap as this project is way overdue :)

[himanshurobo]

Is there any update ??

On 31-Oct-2016 12:06 pm, "willshion" [email protected] wrote:

+1s

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#37 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANrvwrbmShC9c0_wsNpTudKSCb0-8qt8ks5q5Yx3gaJpZM4Ge5NV
.

[bertolo1988]

+1

[tngan]

We hope more developers to discuss and contribute. Now we have a slack channel named as nodejs (see #31), and a Github repository node-tensorflow is reserved. Thanks @Foorack !

[peterbraden]

I have a working prototype using SWIG here: node-tensorflow/node-tensorflow#13

The next steps would be to define the areas that the bindings would initially cover (must be within the C++ API ) and start implementing the SWIG interface files for these.

If anyone has experience with SWIG, I'd love to collaborate, as it seems like a huge amount of the python SWIG interfaces are custom overrides etc. and I'm keen not to reproduce their work. Additionally, would be great to get some clarity from the tensorflow team on what API's would be good to initially cover as I'm sure their roadmap has many changes on the way, and I wouldn't want to conflict. (cc @martinwicke ? )

[teckays]

+1

[lucked]

+1

[mredmundto]

+1

[Foorack]

Anyone up to write a NodeJS library? 👍
I think it would be better with a official NodeJS API however a community one will be as (if not more) interesting in my opinion. I know there are multiple ways of approaching this however I strongly recommend node-gyp for performance. I will gladly contribute in any way I can, however, this is something I will not be able to do alone. Would be best if a few other people is interested as well, specially someone with C++ knowledge.

[augbog]

👍

[tngan]

@Foorack I am willing to contribute it if some people are interested as well. Is it possible to move the discussion to a slack channel ? (see #31)

[Foorack]

@tngan The slack channel is private, however I was able to join with the herokuapp link. 👍

[marcbaetica]

I am willing to contribute. Thanks for the initiative guys!

[Foorack]

@miguelalche Glad to see you're interested! Please join the slack channel and someone will add you to the repository. ^^

[cauerego]

I look forward for contributing ( specially along with #132 ) !!

[gpresland]

+1

[mpj]

Hooray for node! Let's do this.

[miql]

+1

[g3ortega]

+1

[jimfleming]

Here's a writeup on how to load and execute TensorFlow graphs using the C API: https://medium.com/jim-fleming/loading-tensorflow-graphs-via-host-languages-be10fd81876f (source code included)

[tngan]

The proposal will be released in the next week. Keep tracking on https://github.com/node-tensorflow/node-tensorflow.

[duyet]

+1

[nikhilk]

I have published my starting point -- https://github.com/nikhilk/node-tensorflow that will be published to npm later.

@jimfleming - like your approach (we're both using ffi ... I did it to get started quickly). Are you going to take on building higher level framework-style APIs to replicate the python experience? Thats my next step.

[jimfleming]

@nikhilk Thanks. Something like new tf.Tensor() instead of tf.NewTensor() might be a nice addition but I'm not planning on expanding it at the moment. I'm only interested in loading graphs created in python and I think I like the minimalism.

[robbinhan]

+1

[tngan]

The proposal is released here with current progress.
https://github.com/node-tensorflow/node-tensorflow/tree/1.0.0

There is an open issue for the discussion.
node-tensorflow/node-tensorflow#2

[alexzaporozhets]

+1

[gmosx]

+1

[please-wait]

+1

[haduythuan]

+1

[qrpike]

+1

[ken-okabe]

+1

[buholzer]

+1

[ovrmrw]

+1

[Konard]

+1

[pavelchristof]

+1

It'd be great to be able to easily run tensorflow networks in node.js based servers.

[nikhildaga]

+1

[taveras]

+1

[alexahdp]

+1

[pavel-kudinov]

+1

[muka]

+1

[jasonmayes]

+1

[andrewjaykeller]

I am very willing to contribute. @Foorack please add me to what ever you can! I have a real life use case for this so it will be great to develop and test it at the same time!!

[Foorack]

@pushtheworldllc I'm glad you are interested. :)
The repository and the proposal can be found here: https://github.com/node-tensorflow/node-tensorflow/
You can use this link to join our slack channel: https://tensor-flow-talk-invite.herokuapp.com/

[highruned]

+1

[teagup]

+1

[helxsz]

+1

[aralroca]

+1 👍

[pavelkukov]

+1 👍

[vsantosu]

+1

+1 👍

[kristoffernolgren]

+1

[maltyxx]

+1

+1

[wajeehullah]

+1

[sbechet]

+1

[allanjuma]

👍

[adamvresky]

+1

[claudio4]

+1

[Loksly]

+1

[progdude]

+1

[vunb]

+1

[guillaume-chevalier]

This would be interesting for pure front-end graph exportation for direct usage on web clients. Even if the desired inputs/outputs asked from the graph would be hard-coded in the exported JS "sess.run" equivalent function.

[jadewon]

+1

[rodrigo-garcia-olx]

👍

[prajankya]

+1

[heineiuo]

+1

[sequoiar]

+1

[vjk2005]

+1

[o0x2a]

+1

[himanshurobo]

Is there any link related to node-gyp binding for tensor flow API ??

[cedricve]

+1

[keyvez]

+1

[lcultx]

+1

[willshion]

+1s