Re: There is a bug in shape inference of the where operator

2018-08-23 Thread Sheng Zha
Correct me if I'm wrong. The bug went into the release branch so we need to
cherry-pick the fix once the patch is merged to master.

-sz

On Thu, Aug 23, 2018 at 4:14 PM Lin Yuan  wrote:

> Hi Da,
>
> I am currently running the unit test and will check in the fix once it's
> complete.
>
> Thanks,
>
> Lin
>
> On Thu, Aug 23, 2018 at 3:59 PM Zheng, Da 
> wrote:
>
> > Hello all,
> >
> > There is a little bug in shape inference of the where operator.
> Currently,
> > the where operator doesn’t work if the first input is a 1D array. Yuan
> Lin
> > will provide a patch to fix this bug.
> >
> > Best,
> > Da
> >
>


There is a bug in shape inference of the where operator

2018-08-23 Thread Zheng, Da
Hello all,

There is a little bug in shape inference of the where operator. Currently, the 
where operator doesn’t work if the first input is a 1D array. Yuan Lin will 
provide a patch to fix this bug.

Best,
Da


Re: Release plan - MXNET 1.3

2018-08-23 Thread kellen sunderland
Great news!  Thanks for the efforts Roshani + Sheng.

On Thu, Aug 23, 2018 at 6:58 PM Roshani Nagmote 
wrote:

> Release branch v1.3.x was cut yesterday night. Thanks, @Sheng for helping
> with this and merging a bunch of PRs. I will be running tests on the branch
> and move forward with the release steps now. :)
> Thanks,
> Roshani
>
> On Wed, Aug 22, 2018 at 11:12 AM Roshani Nagmote <
> roshaninagmo...@gmail.com>
> wrote:
>
> > Thanks Patric for reviewing the notes. Updated the doc with MKL-DNN
> points
> > you mentioned accordingly.
> >
> > Regards,
> > Roshani
> >
> > On Tue, Aug 21, 2018 at 8:03 PM Zhao, Patric 
> > wrote:
> >
> >> Hi Roshani,
> >>
> >> Good notes :)
> >>
> >> Several items about the performance and MKL-DNN in the below, please
> help
> >> take a review.
> >>
> >> @Da, Alex, if anything about MKL-DNN is missed, feel free to add.
> >>
> >> *Performance improvement
> >> +Support for dot(dns, csr) = dns and dot(dns, csr.T) = dns on CPU
> >> https://github.com/apache/incubator-mxnet/pull/3
> >> +Performance improvement for Batch Dot on CPU from mshadow
> >> https://github.com/dmlc/mshadow/pull/342
> >> -Fix the topk regression issue (#12197)
> >> This is the bugfix rather than performance improvements
> >>
> >>
> >> *MKL-DNN
> >> More functionality supports:
> >> +Support more activation functions, "sigmoid", "tanh", "softrelu"
> >> https://github.com/apache/incubator-mxnet/pull/10336
> >>
> >> Debugging functionality:
> >> +Result check
> >> https://github.com/apache/incubator-mxnet/pull/12069
> >> +Backend switch
> >> https://github.com/apache/incubator-mxnet/pull/12058
> >>
> >> Thanks,
> >>
> >> --Patric
> >>
> >> > -Original Message-
> >> > From: Roshani Nagmote [mailto:roshaninagmo...@gmail.com]
> >> > Sent: Wednesday, August 22, 2018 1:53 AM
> >> > To: dev@mxnet.incubator.apache.org
> >> > Subject: Re: Release plan - MXNET 1.3
> >> >
> >> > Hi,
> >> >
> >> > Thank you everyone for helping to clear release blockers. CI tests
> were
> >> failing
> >> > so we delayed RC by some time. But now the tests are passing and we
> are
> >> > ready to cut the release branch.
> >> >
> >> > I have drafted release notes here:
> >> > https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28in
> >> > cubating%29+1.3.0+Release+Notes
> >> >
> >> >
> >> > Please take a look and update if I have missed anything. I will be
> >> cutting
> >> > RC0 tomorrow.
> >> >
> >> > Thanks,
> >> > Roshani
> >> >
> >> > On Thu, Aug 16, 2018 at 2:28 PM Roshani Nagmote
> >> > 
> >> > wrote:
> >> >
> >> > > Sure will do. thanks.
> >> > >
> >> > > -Roshani
> >> > >
> >> > > On Thu, Aug 16, 2018 at 11:53 AM Afrooze, Sina 
> >> > wrote:
> >> > >
> >> > >> Hi Roshani - Can you please make sure that this fix (which is
> already
> >> > >> merged to master) is also merged to the stable branch for 1.3.0:
> >> > >> https://github.com/apache/incubator-mxnet/pull/11493 - Thanks,
> Sina
> >> > >>
> >> > >>
> >> > >> On 8/16/18, 10:51 AM, "Roshani Nagmote"
> >> > 
> >> > >> wrote:
> >> > >>
> >> > >> Hi all,
> >> > >>
> >> > >> Release status:
> >> > >>
> >> > >> Currently, for release 1.3.0 there are a couple of issues open
> >> > >> which needs
> >> > >> to be resolved before cutting RC.
> >> > >>
> >> > >> The current date we are looking at for cutting RC0 is
> >> 08/17(Friday).
> >> > >>
> >> > >>
> >> > >>
> >> > >> Open issues which need to be looked at before cutting RC:
> >> > >>
> >> > >>1. Topk regression issue
> >> > >> -
> >> > >> #12202 PR
> >> > >>with fix <
> >> https://github.com/apache/incubator-mxnet/pull/12202>
> >> > >>2. Excessive memory allocation issue
> >> > >> -
> >> > >> #12184 PR
> >> > >>with fix <
> >> https://github.com/apache/incubator-mxnet/pull/12184>
> >> > >>3. Test_io.test_csvIter breaks on CentOS
> >> > >> -
> >> > >> #12189 PR
> >> > >>with fix
> >> > >> 
> >> > >>
> >> > >>
> >> > >>
> >> > >> @committers, could you please help review these PRs and get
> them
> >> > >> merged?
> >> > >>
> >> > >>
> >> > >>
> >> > >> Thanks,
> >> > >>
> >> > >> Roshani
> >> > >>
> >> > >> On Tue, Aug 14, 2018 at 12:46 PM Roshani Nagmote <
> >> > >> roshaninagmo...@gmail.com>
> >> > >> wrote:
> >> > >>
> >> > >> > Talked to the person who ran resnet50 benchmarks offline.
> Build
> >> > >> flag was
> >> > >> > not properly set so there was a difference in performance
> >> > >> numbers observed.
> >> > >> > There is no issue caught and he was able to get the same
> >> results as
> >> > >> > mentioned here
> >> https://mxnet.incubator.apache.org/faq/perf.html
> >> > >> > <
> >> https://mxnet.incubator.apache.org/faq/perf.html#scoring-results>

Re: Release plan - MXNET 1.3

2018-08-23 Thread Roshani Nagmote
Release branch v1.3.x was cut yesterday night. Thanks, @Sheng for helping
with this and merging a bunch of PRs. I will be running tests on the branch
and move forward with the release steps now. :)
Thanks,
Roshani

On Wed, Aug 22, 2018 at 11:12 AM Roshani Nagmote 
wrote:

> Thanks Patric for reviewing the notes. Updated the doc with MKL-DNN points
> you mentioned accordingly.
>
> Regards,
> Roshani
>
> On Tue, Aug 21, 2018 at 8:03 PM Zhao, Patric 
> wrote:
>
>> Hi Roshani,
>>
>> Good notes :)
>>
>> Several items about the performance and MKL-DNN in the below, please help
>> take a review.
>>
>> @Da, Alex, if anything about MKL-DNN is missed, feel free to add.
>>
>> *Performance improvement
>> +Support for dot(dns, csr) = dns and dot(dns, csr.T) = dns on CPU
>> https://github.com/apache/incubator-mxnet/pull/3
>> +Performance improvement for Batch Dot on CPU from mshadow
>> https://github.com/dmlc/mshadow/pull/342
>> -Fix the topk regression issue (#12197)
>> This is the bugfix rather than performance improvements
>>
>>
>> *MKL-DNN
>> More functionality supports:
>> +Support more activation functions, "sigmoid", "tanh", "softrelu"
>> https://github.com/apache/incubator-mxnet/pull/10336
>>
>> Debugging functionality:
>> +Result check
>> https://github.com/apache/incubator-mxnet/pull/12069
>> +Backend switch
>> https://github.com/apache/incubator-mxnet/pull/12058
>>
>> Thanks,
>>
>> --Patric
>>
>> > -Original Message-
>> > From: Roshani Nagmote [mailto:roshaninagmo...@gmail.com]
>> > Sent: Wednesday, August 22, 2018 1:53 AM
>> > To: dev@mxnet.incubator.apache.org
>> > Subject: Re: Release plan - MXNET 1.3
>> >
>> > Hi,
>> >
>> > Thank you everyone for helping to clear release blockers. CI tests were
>> failing
>> > so we delayed RC by some time. But now the tests are passing and we are
>> > ready to cut the release branch.
>> >
>> > I have drafted release notes here:
>> > https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28in
>> > cubating%29+1.3.0+Release+Notes
>> >
>> >
>> > Please take a look and update if I have missed anything. I will be
>> cutting
>> > RC0 tomorrow.
>> >
>> > Thanks,
>> > Roshani
>> >
>> > On Thu, Aug 16, 2018 at 2:28 PM Roshani Nagmote
>> > 
>> > wrote:
>> >
>> > > Sure will do. thanks.
>> > >
>> > > -Roshani
>> > >
>> > > On Thu, Aug 16, 2018 at 11:53 AM Afrooze, Sina 
>> > wrote:
>> > >
>> > >> Hi Roshani - Can you please make sure that this fix (which is already
>> > >> merged to master) is also merged to the stable branch for 1.3.0:
>> > >> https://github.com/apache/incubator-mxnet/pull/11493 - Thanks, Sina
>> > >>
>> > >>
>> > >> On 8/16/18, 10:51 AM, "Roshani Nagmote"
>> > 
>> > >> wrote:
>> > >>
>> > >> Hi all,
>> > >>
>> > >> Release status:
>> > >>
>> > >> Currently, for release 1.3.0 there are a couple of issues open
>> > >> which needs
>> > >> to be resolved before cutting RC.
>> > >>
>> > >> The current date we are looking at for cutting RC0 is
>> 08/17(Friday).
>> > >>
>> > >>
>> > >>
>> > >> Open issues which need to be looked at before cutting RC:
>> > >>
>> > >>1. Topk regression issue
>> > >> -
>> > >> #12202 PR
>> > >>with fix <
>> https://github.com/apache/incubator-mxnet/pull/12202>
>> > >>2. Excessive memory allocation issue
>> > >> -
>> > >> #12184 PR
>> > >>with fix <
>> https://github.com/apache/incubator-mxnet/pull/12184>
>> > >>3. Test_io.test_csvIter breaks on CentOS
>> > >> -
>> > >> #12189 PR
>> > >>with fix
>> > >> 
>> > >>
>> > >>
>> > >>
>> > >> @committers, could you please help review these PRs and get them
>> > >> merged?
>> > >>
>> > >>
>> > >>
>> > >> Thanks,
>> > >>
>> > >> Roshani
>> > >>
>> > >> On Tue, Aug 14, 2018 at 12:46 PM Roshani Nagmote <
>> > >> roshaninagmo...@gmail.com>
>> > >> wrote:
>> > >>
>> > >> > Talked to the person who ran resnet50 benchmarks offline. Build
>> > >> flag was
>> > >> > not properly set so there was a difference in performance
>> > >> numbers observed.
>> > >> > There is no issue caught and he was able to get the same
>> results as
>> > >> > mentioned here
>> https://mxnet.incubator.apache.org/faq/perf.html
>> > >> > <
>> https://mxnet.incubator.apache.org/faq/perf.html#scoring-results>
>> > >> >
>> > >> > We are good here.
>> > >> >
>> > >> > Thanks,
>> > >> > Roshani
>> > >> >
>> > >> > On Mon, Aug 13, 2018 at 4:08 PM Roshani Nagmote <
>> > >> roshaninagmo...@gmail.com>
>> > >> > wrote:
>> > >> >
>> > >> >> Hi Dom,
>> > >> >>
>> > >> >> I verified resnet50 run on MXNet master branch. Checked on
>> > >> single gpu
>> > >> >> machine. Numbers match. I didn't see any performance
>> 

Re: Proposal: Apache MXNet user group meetings

2018-08-23 Thread Ivan Serdyuk
On Wed, Aug 22, 2018 at 9:04 PM Davydenko, Denis <
dzianis.davydze...@gmail.com> wrote:

> Hello, Apache MXNet community,
>

Hello.


> I would like to submit for your consideration updated and improved
> suggestion for Apache MXNet User Groups meetings: [1]. Main goals of this
> initiative are:
>
> - make it easy: users and developers should be able to understand what is
> Group Meeting and how to participate in it in under 60 seconds
>

Maybe.


>
> - make it real: users and developers will have access to Apache MXNet
> committers and contributors live and can discuss their topics in person
>
OK


>
> - make it scalable: it should be easy for Apache MXNet community members
> to join initiative and host more User Groups meetings on their own schedule
>

Well, we can do something for hosting such in Ukraine - but that is a
pretty good question: why would they go to Ukraine, from nearby countries
(considering that local developers/engineers could be interested by
default)? I as for local attendees - I might assume that they might even be
interested to come to Germany, cause of that (for a week, for instance -
and come to your local office).


>
> - make it fun: there should be minimal process to run User Groups meetings
>

Which would not be supported by Amazon? How do you imagine that?


> Please note this wiki page’s purpose is to introduce and describe
> initiative for Apache MXNet community and seek improvements/changes
> suggestions.


We might provide contributors, for composing this in Russian and Ukrainian,
too.


> User facing document will be separate and will only contain short
> paragraph on what is User Group meetings are and how to participate (see
> above: user should be able to understand it in under 60 seconds).
>

OK, that is predictable.


> There were couple quite successful pilot sessions hosted by group of
> Apache MXNet developers in Berlin. Users clearly likes this channel of
> communication and this initiative is an effort to streamline it for bigger
> user participation.
>

You can improve that by either switching audio/video streaming software -
either using zoom/bluejeans/hangouts/... via round robin or providing
streaming for few services (at once - say, people could chose bet. chime
and zoom). I am able to find sponsors for commercial accounts for such
software - as also as for covering the costs of the hardware setup (within
the MXNet hours hosting location, to stream audio/video online). So those
options would be added to what AWS would support.


> Also, we are looking to add small reference to User Groups meetings into
> Apache MXNet documentation to bring user awareness up.
>

I am running a user group's page on Facebook and could share something on
meetup.com. I could assist.