subscribe mxnet dev mailing list

2019-04-16 Thread Wang Jiajun



Re: [Announcement] New Committer - Wang Jiajun

2019-04-16 Thread kellen sunderland
Welcome!  Very impressed with the work fixing memory leaks so far.

On Tue, Apr 16, 2019 at 9:14 AM Carin Meier  wrote:

> Congrats!
>
> On Tue, Apr 16, 2019 at 11:58 AM Anirudh Subramanian <
> anirudh2...@gmail.com>
> wrote:
>
> > Hi,
> >
> > Please join me to welcome Wang Jiajun (https://github.com/arcadiaphy)
> as a
> > new committer of Apache (incubating) MXNet!
> >
> > Wang has been solving some tough bugs with respect to memory leaks,
> process
> > fork handling, dependency engine issues and custom op exception handling.
> >
> > Issue Involvement:
> >
> >
> https://github.com/apache/incubator-mxnet/issues?utf8=%E2%9C%93=is%3Aissue+involves%3Aarcadiaphy
> >
> > PRs authored:
> >
> >
> https://github.com/apache/incubator-mxnet/pulls?utf8=%E2%9C%93=is%3Apr+author%3Aarcadiaphy+
> >
> > Anirudh
> >
>


Re: [QUESTION] mxnet/Tuple vs nnvm/Tuple

2019-04-16 Thread Lin Yuan
Jun,

Thanks! I was also leaning towards your suggestion.
I have updated nnvm::Tuple to mxnet::Tuple for a few remaining places in
MXNet.

Best,

Lin

On Tue, Apr 16, 2019 at 11:35 AM Jun Wu  wrote:

> include/mxnet/tuple.h was first copied from nnvm in this PR
>  so that we can make
> changes on it to support zero-dim and zero-size tensors without affecting
> TVM project. That PR has changed most of the places where nnvm::Tuple and
> nnvm::TShape were used to mxnet::Tuple and mxnet::TShape. If we still see a
> few locations not changed in the current codebase, we should change them to
> use mxnet Tuple as well for better cosmetics. The nnvm/tuple.h can be
> deprecated in MXNet.
>
> On Mon, Apr 15, 2019 at 10:44 PM Lin Yuan  wrote:
>
> > Dear Community,
> >
> > Currently in MXNet there are two Tuple template class defined in
> > mxnet/tuple.h and nnvm/tuple.h respectively. These two templates are
> higly
> > similar and most part are duplicated except for a couple of functions.
> > However, they were used mixedly in current codebase and causing conflict
> > sometimes.
> >
> > Is there any historical reason that we keep two copies of the same
> template
> > class? If not, can we refactor the code to consolidate into one?
> >
> > Thanks!
> >
> > Lin
> >
>


Re: Changes to MPI-operator

2019-04-16 Thread Roshani Nagmote
Sounds good. We(Pinar, Vandana and me) are currently prototyping and we are
planning to start a discussion on dev list once we have some logical
conclusion.
We will share more details soon and seek feedback from the community.

Thanks,
Roshani

On Mon, Apr 15, 2019 at 5:30 PM Yuan Tang  wrote:

> I am cc’ing MXNet dev mailing list here.
>
> Thanks for the note Roshani. Look forward to seeing your contribution!
> Though let’s also discuss this in MXNet dev mailing list since other people
> (e.g. Carl and Lin) might be working on this as well to avoid duplicate
> work.
>
> Best,
> Yuan
>
> On Mon, Apr 15, 2019 at 5:51 PM Rong Ou  wrote:
>
>> Sounds great! Yes it would be nice to have some examples for MXNet.
>>
>> On Mon, Apr 15, 2019 at 3:36 PM Roshani Nagmote <
>> roshaninagmo...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I work on Apache MXNet and recently I used MPI-Operator to run
>>> distributed training with MXNet and horovod on Kubernetes.
>>> I with few other folks tried to adjust the capacity for a training job
>>> based on the available workers and restart the training job from where it
>>> left off if any worker goes away in between.
>>>
>>> To do this, we had to do a few modifications to MPI-operator. For
>>> example, updating workerReplicas and launcherRole. Currently, changes are
>>> in my repo and I will be making a PR on MPI-operator with these changes.
>>> Also, planning to contribute few examples. I wanted to reach out to you
>>> first before creating a PR.
>>>
>>> Please let me know what your thoughts are on this.
>>>
>>> Thanks,
>>> Roshani
>>>
>>


Re: [Announcement] New Committer - Wang Jiajun

2019-04-16 Thread Carin Meier
Congrats!

On Tue, Apr 16, 2019 at 11:58 AM Anirudh Subramanian 
wrote:

> Hi,
>
> Please join me to welcome Wang Jiajun (https://github.com/arcadiaphy) as a
> new committer of Apache (incubating) MXNet!
>
> Wang has been solving some tough bugs with respect to memory leaks, process
> fork handling, dependency engine issues and custom op exception handling.
>
> Issue Involvement:
>
> https://github.com/apache/incubator-mxnet/issues?utf8=%E2%9C%93=is%3Aissue+involves%3Aarcadiaphy
>
> PRs authored:
>
> https://github.com/apache/incubator-mxnet/pulls?utf8=%E2%9C%93=is%3Apr+author%3Aarcadiaphy+
>
> Anirudh
>


[Announcement] New Committer - Wang Jiajun

2019-04-16 Thread Anirudh Subramanian
Hi,

Please join me to welcome Wang Jiajun (https://github.com/arcadiaphy) as a
new committer of Apache (incubating) MXNet!

Wang has been solving some tough bugs with respect to memory leaks, process
fork handling, dependency engine issues and custom op exception handling.

Issue Involvement:
https://github.com/apache/incubator-mxnet/issues?utf8=%E2%9C%93=is%3Aissue+involves%3Aarcadiaphy

PRs authored:
https://github.com/apache/incubator-mxnet/pulls?utf8=%E2%9C%93=is%3Apr+author%3Aarcadiaphy+

Anirudh