Re: Julia Package Release Process
okay. Before disabling the issue tracker, I'm going to transfer the issue from MXNet.jl to main repo. (via https://help.github.com/articles/transferring-an-issue-to-another-repository/) On 1/7/19 12:17 AM, Chris Olivier wrote: +1 for disabling issue tracker and putting a note on original repo (if it isn’t already there) that work/issue tracking has moved to mxnet (using julia label in github or Jira). m On Sun, Jan 6, 2019 at 1:19 AM iblis wrote: Before PR #10149 got merged (Oct 5, 2018) into main repo, julia code is developed and maintained in the separate repo -- dmlc/MXNet.jl. After that PR, there are no further development happened in dmlc/MXNet.jl. We work with the main repo now. But the original MXNet.jl repo is still there, it just isn't deleted or archived yet. I receive some issue ticks from this repo occasionally, maybe we should just disable the issue tracker of it. Does it work with other frameworks other than mxnet? hmm, I'm not sure what you mean. On 1/6/19 1:18 PM, Chris Olivier wrote: Curious: Why is the julia code maintained in a separate repo? I was under the impression that it was donated/permanently merged into the mxnet source tree. Does it work with other frameworks other than mxnet? On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin wrote: If there is trademark issue, how about this option: 3) transferring the MXNet.jl repo ownership from DMLC to Apache. On 1/6/19 6:45 AM, Justin Mclean wrote: Hi, 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl It's under DMLC. I have the committer bit of this repo. I'm not 100% sure that would be allowed from a branding/trademark perspective, any distribution owned by a 3rd party can't be called "Apache MXNet". 2) A new repo under ASF's organization? That seems preferable I think. Thanks, Justin -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤
Re: Julia Package Release Process
+1 for disabling issue tracker and putting a note on original repo (if it isn’t already there) that work/issue tracking has moved to mxnet (using julia label in github or Jira). m On Sun, Jan 6, 2019 at 1:19 AM iblis wrote: > Before PR #10149 got merged (Oct 5, 2018) into main repo, > julia code is developed and maintained in the separate repo -- > dmlc/MXNet.jl. > > After that PR, there are no further development happened in dmlc/MXNet.jl. > We work with the main repo now. > But the original MXNet.jl repo is still there, it just isn't deleted or > archived yet. > I receive some issue ticks from this repo occasionally, > maybe we should just disable the issue tracker of it. > > > Does it work with other frameworks other than mxnet? > hmm, I'm not sure what you mean. > > On 1/6/19 1:18 PM, Chris Olivier wrote: > > Curious: Why is the julia code maintained in a separate repo? I was > under > > the impression that it was donated/permanently merged into the mxnet > source > > tree. Does it work with other frameworks other than mxnet? > > > > On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin wrote: > > > >> If there is trademark issue, how about this option: > >> 3) transferring the MXNet.jl repo ownership from DMLC to Apache. > >> > >> On 1/6/19 6:45 AM, Justin Mclean wrote: > >>> Hi, > >>> > 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl > It's under DMLC. I have the committer bit of this repo. > >>> > >>> I'm not 100% sure that would be allowed from a branding/trademark > >> perspective, any distribution owned by a 3rd party can't be called > "Apache > >> MXNet". > >>> > 2) A new repo under ASF's organization? > >>> > >>> That seems preferable I think. > >>> > >>> Thanks, > >>> Justin > >>> > >> > >> -- > >> Iblis Lin > >> 林峻頤 > >> > > > > -- > Iblis Lin > 林峻頤 >
Re: soft relu gradient, is it correct?
Hi Pedro, these are just helper functions, you need to check the operator. In this case, the function is the derivative as function of the *output*, which is cheaper to compute: y = log(1 + exp(x)) => dy/dx = 1/(1 + exp(-x)) = 1 - exp(-y) If you check all sorts of other ops, the same is the case. You need to always check the code for the operator. In any case, there are quite some unit tests, that would catch this, except of course if people added functions after I did this, and have not updated the unit tests. Bye, Matthias On Wed, Nov 21, 2018 at 12:52 AM Pedro Larroy wrote: > I bumped into the definition of the softrelu gradient: > > > https://github.com/apache/incubator-mxnet/blob/master/src/operator/mshadow_op.h#L170 > > Which is defined as 1- exp(-x) > > As we define the forward of the softrelu as the softplus function, > shouldn't the gradient be the logistic function? > > Is my understanding that the gradient of the softrelu should go down > to zero as Lim x -> -Inf Which is not the case with the above > definition which goes to -Inf as Lim x- > -Inf > > https://en.wikipedia.org/wiki/Rectifier_(neural_networks) > > > Pedro. > -- Matthias Seeger
Re: Julia Package Release Process
Before PR #10149 got merged (Oct 5, 2018) into main repo, julia code is developed and maintained in the separate repo -- dmlc/MXNet.jl. After that PR, there are no further development happened in dmlc/MXNet.jl. We work with the main repo now. But the original MXNet.jl repo is still there, it just isn't deleted or archived yet. I receive some issue ticks from this repo occasionally, maybe we should just disable the issue tracker of it. Does it work with other frameworks other than mxnet? hmm, I'm not sure what you mean. On 1/6/19 1:18 PM, Chris Olivier wrote: Curious: Why is the julia code maintained in a separate repo? I was under the impression that it was donated/permanently merged into the mxnet source tree. Does it work with other frameworks other than mxnet? On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin wrote: If there is trademark issue, how about this option: 3) transferring the MXNet.jl repo ownership from DMLC to Apache. On 1/6/19 6:45 AM, Justin Mclean wrote: Hi, 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl It's under DMLC. I have the committer bit of this repo. I'm not 100% sure that would be allowed from a branding/trademark perspective, any distribution owned by a 3rd party can't be called "Apache MXNet". 2) A new repo under ASF's organization? That seems preferable I think. Thanks, Justin -- Iblis Lin 林峻頤 -- Iblis Lin 林峻頤
