If I'm understanding mxnet.js correctly, any mxnet model can be
converted to mxnet.js via:
https://github.com/dmlc/mxnet.js/blob/master/tools/model2json.py
and then executed on mxnet.js
Questions: is this 'mxnet json model' format documented anywhere?
On Thu, Nov 2, 2017 at 12:10 PM, TongKe
Build for MXNet branch master has broken. Please view the build at
https://builds.apache.org/job/incubator-mxnet/job/master/581/
The JIRA was just created, so as far as I know, there is no "process" yet.
I do think we should get some sections (are they called Boards?) created,
though, such as Infrastructure. I've used Jira, but never set one up from a
blank slate. Who knows how this is done?
On Thu, Nov 2, 2017 at 9:07
Many of developers are using Makefile. Getting rid of it doesn't sound user
friendly.
On Thu, Nov 2, 2017 at 8:53 AM, Chris Olivier wrote:
> I don't know why we don't get rid of the Makefile altogether and use cmake.
> It's a pain to manage both of them independently.
Chris Olivier created MXNET-1:
-
Summary: EPIC: Create independent Jenkins Server for MXNet CI
Key: MXNET-1
URL: https://issues.apache.org/jira/browse/MXNET-1
Project: Apache MXNet
Issue Type:
I agree about your point on correctness -- do you know of any known
correctness issues with Ninja?
These build times seem to be NOT with GPU builds and distributed kvstore
enabled -- could you please confirm? nvcc builds take a significant time.
Bhavin Thaker.
On Thu, Nov 2, 2017 at 8:45 AM,
Hi Pedro,
Using Ninja to improve build times is a good suggestion. Can you share the
build times you have observed with and without using Ninja? I presume you
have enabled compile-time options for GPU builds and Distributed MXNet for
the builds you have experimented with.
See also: