Re: Profiler Broken?

:07 PM Pedro Larroy wrote: > Yes the profiler seems to be broken / has some concurrency issues. I have > seen corrupted profile results. > > On Thu, May 28, 2020 at 12:30 PM Naveen Swamy wrote: > > > I am attempting to profile one of our models, I used the profiler.state >

Profiler Broken?

I am attempting to profile one of our models, I used the profiler.state to run/stop in code and also used the environment variables to autostart the profiler. It creates a 600MB json file, however when I view in chrome tracing it comes out to be blank screen (loading seems to be fine, didn't get

Re: Using AMP

is together with other changes intended to bring AMP > out of contrib. > > > > Regarding performance - it is quite hard to say what is the reason of > this without profiling the application - there could be multiple different > bottleneck here, other than the actual computation on the

Using AMP

Hello, I am trying to use AMP on an RNN Model, however I am not seeing higher throughputs using AMP. also the loss seems to have stagnated. I am wondering if I am missing something. Also has AMP has been tested on any RNN models and if there are any benchmarks ? Appreciate some input here.. I

[ANOUNCEMENT] New PPMC Member Thomas DELTEIL

Hi all, Please join me in welcoming Thomas Delteil as a new member of Apache MXNet (incubating) PPMC! Thomas has contributed to various areas of Apache MXNet being an evangelist he has created many learning materials for MXNet, engaged with contributions on PRs and Users on the forum (he is the

Re: [DISCUSS] Remove amalgamation

so the original email suggesting to remove was after all self-serving :) let's encourage if someone wants to maintain and make use of the original work and make it better. -1 to remove at this point P.S: I suggest to do some due diligence before bringing topics up for discussion. On Wed, Sep

Re: [DISCUSS] Remove amalgamation

+1. I have heard this before elsewhere if you don't understand the code, give it a name like "hacky", "does not follow the pattern", "unmaintainable", etc., may all that be true but it does not help making cliched and disrespectful comments about someone else's contributions. the code is not

Re: [Discuss] Experiment Reproducibility in MXNet

Look at https://mlflow.org/ > On Sep 2, 2019, at 7:02 PM, Chaitanya Bapat wrote: > > Hello MXNet community, > > Reproducibility of ML experiments carried out by data scientists, analysts > and experts is the talk of the town. > > While listening to TWiML's latest podcast - Managing Deep

[ANNOUNCEMENT] New Committer: Przemyslaw Tredak (ptrendx)

The Project Podling Management Committee (PPMC) for Apache MXNet has invited Przemyslaw Tredak (ptrendx) based on his contribution to MXNet to become a committer and we are pleased to announce that he has accepted. Przemyslaw, thanks a lot for your contribution and continued effort to support

Re: [Proposal] New operator graph for MXNet

Being dismissive and condescending has been exactly what is plaguing this project. I agree the last paragraph sounds very condescending and very dismissive and it breaks many code of conducts listed. On Wed, May 15, 2019 at 11:31 AM Anirudh Subramanian wrote: > Hi Junru, > > Overall, I

Re: [Proposal] MXNet operator benchmark library

Sandeep, Thanks for initiating work on individual operator performance. However I find the proposed approach(ie., a separate libary/framework) to unnecessary and increases maintenance overhead for the project. Also, have you considered alternate approaches to achieve the same goal.? Many of the

Re: Unable to comment on GitHub issue

locked as off topic and limited conversation to > > > collaborators 24 seconds from now > > > > > > Then to the right of that: > > > > > > Unlock conversation > > > Pin issue > > > > > > On Thu, May 9, 2019 at 4:27 PM Nav

Re: Unable to comment on GitHub issue

l probably have the > ability to unlock it from there too. > >> On Thu, May 9, 2019 at 3:42 PM Chaitanya Bapat wrote: >> >> Any specific issues you could give the links to? So I could verify if >> that's the case with me. >> >>> On Thu, 9 May 2019 at 14:44, Nav

Unable to comment on GitHub issue

I am unable to comment on certain GitHub issues and see a locked Icon, wondering if anyone has experienced this and know why?

Re: Requesting slack access

done. Welcome to Apache MXNet. On Sat, Mar 30, 2019 at 2:44 PM Luyang Wang wrote: > >

Re: Gluon fit API- Design proposal

es, which can make MXNet/Gluon even more friendly to so-called "deep > learning beginners" - so +1 on the proposal! > > Hagay > > On Fri, Feb 8, 2019 at 10:30 AM Naveen Swamy wrote: > > > Hi Alfredo, > > Thanks for your comments, I really like all your suggesti

Re: [DISCUSS] Process to remove deprecated operators

It might be a good idea to issue those deprecation messages right away if have replacement operators already, so users get enough time to migrate to the new operators. On Thu, Feb 28, 2019 at 2:45 PM Anirudh Acharya wrote: > Hi Lin, > > This is a good idea. Here is an issue - >

MXNet Meetups

A user driven meetup in Copenhagen on April 4th, if any of you are in the area. check it out a) Introduction to Gluon NLP & CV and ONNX b) MXNet to ONNX to ML.NET [1] Thanks Cosmin for your passion to MXNet, organizing and leading the meetup group. Another Meetup today in Palo Alto, Deep

Re: Help with the Clojure release jars

. > > Let me know if this is what we want to do and I will kick off the process. > > -Carin > >> On Sun, Feb 24, 2019 at 6:39 PM Naveen Swamy wrote: >> >> Did you close the repo? In my understanding, the repo(*.Apache.org) is >> under infra's control, s

Re: Help with the Clojure release jars

Did you close the repo? In my understanding, the repo(*.Apache.org) is under infra's control, so we porbably have to create a infra ticket, last time I wasn't able to delete( luckily it was in staging, so I abandoned and released to staging again.) > On Feb 24, 2019, at 2:36 PM, Carin Meier

Re: Wiki Access for Kedar Bellare

i added kedar, i updated your id to have admin access. On Sun, Feb 24, 2019 at 10:43 AM Carin Meier wrote: > Can someone please help Kedar get write access to our wiki? I don't have > that access. He is taking the lead on the next generation of our Clojure > package NDArray and Symbol APIs [1]

Re: Gluon fit API- Design proposal

Hi Alfredo, Thanks for your comments, I really like all your suggestions. Here are my answers let me know if it makes sense or have comments. 1) The fit API is targeting novice users covering about 80% of the use cases listed in the document. For advanced users, and complex models, we (Naveen,

Re: request for approval to post

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.

Re: Jira board and Confluence page for Julia

/users/viewuserprofile.action?username=iblis > And Jira account: > https://issues.apache.org/jira/secure/ViewProfile.jspa?name=iblis > > Both of these accounts predate my apache account. > (Are there any processes of linking them?) > > Iblis Lin > 林峻頤 > > On 1/15/19 2:55 AM, Nave

Re: [DISCUSS] Make MKLDNN as a default on Maven nightly build

Thanks for bringing this up. I think it would be less confusing for users if we keep it same across language bindings? What needs to be done to python, Java, Clojure, etc., ? If they are not getting this default, any reason? On Mon, Jan 14, 2019 at 10:56 AM Qing Lan wrote: > Hi all, > > I would

Re: Jira board and Confluence page for Julia

Ibis, Confluence needs its own user name/password. Once you have let us know, one of us should be able to grant access. For JIRA, I am not an expert at it, I think it uses Apache Login, i'll find you and add appropriate permissions, I was able to create a board for Scala, the board also needs to

Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc0

+1 Verified Signatures Downloaded source from dist server and Tested Scala Package on Linux CPU/ On Fri, Dec 21, 2018 at 11:21 AM Carin Meier wrote: > +1 (binding) - Tested on OSX with Clojure/Scala package > > On Thu, Dec 20, 2018 at 12:25 PM Steffen Rochel > wrote: > > > Dear MXNet

Re: Malformed package uploaded to Maven central

gt; which point to https://repository.apache.org/content/repositories/releases > > Thanks, > Frank > > On Fri, Dec 21, 2018 at 9:59 AM Naveen Swamy wrote: > > > Hi Qing, > > > > Thanks for bringing this to the attention of the community. I understand >

Re: Malformed package uploaded to Maven central

Hi Qing, Thanks for bringing this to the attention of the community. I understand it was an unintended consequences of publish experiment. I will raise a INFRA ticket to remove this package from the releases repo. Could you please file a GitHub issue or MXNet JIRA and mention the commands you

Re: [DISCUSS] About the usage of CUDA/CUDNN

Attempting to answer Qing's question -- If you can digest the legal terms: https://docs.nvidia.com/cuda/eula/index.html#distribution-requirements. It sounds its OK(" 1. Your application must have material additional functionality, beyond the included portions of the SDK.") but I not don't

Re: Include MKLDNN into default mxnet pip package

Great effort Alex and also folks from Intel. +1 to make MKLDNN default. On Tue, Dec 11, 2018 at 9:10 AM Kumar, Vikas wrote: > +1 > > On 12/10/18, 8:01 PM, "Zhao, Patric" wrote: > > +1, thanks for the efforts, Alex. > > > > > -Original Message- > > From: Alex Zai

Re: Scala standard library is included in the mxnet jar

Pedro, Not everyone has Scala installed on their system, especially for example they are Java/Clojure users(and they don't have to). I don't expect them to download/install Scala libraries. IMO, this approach is correct and lowers the entry bar for users. Soon, we are going include all

Re: CI impaired

catalogue, which means that all PRs > > have to be analyzed with the new pipelines - the only thing that will be > > noticeable is that the CI is under higher load. > > > > The pending PRs will not be impacted. The existing pipeline is still > > running in parallel and everything will be

Re: CI impaired

There are still pending PRs pending that needs to be merged and cherry picked to the branch > On Nov 30, 2018, at 6:53 AM, Marco de Abreu > wrote: > > Hello, > > I'm now moving forward with #1. I will try to get to #3 as soon as possible > to reduce parallel jobs in our CI. You might notice

Re: [Announce] Upcoming Apache MXNet (incubating) 1.4.0 release

the tests are randomly failing in different stages http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-13105/ This PR has failed 8 times so far On Thu, Nov 29, 2018 at 3:43 PM Steffen Rochel wrote: > Pedro - ok. Please add PR to v1.4.x branch after merge

Re: Include MKLDNN into default mxnet pip package

gt; period of MKL-DNN and MXNet are not matched very well. I think it would be > a risk for MXNet release if it hardly depends on the release of a > submodule, no need to say depends on the releases of all submodules. > > -tao > > -Original Message- > From: Naveen Swamy

[ANNOUNCEMENT] New Committer: Qing Lan

The Project Podling Management Committee (PPMC) for Apache MXNet has invited Qing Lan based on his contribution to MXNet Scala to become a committer and we are pleased to announce that he has accepted. Qing, thanks a lot for your contribution and continued effort to support MXNet community.

Merging java-api Branch

Hi All, Just wanted to let you know that the work for MXNet Java-API was done on the 'java-api' branch and contributed by multiple contributors, I merged the PR[1] and later realized that the squash/merge credited all code contribution to one contributor. we are going to revert the commit and

Re: [Question] Difference between "Feature" and "Feature request" labels in Github

done now, removed the feature label, there were 4 issues with that label but also had Feature Request. On Tue, Nov 13, 2018 at 5:05 PM Anirudh Acharya wrote: > This issue was raised before here - > >

Re: [Question] Difference between "Feature" and "Feature request" labels in Github

there were a few more that had 'Feature' as label but didn't show up in the filter search, I manually applied the `Feature Request` on them On Tue, Nov 13, 2018 at 5:12 PM Naveen Swamy wrote: > done now, removed the feature label, there were 4 issues with that label > but also had F

Re: Nightly/Weekly tests for examples

Aaron, IMO tutorials have a specific purpose, to introduce concepts and APIs to the users and I think converting examples to tutorials would overwhelm the users, we should carefully choose which examples we want to turn into tutorials. I agree that today examples are graveyard of untested code,

Re: LabelBot New Design in Production

Great job!, this is very helpful to triage issues!, users when creating a new Issue could themselves tag the issues. May be we should add that to the issue template? On Thu, Nov 8, 2018 at 3:54 PM Harsh Patel wrote: > Hey all, > The upgraded label bot has been pushed into production. Current >

Re: [Announce] Upcoming Apache MXNet (incubating) 1.3.1 patch release

Anton, I don't think we need to add the Mac OS tests for 1.3.1 branch since travis CI is timing out and creates blockers, it also did not exist for v1.3.0. On Thu, Nov 8, 2018 at 10:04 AM Anton Chernov wrote: > A PR to fix the tests: > > Remove test for non existing index copy operator

Re: [Announce] Upcoming Apache MXNet (incubating) 1.3.1 patch release

Please note that this is a patch release(1.3.1) to address critical bugs!, For everything else please wait for 1.4.0 which is planned very shortly after 1.3.1 > On Nov 6, 2018, at 7:17 AM, Anton Chernov wrote: > > The following PR's have been created so far: > > Infer dtype in SymbolBlock

Apache MXNet Workshop in ODSC

Hey guys, I wanted to let you know that I and Sandeep conducted a Hands on workshop in ODSC, SF on November 1st, I conducted a similar session in London last month. This session had 30 attendees join us and the response was positive and engaging especially for the fact that they could try out

Re: [VOTE] - Adopt "Become a Committer and PPMC Member" Document

+1 Thanks everyone for your input and participation. Thanks to Carin for driving this. > On Nov 1, 2018, at 6:07 AM, Carin Meier wrote: > > Reminder - vote ends tomorrow morning at 6:00 am EST > >> On Mon, Oct 29, 2018 at 6:46 PM Carin Meier wrote: >> >> This vote is to adopt the document

Re: [VOTE] - Adopt "Become a Committer and PPMC Member" Document

the ML models, every guideline can be interpreted in an >> adversarial fashion but I hope we can have a goodwill to build toward a >> positive sum collaboration. >> >> Tianqi >> >> >> >>>> On Mon, Oct 29, 2018 at 9:01 PM Naveen Swamy wrote: >

Re: [VOTE] - Adopt "Become a Committer and PPMC Member" Document

The committer/PMC privileges is derived from https://www.apache.org/foundation/how-it-works.html. The term abuse is very subjective (in this case) - If an opinion or Vote is against something they prefer, it can be termed as Abuse. I would expect those who differ with the vote to take that as

Re: [VOTE] - Adopt "Become a Committer and PPMC Member" Document

May be we can adopt this. https://struts.apache.org/bylaws.html#voting > On Oct 29, 2018, at 5:52 PM, Carin Meier wrote: > > Chris, > > Is there are rewording that you would find more acceptable? Again, we can > have more time to edit and revise the document. There is not a time limit > on

Re: [DISCUSS] - Revisions to Committer Criteria

I added clarifying sections to explicitly call out committers/PMC privileges. Please review. Pasting here for convenience Committer Privileges - Committers have write access to the code repository. - Committers have an @apache.org email address. - Committers can make short-term

Re: Join mxnet Slack

Hi Piston, Welcome to MXNet! Feel free to browse through our docs meant for developers here https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+Home and let us know if you have any questions or feedback Thanks, Naveen On Wed, Oct 24, 2018 at 8:54 AM Piston Yang wrote: > Hi, I’m a

MXNet Meetup Group in Copenhagen

One of MXNet's user Cosmin has started a Meetup group in Copenhagen, interested and those living around the area please sign up https://www.meetup.com/meetup-group-bdEUVQHL/ Thanks, Naveen

Re: [Discussion] PMC and Committer Courtesy: Only Propose Candidate in a Different Organization

this suggestion looks like it is putting the onus on contributors to collaborate with contributors outside their org to get nominated to be committer or a PMC of this project. Every organization has its own business goals, on the way to meet their objectives if their employees happen to be great

Re: [Discussion] Recognise Reviewers, Besides Committers and PMC

+1 reviews are great contributions given that it takes good understanding and investment of time to provide insightful feedback. On Fri, Oct 19, 2018 at 11:51 AM Tianqi Chen wrote: > Dear MXNet Community: > > There is a great discussion going on in terms of lowering the barrier of > entries and

Re: [Discussion] Separating PMC and Committership

I suggest we discuss on what the revised criteria for committers will be and how do committers move up to become a PMC member before voting on the separation ? I would like to see if that helps grow the community before Voting on this. @Chris Olivier Can you clarify what you mean by bonafide

Storing PGP Key for Publishing packages

I am collaborating with Zach Kimberg and Qing to work on automatic ( currently its very tedious and time consuming) publishing the MXNet-Scala maven package to Apache Snapshot repo(either as nightly or weekly), for publishing the package the artifacts need to be signed with a committer's key,

Re: [LAZY VOTE]: rename dockerfiles s/.build.//

I agree with Kellen on not renaming the CI docker files (by renaming - i think its implicit you can use these for production) i don't think we should telling our users go use these bloated docker files, you could create lean separate docker files for production use-case with only necessary runtime

Re: Creating branch for Java_API

//jenkins.mxnet-ci.amazon-ml.com/job/incubator-mxnet/job/java-api/ > > > > This will be the normal build with the main Jenkinsfile. I'm not sure > about > > the triggering for new commits though... > > > > Best > > Anton > > > > > > пн,

Re: Reproducing test failures on CI

Timur, Here is a meetup Scheduled for 23rd October in London, where Pedro Larroy will talk about Deep Learning using MXNet! https://www.meetup.com/Deep-Learning-with-Apache-MXNet-London/events/255280739/ -Naveen On Mon, Oct 15, 2018 at 11:18 AM Anton Chernov wrote: > Sorry, Timur, I've

Re: Creating branch for Java_API

job for testing it, maybe with a tweaked > Jenkinsfile so you could run only the tests you are interested in. What do > you think? > > Best > Anton > > пт, 12 окт. 2018 г. в 20:24, Naveen Swamy : > > > Hi All, > > > > Just wanted to inform there that I am going

Creating branch for Java_API

Hi All, Just wanted to inform there that I am going to create a branch on GitHub for the Java API work that Andrew/Qing and few others are doing. This is only temporary I realize this will not have testing. There seems to be continued disagreement in the approaches we are taking(which is fine),

Re: [Discussion] Separating PMC and Committership

Thanks for bringing up here. I think this topic and suggestions should be a little more concrete by clarifying the difference between the role of committer and PMC member. Based on my understanding of here are my comments and concerns 1) I agree we need to bring more committers into the project,

Re: Create a Jira board for C/C++ API project

Thanks for making the effort to bring tasks and feature improvements under a managed boards in JIRA. This will help in users/contributors to quickly look through the stories/tasks and contribute to the project that they are interested in. We were able to create JIRA boards/filter and share it

Re: CUDNN algorithm selection failure

Looking at the error raised, you can see that the workspace size(GPU mem size) of 1GB isn't sufficient. I am wondering if it is due to tests running in parallel on CI, if this is true(tests running in parallel) is it possible to reduce the parallelism ? Error: "mxnet.base.MXNetError: [05:40:12]

Re: Subscription

Invited On Mon, Oct 1, 2018 at 12:39 PM Jim Jagielski wrote: > I'd like an invite as well, please :) > > > On Sep 29, 2018, at 12:03 PM, Naveen Swamy wrote: > > > > Invite sent. Welcome to Apache MXNet Cosmin :). > > > > > > On Sat, Sep

Re: Feedback request for new Java API

;> > >> Back to the problem, they are unnecessary but good in terms of, > >> 1. Still not good for java users to write 3 nulls in a function > call with 5 > >> or 4 args > >> 2. Every function call with a “tail” null for arg “out”. I would &

Re: Feedback request for new Java API

having all of them have Builder?" > > On Sat, Sep 29, 2018 at 7:30 PM Naveen Swamy wrote: > > > > > > I think we have had enough of an debate between the two of us and I > have > > > already listed my reasons, I will stop here and see what others say >

Re: Feedback request for new Java API

; operators have Builder, what prevents from > having all of them have Builder?" > On Sat, Sep 29, 2018 at 7:30 PM Naveen Swamy wrote: > > > > I think we have had enough of an debate between the two of us and I have > > already listed my reasons, I will stop here and see

Re: Feedback request for new Java API

us. And won't have any performance issue > > on modern JVM. > > > > Just remind, technical discussion is not about who gives who a lecture. > > On Sat, Sep 29, 2018 at 6:41 PM Naveen Swamy wrote: > > > > > > Well, I am not sure(I don't think)

Re: Feedback request for new Java API

se? 200+ classes is a very tiny increasing in file size > > (~3MB) compare to current status. And won't have any performance issue > > on modern JVM. > > > > Just remind, technical discussion is not about who gives who a lecture. > > On Sat, Sep 29, 2018 at 6:41 PM Nave

Re: [DISCUSS] Use modernized C++11 range loops uniformly throughout the project

MO it also leads to better naming in loop > >> bodies > >> as the concise style means you're less likely to have important 1 letter > >> variable names describing loop elements (e.g. no int i =0 or it ...). > >> More > >> motivation can be found

Re: Which merge option to use on the Import Julia binding PR?

> originally >> > > > > ruled it out since it wasn't an option in the github web >> interface, >> > but >> > > > > since this looks like it is going to have to be done outside it >> > because >> > > > of >> > &g

Re: Feedback request for new Java API

Scala code to work for APIs so your users know what to expect(uniform experience across). > 8) Also, the discussion is not creating NDArray class for Java, just > generate certain APIs to cater for Java incompatibility. > - Yes I agree it's about "generate certain APIs to cater for Java &

Re: Feedback request for new Java API

(data).setGamma(gamma).setBeta(beta).invoke(); > > I don't think any of the reasons you listed is so important as the > benefit above we got from option #2. >> On Sat, Sep 29, 2018 at 8:24 AM Naveen Swamy wrote: >> >> Java APIs are not like Clojure - The current propos

Re: [DISCUSS] Use modernized C++11 range loops uniformly throughout the project

Kellen, Could you please explain why you think range loops are better and how it improves readability? this is a relatively new feature, many of them are used to the old syntax, shouldn't we leave it for the developers to choose the one that best suits the need and their familiarity. In general

Re: Subscription

Invite sent. Welcome to Apache MXNet Cosmin :). On Sat, Sep 29, 2018 at 11:38 AM Cosmin Cătălin Sanda < cosmincata...@gmail.com> wrote: > Hi, I would like to subscribe to the ASF mxnet channel. > > *Cosmin Catalin SANDA* > Data Scientist & Engineer > Phone:

Re: Feedback request for new Java API

Java APIs are not like Clojure - The current proposal is only to build a few thin wrappers for Inference. To better represent the two cases and this discussion in particular, here is an example API 1) def Activation (data : org.apache.mxnet.NDArray, act_type : String, out : Option[NDArray] =

Re: Which merge option to use on the Import Julia binding PR?

on. >>> >>> Best, >>> Chiyuan >>> >>>> On Thu, Sep 27, 2018 at 7:34 AM Jason Dai wrote: >>>> >>>> +1 to rebase and merge to preserve and track the contributions. >>>> >>>> Thanks, >>>> -Jason &g

Re: Requesting slack access

Invite sent. Welcome to Apache MXNet, we have a forum for questions related to MXNet https://discuss.mxnet.io/ and in-depth tutorial on getting started with MXNet https://gluon.mxnet.io/, feel free to ask questions On Thu, Sep 27, 2018 at 12:04 AM, Rahul Padmanabhan <

Re: Which merge option to use on the Import Julia binding PR?

this PR comes from more than 1 individual, if we squash merge we'll not be able to attribute the contribution of those individuals. +1 to rebase merge to preserve history On Thu, Sep 27, 2018 at 12:04 AM, Tianqi Chen wrote: > One of the main reason for a rebase merge is that it preserves the

Re: Remove MKLML as dependency

if MKLDNN is a replacement for MKL and MKLML (which is my understanding) may you guys should bring in the necessary functions into MKLDNN instead of letting the users go through this nightmare of a setup. On Thu, Sep 20, 2018 at 6:01 PM, Lv, Tao A wrote: > " MKLML does not have a complete blas

Re: Some feedback from MXNet Zhihu topic

Qing, this is so loaded and very specific suggestions. Thank you for bringing up here, since Apache MXNet is popular in China, It would be great if Mandrin speaking developers here could bring such feedback and user pain to the community's attention. 1. To capture specific API/Example/Tutorial

Re: multiple installation guides?

Amol, do you want to post this on discuss.mxnet.io ? > On Sep 19, 2018, at 4:34 AM, Hagay Lupesko wrote: > > The /test site seems to be something old that should have been removed a > long time ago, it lists versions 0.10 and 0.10.14 :) > Maybe Aaron has an idea what needs to be done to remove

Re: MXNet Slack Channel

invited. welcome to MXNet. On Fri, Sep 14, 2018 at 1:55 PM, Denver McNeney wrote: > Hello, > > I’d like to be added to the MXNet Slack channel! > > Thanks, > > Denver

Re: Requesting slack access

done, welcome back. On Thu, Sep 13, 2018 at 12:57 AM, shiwen hu wrote: > please add me to slack >

Re: Requesting slack access

done. On Wed, Sep 12, 2018 at 11:09 AM, Chaitanya Bapat wrote: > Hello, > > Chaitanya here. Requesting slack access. > Thanks > > -- > *Chaitanya Prakash Bapat* > *+1 (973) 953-6299* > > [image: https://www.linkedin.com//in/chaibapat25] > [image:

Re: Off-Heap Memory Management in MXNet Scala

, 2018 at 6:06 AM, Carin Meier wrote: > Naveen, > > Thanks for putting together the detailed document and kickstarting this > effort. It will benefit all the MXNet JVM users and will help solve a > current pain point for them. > > - Carin > > On Tue, Sep 11, 2018 at

Re: Error Publishing OSX package to Maven

the artifacts(generated through maven release prepare/perform) to the Staging repo so we can make it available for OSX users. This issue needs to be investigated independently. -Naveen On Tue, Sep 11, 2018 at 2:03 PM, Naveen Swamy wrote: > that seems reasonable. I also asked this question o

Off-Heap Memory Management in MXNet Scala

Hi All, I am working on managing Off-Heap Memory Management and have written a proposal here based on my prototype and research I did. Please review the doc and provide your feedback ? https://cwiki.apache.org/confluence/display/MXNET/JVM+Memory+Management I had offline discussion with a few

Re: Error Publishing OSX package to Maven

ng. I would recommend timeboxing the > effort and if it is going to take more effort to investigate, we can go > with announcing later for OSX. > > > - Carin > > On Tue, Sep 11, 2018 at 2:10 PM Naveen Swamy wrote: > > > hey all, > > > > I am working on p

Error Publishing OSX package to Maven

hey all, I am working on publishing the 1.3.0 Scala package to Maven and encountering a error when I am about to Close the Repo on Nexus. When I publish the OSX package to Staging, the artifacts gets split into 2 repositories and when I close[1] the repo(to make it available for use) it fails

Re: [VOTE] Release MXNet version 1.3.0.RC0

+1 Roshani/Sheng, Thanks for putting this release together, I was able to test the release only now. As Kellen indicated this release does not have enough committer votes, I suggest you extend the timeline. I downloaded the source code from

Re: [VOTE] Release MXNet version 1.3.0.RC0

"Releases may not be vetoed" http://www.apache.org/legal/release-policy.html#release-approval I haven't tested the release yet, I'll do so tomorrow. > On Sep 4, 2018, at 7:13 PM, Sheng Zha wrote: > > Thanks for sharing your opinions, Thomas. Your recognition and respect of > people's efforts

Re: New Java Inference API

this proposal is missing many of the offline discussions that happened and subsequent changes. @andrewfayres: Please update the wiki(may be you forgot to publish the changes) On Tue, Sep 4, 2018 at 11:11 AM Qing Lan wrote: > Hi All, > > Here is an update for the Java Inference API design doc

Re: Propose to discontinue supporting Apache MXNet on Windows 7

+1 to stop supporting Win7 On Tue, Aug 28, 2018 at 3:54 PM Lin Yuan wrote: > Dear Community, > > > > Currently, our MXNet installation guide for Windows does not work for > Windows 7. e.g. Microsoft Visual Studio 2015 is not supported on Windows 7 > < >

Re: build from source instructions

The automated script served its purpose when MXNet PyPi package was not regularly maintained, the script made it simple for users when they had to build from source to get the latest. Now that we have a pypi package and build from source is something that the developers need, I have to agree

Re: Removing misleading metric log

Can you not just print the batch range[10-20] along with epoch, there might be user scripts that depend on these values(we won't know who is using) , I don't think we should drop this log. On Mon, Aug 27, 2018 at 9:38 AM Vandana Kannan wrote: > Hi All, > > The log self.logger.info('Epoch[%d]

Re: Release plan - MXNET 1.3

Is this is a major feature? This is a regression that Dom is reporting wrt to performance On Mon, Aug 13, 2018 at 11:38 AM, Roshani Nagmote wrote: > Thanks for reporting this issue Dom. > 08/10 (Frida)y was the major feature freeze date. We won't be accepting any > new features now for MXNet

Re: Growing number of open PRs and Labelling PRs

y to filter, group and take actions > > (review, merge, ping corresponding contributors). And when we have > deployed > > the labelling bot (hopefully soon to happen), we should be able to > > disassociate from the need for committer. > > Suggestion? > > > > @Naveen - T

Re: Suggestions for Design Proposal Template

Hi Patric, Design template is some preliminary work that I did and plan to propose as part of the PR best practice(criteria). I am still working on the PR document. Thanks for feedback on the Design Template and you make a great point. I discussed a similar idea with a few contributors nearby

  1   2   3   >