Alright Sam! Congratulations!
On Wed, Jul 29, 2020, 8:41 PM Kshitij Kalambarkar <
kshitijkalambar...@gmail.com> wrote:
> Congrats Sam! Keep up the great work.
>
> On Thu, 30 Jul, 2020, 8:49 AM Zhang Zhi, wrote:
>
> > Congrats Sam!!
> >
> > -Zhi
> >
> > On Wed, Jul 29, 2020 at 7:30 PM Chen,
Congrats Sam! Keep up the great work.
On Thu, 30 Jul, 2020, 8:49 AM Zhang Zhi, wrote:
> Congrats Sam!!
>
> -Zhi
>
> On Wed, Jul 29, 2020 at 7:30 PM Chen, Ciyong
> wrote:
>
> > Congratulations Sam!
> > Those are great features to MXNet.
> >
> > -Original Message-
> > From: Zhao, Patric
Congrats Sam!!
-Zhi
On Wed, Jul 29, 2020 at 7:30 PM Chen, Ciyong wrote:
> Congratulations Sam!
> Those are great features to MXNet.
>
> -Original Message-
> From: Zhao, Patric
> Sent: Thursday, July 30, 2020 8:40 AM
> To: dev@mxnet.incubator.apache.org
> Subject: RE: [Announcement]
Congratulations Sam!
Those are great features to MXNet.
-Original Message-
From: Zhao, Patric
Sent: Thursday, July 30, 2020 8:40 AM
To: dev@mxnet.incubator.apache.org
Subject: RE: [Announcement] New Committer - Sam Skalicky
Congratulations, Sam, thanks all of your great works in MXNet
Congratulations, Sam, thanks all of your great works in MXNet
> -Original Message-
> From: Chaitanya Bapat
> Sent: Thursday, July 30, 2020 1:12 AM
> To: dev@mxnet.incubator.apache.org
> Subject: Re: [Announcement] New Committer - Sam Skalicky
>
> Congratulations Sam! Well deserved!
>
Thanks for creating the RFC. For readers to understand this issue better, could
you substantiate with the PR example of how onnx_tensorrt updates can break the
MX-ONNX import/export functionalities?
--
You are receiving this because you are subscribed to this thread.
Reply to this email
## Description
ONNX is integrated as a dependency of onnx_tensorrt, which is itself a
dependency (3rd party) of MXNet.
In parallel, ONNX is directly used by MXNet for its import and export
functionalities.
Updating onnx_tensorrt can break the ONNX import/export functionalities.
This is not
Congratulations Sam! Well deserved!
On Wed, 29 Jul 2020 at 08:05, Marco de Abreu
wrote:
> Welcome!
>
> -Marco
>
> On Wed, Jul 29, 2020, 4:58 PM sandeep krishnamurthy <
> sandeep.krishn...@gmail.com> wrote:
>
> > Hello all,
> >
> > Please join me in welcoming Sam Skalicky(@samskalicky) as a new
This is great discussion. Thanks @lanking520 for initiating this. Perhaps we
can define some key metrics here so we can compare the solutions later?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
@saudet Thanks for your reply. Still, I am concerned about the first question:
you mentioned:
> We can go either way, but I found that for contemporary projects like
> Deeplearning4j, MXNet, PyTorch, or TensorFlow that > need to develop
> high-level APIs on top of something like JavaCPP prefer
Welcome!
-Marco
On Wed, Jul 29, 2020, 4:58 PM sandeep krishnamurthy <
sandeep.krishn...@gmail.com> wrote:
> Hello all,
>
> Please join me in welcoming Sam Skalicky(@samskalicky) as a new committer
> of Apache MXNet (incubating)!
>
> Sam has made a number of contributions to this project such as
Hello all,
Please join me in welcoming Sam Skalicky(@samskalicky) as a new committer
of Apache MXNet (incubating)!
Sam has made a number of contributions to this project such as SubGraphs,
Custom Ops, Accelerator APIs, along with several other operator
implementations and bug fixes. Sam has been
12 matches
Mail list logo
