A proposal of supporting dynamic shape and shape symbol

2018-07-19 Thread Zheng, Da
Hello all, As you know, MXNet performs static shape inference to optimize the performance. However, there are cases that the output arrays of an operator can’t be statically inferred. In addition, MXNet doesn’t support shape symbol. For example, the input shape of mx.sym.ones has to be a

Re: A proposal of supporting dynamic shape and shape symbol

2018-07-19 Thread Junru Shao
Hi Da, So excited to see this proposal, it empowers MXNet with the capacity to tackle modern CV/NLP tasks with ease! Vote for it. Thanks, Junru On Thu, Jul 19, 2018 at 7:59 PM Zheng, Da wrote: > Hello all, > > As you know, MXNet performs static shape inference to optimize the > performance.

[RESULT][VOTE] Subscribe dev@ to Github Activities

2018-07-19 Thread Sheng Zha
Hi, The vote concluded at 9PM today (2018/07/18), and here are the results: +1 Timur Shenkao Aaron Markham Lin Yuan Anirudh Acharya Junru Shao Yizhi Liu (committer) Zhi Zhang (committer) Tianqi Chen (committer) Sheng Zha (committer) -1 Qing Lan Rahul Huilgol K, S Anirudh (committer) Chris

Re: Request for feedback: proposal for MXNet SDK Office hours

2018-07-19 Thread Sheng Zha
I'm guessing Mu's intention is to make it clear that such invitation is extended by teams in Amazon/AWS instead of by committers, so as to avoid the confusion of the naming "MXNet SDK". Suggestions to achieve the same goal are welcome. Best regards, -sz On Thu, Jul 19, 2018 at 9:09 AM, Isabel

Invitation: MXNet hangout (I) @ Wed Aug 1, 2018 17:00 - 18:00 (CEST) (dev@mxnet.incubator.apache.org)

2018-07-19 Thread Pedro Larroy
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20180801T15Z DTEND:20180801T16Z DTSTAMP:20180719T164006Z ORGANIZER;CN=Pedro Larroy:mailto:pedro.larroy.li...@gmail.com

Re: Request for feedback: proposal for MXNet SDK Office hours

2018-07-19 Thread Sheng Zha
Thanks. Yeah, I think naming after focused area instead of Amazon internal organization/team names would likely work better. That way, others who'd like to offer help in that area can just jump in and start helping. -sz On Thu, Jul 19, 2018 at 9:51 AM, Pedro Larroy wrote: > There's an MXNet

Invitation: MXNet Hangout (II) @ Thu Aug 2, 2018 14:00 - 15:00 (CEST) (dev@mxnet.incubator.apache.org)

2018-07-19 Thread Pedro Larroy
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20180802T12Z DTEND:20180802T13Z DTSTAMP:20180719T164141Z ORGANIZER;CN=Pedro Larroy:mailto:pedro.larroy.li...@gmail.com

Re: Request for feedback: proposal for MXNet SDK Office hours

2018-07-19 Thread Pedro Larroy
There's an MXNet comitter in our office hours (Marco de Abreu @marcoabreu), others are contributors such as Anton (@lebeg) or others. I think we could refocus the conversation to the point that the office hours might have some emphasis in a particular area of MXNet. On Thu, Jul 19, 2018 at 6:21

Re: Request for feedback: proposal for MXNet SDK Office hours

2018-07-19 Thread Naveen Swamy
I do not think there needs to be a distinction made for support/office-hours by committer or contributors(in this case Amazon employed contributors) -- correct me if I misunderstood your guess :). Like I said, I would rather call it MXNet Office hours and categorize the kind of support that is

Re: Request for feedback: proposal for MXNet SDK Office hours

2018-07-19 Thread Isabel Drost-Fromm
On 18/07/18 23:30, Mu Li wrote: A minor suggestion: rename MXNet SDK to AWS MXNet SDK or Amazon MXNet SDK. What exactly is the Amazon MXNet SDK? What is the AWS MXNet SDK? Your suggestion triggered my question because: https://www.apache.org/foundation/marks/#products Isabel

Re: MXNet developer setup on Mac with VSCode for develop, test and debug

2018-07-19 Thread Anton Chernov
I hope that the instructions will be for cmake soon. After merging this PR [1] there should be not too much problems with the build (considering it's without CUDA). Best Anton [1] https://github.com/apache/incubator-mxnet/pull/11148 чт, 19 июл. 2018 г. в 18:59, Pedro Larroy : > Have you guys

Remove Caffe functionality

2018-07-19 Thread Anton Chernov
Dear community, Currently MXNet has a Caffe framework integration (translator and converter) [1]. There were some issues discovered with it, for example some tests were failing [2]. Since we decided to remove the flaky tests and proceed to making them stable I propose completely removing this

Re: Release plan - MXNET 1.3

2018-07-19 Thread Anirudh Acharya
@sandeep krishnamurthy the bug fixes in the R-package is something we have just begun, there will not be anything significant to announce before the v1.3 code freeze. On Wed, Jul 18, 2018 at 10:08 PM Steffen Rochel wrote: > To make it easier to find the discussions related to project proposals

Re: Remove Caffe functionality

2018-07-19 Thread Mu Li
Hi Anton, It's understandable that Caffe is old and its community is shrinking. For this very reasons, existing caffe users are looking for alternatives. The current converter is important for such users to transit to MXNet. It addresses an important issue that: how I can reuse my previous caffe

Re: MXNet developer setup on Mac with VSCode for develop, test and debug

2018-07-19 Thread Pedro Larroy
Have you guys tried CLion, works like a charm for me. (Requires license). On Wed, Jul 18, 2018 at 10:09 PM Naveen Swamy wrote: > Thanks Sandeep for putting this together, it would make it easy for people > who prefer to IDEs to get started with MXNet easily. > > On Wed, Jul 18, 2018 at 1:04 PM,

Re: Request for feedback: proposal for MXNet SDK Office hours

2018-07-19 Thread Pedro Larroy
Yes Naveen, I think you are saying exactly the same as I hinted. Sheng also agreed with this. Pedro. On Thu, Jul 19, 2018 at 6:54 PM Naveen Swamy wrote: > I do not think there needs to be a distinction made for > support/office-hours by committer or contributors(in this case Amazon > employed

Re: Remove Caffe functionality

2018-07-19 Thread Afrooze, Sina
I think it'd be more sustainable long term to expect users to convert caffe -> caffe2 ->onnx->mxnet rather than caffe->mxnet. Perhaps an MXNet tutorial can show how to do this with minimum pain. - Sina On 7/19/18, 1:27 PM, "Steffen Rochel" wrote: Hi Mu - do we have any indication how

Re: Remove Caffe functionality

2018-07-19 Thread Mu Li
We cannot rely on #issue as a popularity score. No issue means either no one is using it or it's well documented and has no bug. Removing functionality is equivalent to API breaking, we should be very careful about it. I don't suggest the caffe2->onnx approach for 2 reasons: 1. it's

Re: Remove Caffe functionality

2018-07-19 Thread Steffen Rochel
Hi Mu - do we have any indication how many users we do have on the functionality? I see only two github issues from 2017 open. On Thu, Jul 19, 2018 at 12:54 PM Mu Li wrote: > Hi Anton, > > It's understandable that Caffe is old and its community is shrinking. For > this very reasons, existing

Re: Remove Caffe functionality

2018-07-19 Thread Chris Olivier
There’s more production systems still using Caffe 1 than you may realize. While it may be easy for individual developers to move off of Caffe, it will be quite some time before many production systems are off of it, because, as you can imagine, it’s much more difficult to change a live system