Re: request for approval to post

[Naveen Swamy]

Welcome to Apache MXNet, added permissions to your handle.


On Tue, Jan 22, 2019 at 2:25 PM Gasparakis, Harris <
harris.gaspara...@amd.com> wrote:

> Hello!
>
> Please allow me to introduce myself, I'm currently AMD's lead/responsible
> party for our MXNet port on AMD's ROCM open source platform. I'm also one
> of ROCM's architects, and also lead AMD's port of CNTK (soon to become
> public) and also TF in the earlier days. In the past I architected and lead
> the OpenCL implementation of opencv.
>
> I'm very excited about participating in the development of mxnet! As I'm
> still getting my feet wet, I was trying to post some comments in the cwiki
> that my team started
>
>
> https://cwiki.apache.org/confluence/display/MXNET/Upstreaming+of+Mxnet+HIP+port
>
> but with no luck.  Presumably I miss permissions?
>
> My handle is harris.gasparakis
> And email is harris.gaspara...@amd.com
>
> Thanks! Appreciate your help!
>

request for approval to post

[Gasparakis, Harris]

Hello!

Please allow me to introduce myself, I'm currently AMD's lead/responsible party 
for our MXNet port on AMD's ROCM open source platform. I'm also one of ROCM's 
architects, and also lead AMD's port of CNTK (soon to become public) and also 
TF in the earlier days. In the past I architected and lead the OpenCL 
implementation of opencv.

I'm very excited about participating in the development of mxnet! As I'm still 
getting my feet wet, I was trying to post some comments in the cwiki that my 
team started

https://cwiki.apache.org/confluence/display/MXNET/Upstreaming+of+Mxnet+HIP+port

but with no luck.  Presumably I miss permissions?

My handle is harris.gasparakis
And email is harris.gaspara...@amd.com

Thanks! Appreciate your help!

Re: Taxonomy on our cwiki

[Sheng Zha]

Thanks, Qing. Plan is in the email. I thought about suggesting a wiki
guideline, but on second thought I think once a good structure is in place,
things would self-organize in that structure, and I don't want to
intimidating people by forcing them to read :)

After experimenting, by using the move tool in cwiki it doesn't seem to
affect edit history or authorship, so I see no reason to bother others.

Given the positive feedback in the last couple of days, I will go ahead
move things around and report back the diff once finished (and I won't
remove or modify content).

-sz

On Tue, Jan 22, 2019 at 10:09 AM Qing Lan  wrote:

> Agreed +1.
> Could we draft a plan on CWIKI and let's sign up our name to migrate the
> pages to the right location?
>
> Thanks,
> Qing
>
> On 1/21/19, 6:18 AM, "Anton Chernov"  wrote:
>
> A quick tip about links to the wiki pages, note the difference in
> links:
>
> * https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> (1)
> * https://cwiki.apache.org/confluence/x/BINjB (2)
>
> If sharing was done via the 'Share' menu the link (2) would persist
> after
> any structual movements.
>
> Best
> Anton
>
>
> сб, 19 янв. 2019 г. в 16:49, Pedro Larroy <
> pedro.larroy.li...@gmail.com>:
>
> > +1
> >
> > On Sat, Jan 19, 2019 at 2:51 PM Zhao, Patric 
> > wrote:
> > >
> > > +1, Good idea.
> > >
> > > It's not very easy to find out the related contents since lots of
> > folders in the website.
> > >
> > >
> > > > -Original Message-
> > > > From: Sheng Zha [mailto:zhash...@apache.org]
> > > > Sent: Saturday, January 19, 2019 3:28 AM
> > > > To: dev@mxnet.incubator.apache.org
> > > > Subject: Taxonomy on our cwiki
> > > >
> > > > Hi MXNet,
> > > >
> > > > Given that currently cwiki is the only place other than mxnet
> website
> > for
> > > > mxnet-related documentation, I'd like to request your attention
> to the
> > > > (slightly disorganized) cwiki page of MXNet. The top level
> folders
> > (and their
> > > > contents) currently looks like this:
> > > > - Design Proposals* (bag of proposals, not in order)
> > > > - Development* (mixture of guides, roadmaps, processes)
> > > > - Release Process (release notes)
> > > > - Website (guides and proposals)
> > > > - MXNet Clojure (call for contribution, guides)
> > > > - MXNet Keras Integration (design)
> > > > - MXNet-ONNX Integration (design, dev status)
> > > > - MXNet R Package (guide, backlog)
> > > > - MXNet-Scala (design, dev status, guide)
> > > > - Content Formatting Templates (not a folder but link to two
> docs)
> > > > - How-to articles (1 guide)
> > > > - Community (guide on apache-related processes)
> > > > - Data IO (designs)
> > > > - Continuous Integration (guides, designs)
> > > > - Meetups and Hangouts (events)
> > > >
> > > > And here are two good examples from successful Apache projects:
> > > > - Apache Flink: an **audience-oriented** structure [1]
> > > >   Users (Presentations and How-to)
> > > >   Contributors (Dev processes and How-to)
> > > >   Committers (Infra, Dev processes, Release processes, Releases)
> > > >   Roadmaps and Feature Designs (archive)
> > > > - Apache OpenNLP: a **content-oriented** structure [2]
> > > >   Guides
> > > >   External Resources
> > > >   Proposals
> > > >   Releasing
> > > >
> > > > Clean organization helps content discovery and saves time on
> locating
> > useful
> > > > content. Given that we have good amount of content on the wiki
> page, I
> > > > suggest that we decide on a cleaner taxonomy, re-organize
> contents
> > > > accordingly, and add future contents accordingly. To provide a
> > starting point
> > > > for the discussion, I suggest:
> > > > - Given the state we are in, start with content-oriented
> organization,
> > use
> > > > these top-level categories: Guides (including processes and
> how-tos),
> > > > Development (including designs, proposals, notes, roadmaps),
> Community
> > > > (including events, activities, external resources and contents)
> > > > - If people strongly prefer audience-oriented structure, later
> we can
> > adopt a
> > > > structure similar to Flink's.
> > > >
> > > > Feel free to share your thoughts and preferences here. Thanks.
> > > >
> > > > -sz
> > > >
> > > > [1]
> > > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/Apache+Flink+Homehttp
> > > > s://cwiki.apache.org/confluence/display/FLINK/Apache+Flink+Home
> > > > [2] https://cwiki.apache.org/confluence/display/OPENNLP/Index
> >
>
>
>

Re: Question about Gluon Api for Scala package & JVM langs

[Carin Meier]

Thanks!

I've heard this from our Clojure community so if anyone else would like to
chime in, please feel free...

One popular Deep Learning book out there is "Dive into Deep Learning"
https://d2l.ai/ -  which has its examples in Gluon. It would be nice as a
starting point in the discussion to see what is covered in there and the
scope/effort it would be to build it out.

I'll help draft a proposal in the next few days.

- Carin

On Tue, Jan 22, 2019 at 1:32 PM Qing Lan  wrote:

> Hi Carin,
>
> Thanks for your question. I would like to know which part(s) of Gluon you
> would like to see for JVM in general?
> Since itself if big, we can start working on the components users needed
> the most and then cover the rest of the part.
> Please feel free to draft a proposal somewhere and we can discuss about it.
>
> Thanks,
> Qing
>
> On 1/21/19, 4:53 PM, "Carin Meier"  wrote:
>
> Currently the Scala package supports the Module and FeedForward APIs.
> Since
> quite a bit of the documentation is focusing now on the Gluon API, I
> wondered if there were thoughts of bringing the Gluon interface to the
> Scala package in the future for the JVM langs.
>
> - Carin
>
>
>

[VOTE] Release Apache MXNet (incubating) version 1.4.0.rc1

[Steffen Rochel]

Dear MXNet community,

This is the vote to release Apache MXNet (incubating) version v1.4.0.
Voting will
start today, January 22nd 2019 noon PST and will close on Friday, January
25th 9pm PST.

Link to release notes:

https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubating%29+
1.4.0+Release+Notes

Link to release candidate:
https://github.com/apache/incubator-mxnet/releases/tag/
1.4.0.rc1


Link to source and signatures on apache dist server:
https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.4.0.rc1


Please remember to TEST first before voting accordingly:
+1 = approve
+0 = no opinion
-1 = disapprove (provide reason)


Best regards,
Steffen

Re: Question about Gluon Api for Scala package & JVM langs

[Qing Lan]

Hi Carin,

Thanks for your question. I would like to know which part(s) of Gluon you would 
like to see for JVM in general?
Since itself if big, we can start working on the components users needed the 
most and then cover the rest of the part. 
Please feel free to draft a proposal somewhere and we can discuss about it.

Thanks,
Qing

On 1/21/19, 4:53 PM, "Carin Meier"  wrote:

Currently the Scala package supports the Module and FeedForward APIs. Since
quite a bit of the documentation is focusing now on the Gluon API, I
wondered if there were thoughts of bringing the Gluon interface to the
Scala package in the future for the JVM langs.

- Carin

Re: [Announce] Runtime feature detection

[Skalicky, Sam]

This is awesome!!!

Great stuff Pedro! 

Is this added to any of the documentation yet?

Sam


> On Jan 22, 2019, at 8:39 AM, Pedro Larroy  
> wrote:
> 
> Hi
> 
> I'm pleased to announce that runtime feature detection has been merged
> in master, thanks to Aaron for the merge and the many reviewers who
> gave feedback on the PR.  (
> https://github.com/apache/incubator-mxnet/pull/13549 )
> 
> As the functionality matures and is exposed through other bindings,
> please feel free to try and use it to build on it, for example for
> easier test suite selection depending on what's compiled in the
> engine.
> 
> Usage examples:
> 
> $ ipython
> In [4]: import mxnet.mxfeatures
> 
> In [5]: mxnet.mxfeatures.features_enabled()
> Out[5]:
> [,
> ,
> ,
> ,
> ,
> ,
> ,
> ,
> ,
> ,
> ]
> 
> In [6]: mxnet.mxfeatures.features_enabled_str()
> Out[6]: 'CPU_SSE, CPU_SSE2, CPU_SSE3, CPU_SSE4_1, CPU_SSE4_2, CPU_AVX,
> F16C, BLAS_OPEN, LAPACK, SIGNAL_HANDLER, DEBUG'
> 
> see also: help(mxnet.mxfeatures)
> 
> Regards.

Re: [ANNOUNCE] Jenkins Nightly Release Pipeline with MXNet Scala

[Qing Lan]

Great work Zach! 
Please reach out to Scala community if you are interested to learn more about 
the nightly build for MXNet Scala.

Thanks,
Qing

On 1/19/19, 8:54 AM, "Carin Meier"  wrote:

Thanks for everyone involved in this effort. This not only is a huge win
for the Scala community but also for the Clojure community which depends on
the Scala jar artifact.

Well done.

On Fri, Jan 18, 2019 at 9:58 PM Zach Kimberg 
wrote:

> Hi,
>
> A little over a month ago, we announced the nightly build of the Scala
> package on Nexus [1]. It featured the same statically linked binary build
> logic used by the Python pip to make the adoption as easy for our JVM 
users
> as for our python users. However, that release occurred on a private
> pipeline using code that was not publicly available.
>
> First, I would like to thank Sheng for contributing the pip binary build
> scripts to the community and making them accessible as part of the MXNet
> repository [2]. Now, everyone can produce similar published artifacts for
> their own needs and we can better verify the release production code as
> part of the Jenkins CI.
>
> Using his contribution, we have created a new job on the MXNet Jenkins for
> publishing artifacts on a nightly basis [3]. In order to ensure the 
highest
> quality for our releases regardless of user system, it will automatically
> test the artifacts across other distributions including Ubuntu 16.04,
> Ubuntu 18.04, and CentOS 7 as part of the deployment.
>
> You can find the code for the nightly publish pipeline on the repo [4]. We
> hope that others can work off of this pipeline to help expand the same
> static building and thorough testing to additional MXNet packages and
> language bindings in the future.
>
> Special thanks to Qing for his help throughout the project, Sheng for the
> binary build logic, Marco for his reviews and support working with 
Jenkins,
> Anton for setting up the development Jenkins for us, and Frank and Naveen
> for work on the Scala maven build and deployment.
>
> Zach
>
> [1] - https://repository.apache.org/#nexus-search;quick~org.apache.mxnet
> [2] -
> https://github.com/apache/incubator-mxnet/tree/master/tools/staticbuild
> [3] -
>
> 
http://jenkins.mxnet-ci.amazon-ml.com/job/restricted-publish-artifacts/job/master/
> [4] - https://github.com/apache/incubator-mxnet/tree/master/ci/publish
>

Re: Taxonomy on our cwiki

[Qing Lan]

Agreed +1. 
Could we draft a plan on CWIKI and let's sign up our name to migrate the pages 
to the right location?

Thanks,
Qing

On 1/21/19, 6:18 AM, "Anton Chernov"  wrote:

A quick tip about links to the wiki pages, note the difference in links:

* https://cwiki.apache.org/confluence/display/MXNET/Release+Process (1)
* https://cwiki.apache.org/confluence/x/BINjB (2)

If sharing was done via the 'Share' menu the link (2) would persist after
any structual movements.

Best
Anton


сб, 19 янв. 2019 г. в 16:49, Pedro Larroy :

> +1
>
> On Sat, Jan 19, 2019 at 2:51 PM Zhao, Patric 
> wrote:
> >
> > +1, Good idea.
> >
> > It's not very easy to find out the related contents since lots of
> folders in the website.
> >
> >
> > > -Original Message-
> > > From: Sheng Zha [mailto:zhash...@apache.org]
> > > Sent: Saturday, January 19, 2019 3:28 AM
> > > To: dev@mxnet.incubator.apache.org
> > > Subject: Taxonomy on our cwiki
> > >
> > > Hi MXNet,
> > >
> > > Given that currently cwiki is the only place other than mxnet website
> for
> > > mxnet-related documentation, I'd like to request your attention to the
> > > (slightly disorganized) cwiki page of MXNet. The top level folders
> (and their
> > > contents) currently looks like this:
> > > - Design Proposals* (bag of proposals, not in order)
> > > - Development* (mixture of guides, roadmaps, processes)
> > > - Release Process (release notes)
> > > - Website (guides and proposals)
> > > - MXNet Clojure (call for contribution, guides)
> > > - MXNet Keras Integration (design)
> > > - MXNet-ONNX Integration (design, dev status)
> > > - MXNet R Package (guide, backlog)
> > > - MXNet-Scala (design, dev status, guide)
> > > - Content Formatting Templates (not a folder but link to two docs)
> > > - How-to articles (1 guide)
> > > - Community (guide on apache-related processes)
> > > - Data IO (designs)
> > > - Continuous Integration (guides, designs)
> > > - Meetups and Hangouts (events)
> > >
> > > And here are two good examples from successful Apache projects:
> > > - Apache Flink: an **audience-oriented** structure [1]
> > >   Users (Presentations and How-to)
> > >   Contributors (Dev processes and How-to)
> > >   Committers (Infra, Dev processes, Release processes, Releases)
> > >   Roadmaps and Feature Designs (archive)
> > > - Apache OpenNLP: a **content-oriented** structure [2]
> > >   Guides
> > >   External Resources
> > >   Proposals
> > >   Releasing
> > >
> > > Clean organization helps content discovery and saves time on locating
> useful
> > > content. Given that we have good amount of content on the wiki page, I
> > > suggest that we decide on a cleaner taxonomy, re-organize contents
> > > accordingly, and add future contents accordingly. To provide a
> starting point
> > > for the discussion, I suggest:
> > > - Given the state we are in, start with content-oriented organization,
> use
> > > these top-level categories: Guides (including processes and how-tos),
> > > Development (including designs, proposals, notes, roadmaps), Community
> > > (including events, activities, external resources and contents)
> > > - If people strongly prefer audience-oriented structure, later we can
> adopt a
> > > structure similar to Flink's.
> > >
> > > Feel free to share your thoughts and preferences here. Thanks.
> > >
> > > -sz
> > >
> > > [1]
> > >
> https://cwiki.apache.org/confluence/display/FLINK/Apache+Flink+Homehttp
> > > s://cwiki.apache.org/confluence/display/FLINK/Apache+Flink+Home
> > > [2] https://cwiki.apache.org/confluence/display/OPENNLP/Index
>

Re: [Article] Object Detection with Clojure MXNet

[Qing Lan]

That looks cool! So glad to see the active community of Clojure.
BTW, Piyush (piyushghai) plans to add the bounding box support for Scala this 
week.

Thanks,
Qing

On 1/20/19, 7:29 AM, "Carin Meier"  wrote:

Thanks - props for the images belongs to the original Scala article

https://medium.com/apache-mxnet/object-detection-with-mxnet-scala-inference-api-9049230c77fd
and Kedar - the contributor that ported the object detection feature to
Clojure. They are pretty awesome though.



On Sat, Jan 19, 2019 at 4:57 PM Marco de Abreu 
wrote:

> Great article! I have to admit I always love your picture choices :D
>
> -Marco
>
> Am Sa., 19. Jan. 2019, 21:57 hat Carin Meier 
> geschrieben:
>
> > I just blogged about the new Object Detection feature that was just
> ported
> > from the Scala package into the Clojure package.
> >
> >
> 
http://gigasquidsoftware.com/blog/2019/01/19/object-detection-with-clojure-mxnet/
> >
> > I posted it in Slack but in an effort to direct more communication
> towards
> > this mailing list, I'm putting it out here too :)
> >
> > - Carin
> >
>

[Announce] Runtime feature detection

[Pedro Larroy]

Hi

I'm pleased to announce that runtime feature detection has been merged
in master, thanks to Aaron for the merge and the many reviewers who
gave feedback on the PR.  (
https://github.com/apache/incubator-mxnet/pull/13549 )

As the functionality matures and is exposed through other bindings,
please feel free to try and use it to build on it, for example for
easier test suite selection depending on what's compiled in the
engine.

Usage examples:

$ ipython
In [4]: import mxnet.mxfeatures

In [5]: mxnet.mxfeatures.features_enabled()
Out[5]:
[,
 ,
 ,
 ,
 ,
 ,
 ,
 ,
 ,
 ,
 ]

In [6]: mxnet.mxfeatures.features_enabled_str()
Out[6]: 'CPU_SSE, CPU_SSE2, CPU_SSE3, CPU_SSE4_1, CPU_SSE4_2, CPU_AVX,
F16C, BLAS_OPEN, LAPACK, SIGNAL_HANDLER, DEBUG'

see also: help(mxnet.mxfeatures)

Regards.