Re: Embedded World 2019 Robotics Demo

2019-02-28 Thread Isabel Drost-Fromm
Hi, First of all thank you for the summary, that sounds awesome. Would be great to hear more stories like this shared here - for the stories that can be shared. Am 28. Februar 2019 08:03:38 MEZ schrieb Thomas DELTEIL : >To answer your question Isabel, this project was a joint cooperation >betw

Re: Embedded World 2019 Robotics Demo

2019-02-28 Thread Tsukrov, Stanislav
Guys, that's amazing! Stas On 28.02.19, 09:19, "Isabel Drost-Fromm" wrote: Hi, First of all thank you for the summary, that sounds awesome. Would be great to hear more stories like this shared here - for the stories that can be shared. Am 28. Februar 2019 08:03:38 M

Re: [DISCUSS] Process to remove deprecated operators

2019-02-28 Thread Chaitanya Bapat
This sounds good. Going further, if we can maintain a list of deprecated operators - we can create a "Good for first contribution" issue to improve log messaging of Deprecated operators. If it makes sense, I can go ahead and create that. Hope this helps. On Thu, 28 Feb 2019 at 01:54, Lin Yuan wr

Request for invitation to slack channel

2019-02-28 Thread Bazan, Ivy
I’d like to request an invitation to the #mxnet Slack channel.

Re: Request for invitation to slack channel

2019-02-28 Thread Aaron Markham
I sent you an invite. On Thu, Feb 28, 2019 at 7:11 AM Bazan, Ivy wrote: > > I’d like to request an invitation to the #mxnet Slack channel.

Re: [DISCUSS] Process to remove deprecated operators

2019-02-28 Thread Wen-Yang Chu
Hi, I have raised an issue: mx.nd.Crop does not support FP16 and decpreciated but no direct alternative with central crop I use this operator to implement Unet and I found other people too on the Internent. It is very inconvenient to remove this specific operator withoit clear alternative for me:

Re: [DISCUSS] Process to remove deprecated operators

2019-02-28 Thread Anirudh Acharya
Hi Lin, This is a good idea. Here is an issue - https://github.com/apache/incubator-mxnet/issues/9686 that is already attempting to collate all the breaking changes that might be necessary for v2.0. We could start by adding things to that issue. I think eventually we will need a separate branch i