Hi Sheng.
Do you need some help with this? Do we plan to have this for 1.5?
Pedro.
On Wed, Apr 24, 2019 at 4:26 PM Pedro Larroy
wrote:
>
> Thanks. Great to read.
>
> On Wed, Apr 24, 2019 at 2:19 PM Sheng Zha wrote:
> >
> > The community has agreed to donate mshadow to the mxnet code base. I
Hi Pedro,
Thanks for taking the inititaive. Skimming through the design doc, I didn't see
comparison with existing solutions such as relay in tvm, which is already a
dependency of mxnet already. Could you elaborate on comparison with existing
solutions in the design doc too?
-sz
On
Hi Tianqi
I thought a bit more about your comments and I think there is a simple
way to address your concerns that satisfies both needs.
We can have a NodeAttributes template class which has a map of string
to any as it's currenlty the case, so the graph can be used in the
highly dynamic
The core part of the proposal is to move the graph to be much more strongly
typed template class.
I think this is mainly a point of engineering taste, and both sides have
pros and cons, let me list them before I share my thoughts on this issue:
- Typed fields certainly enjoy more compile-time
Thanks for the proposal. Let me share some of my thoughts:
Specific comments on the proposal
---
The heavy use of generic in the Graph type was a huge departure from
type-erased data structure which was presented in the previous design.
While we
+1 Let python2 rest, let's simplify our infrastructure and need to
support old Python versions.
On Mon, May 13, 2019 at 1:58 PM Jake Lee wrote:
>
> +1 Recently I upgraded the Numpy version and found out that Pylint had
> false alarm on it. The Pylint fix is only available on Python3. So I
>
Hi Tianqi
Thanks for the quick response.
Could you point to examples where graph.h is being exposed which would
not be possible with what I propose? I don't think my proposal is
having any impact in language bindings, and the way I describe it
doesn't affect having or not having higher language
Hi dev@
As a result of my deep dives on the graph machinery I have created a
new proposal to improve the operator graph in MXNet.
This would mean superseding the use of NNVM Graph in MXNet and having
a new implementation that we can use to simplify a lot of code and do
powerful graph
Hi Sheng
Could you provide relevant links to Relay and what you would
recommend to read so we have a focused discussion instead of me
potentially me miss-searching? Probably I also missed the discussion
or vote in the mail list regarding including TVM as a depedency or
future plans on using
Dear MXNet community,
I would like to invite you to the regular Apache MXNet (Incubating) User
Group meeting on the 19th of March 2019 [1].
As usually, the meeting will have remote VC, powered by Amazon Chime [2].
Due to availability, **TODAY** It will be held from* 7pm-8pm (CEST) /
10am-11am
Hi Per da Silva,
I would like to join this meeting. I would like to ask about some solution
of how to replace the depreciated "crop" layer properly.
I found many have the same issue and I do not find a proper solution. It
can be a real deal breaker for me despite I am really fond
of MXNET and
Hey Wen-Yang Chu,
Unfortunately, my talents are more on the CI/CD at the moment, so I don't
know that I'll be able to answer your question.
Is there anyone out there than can join us and shine some light in the
situation?
If no one is able to join, I'll try to understand your question and find
12 matches
Mail list logo
