Re: [math] Proposal: logsumexp

2018-11-16 Thread Gilles 

Hello.


Thank you for your interest in the "Commons Math" library.
However, you should be aware that some of its functionality is in the
process of being transferred to more focused components:
 * Commons Numbers
 * Commons RNG
 * Commons Statistics
 * Commons Geometry

In particular, a method such as you describe could perhaps have its
place in the "commons-numbers-arrays" module of "Numbers".[1]

Regards,
Gilles

[1] 
https://git1-us-west.apache.org/repos/asf?p=commons-numbers.git;a=tree;f=commons-numbers-arrays/src/main/java/org/apache/commons/numbers/arrays



On Fri, 16 Nov 2018 15:56:45 -0500, Ahmed Fasih wrote:

Hello friends, I'm new to Java, and to Apache Commons Math, and I'm
porting some code to Java. One useful function that's available in
Scipy is `logsumexp`:


https://docs.scipy.org/doc/scipy/reference/generated/scipy.special.logsumexp.html

In a nutshell, given a list of values in the log domain, the function
numerically-stably sums them, yielding the result still in the log
domain.

This is useful for me because I need to add and subtract the results
of the log-Gamma function (via your `Gamma.logGamma`). For
*subtraction,* Scipy's `logsumexp` can accept a *second* list giving
the scalars to apply to each value (e.g., +1, -1), and returns both
the magnitude *and* sign of the result.

I would like feedback on adding `logsumexp` to Apache Commons Math. I
have ported the Python version, from


https://github.com/scipy/scipy/blob/5e5a2d2a47b9011be2f73971bba94b3e158936c5/scipy/special/_logsumexp.py#L9-L130

to Java, which lives at:


https://github.com/fasiha/ebisu-java/blob/2b651071b37aac5f85e8cb4c07ea7a1e14bb175c/src/main/java/me/aldebrn/ebisu/Ebisu.java#L33-L69

As mentioned above, I'm a beginner, and am experimenting with Java 8
Collections, etc., so I am embarrassed by my mixing of `List` and
plain arrays in this last link above. Assuming that you think it 
would
be a good addition to Math, I'm totally open to suggestions to 
improve

the API.

Many thanks,

Ahmed




-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons Pool2 2.6.1

2018-11-16 Thread Gary Gregory 
On Fri, Nov 16, 2018 at 2:32 PM Romain Manni-Bucau 
wrote:

> Le ven. 16 nov. 2018 21:23, Gary Gregory  a écrit
> :
>
> > On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg  >
> > wrote:
> >
> > > Oki, now the full VOTE text!
> > >
> > > I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> > > The release was run with JDK-1.7 to ensure Java7 compatibility.
> > >
> > >
> > > The ASF staging repository is at
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > >
> > > The source zip is at
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > > The sha1 of the source-release zip is
> > > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > > The sha512 is
> > >
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > >
> >
> > For me:
> >
> > $ sha512sum commons-pool2-2.6.1-src.zip
> >
> >
> 2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
> > *commons-pool2-2.6.1-src.zip
> >
> > Which is not what you list above. Please advise.
> >
>
> Src vs source-release?
>

Yes, the hash matches source-release, thank you!

Gary


>
>
>
>
>
> > Gary
> >
> >
> > >
> > > I added my KEY (struberg at apache.org) to our dist KEYS file
> > > https://dist.apache.org/repos/dist/release/commons/KEYS
> > >
> > > I've created the release in a GIT manner and pushed the according
> changes
> > > to my ASF-linked github repo
> > >
> > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > the sha1 of the commit is
> > >
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > >
> > > the tag is
> > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > c910171
> > > <
> > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171
> >
> > >
> > > This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> > >
> > > Site will be updated once the release has passed.
> > >
> > > Please VOTE:
> > >
> > > [+1] go ship it!
> > > [+0] meh, I don't care
> > > [-1] stop there is a ${showstopper} (that means something _important_
> is
> > > missing!)
> > >
> > >
> > > Here is my own +1
> > > checked:
> > > * signature
> > > * hashes
> > > * LICENSE
> > > * NOTICE
> > > * rat
> > > * builds fine with various JDKs
> > >
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > >
> > >
> > >
> > > > Am 14.11.2018 um 10:13 schrieb Mark Struberg
>  > > >:
> > > >
> > > > PS: I've created the release in a GIT manner and pushed the according
> > > changes to my ASF-linked github repo
> > > >
> > > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > > the sha1 of the commit is
> > > >
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > > >
> > > > the tag is
> > > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > > c910171
> > > >
> > > > This will get pushed to the ASF cannonical repo once the VOTE
> succeeds.
> > > > Yay, this is the way GIT works and before someone not familiar with
> GIT
> > > screams that this is not hosted on ASF: This got discussed on the board
> > > level a long time ago (when we did DeltaSpike and CouchDB as the very
> > first
> > > GIT repos at the ASF) and is perfectly fine as all this is based on
> > > cryptographically strong steps.
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > >
> > > >> Am 14.11.2018 um 09:17 schrieb Mark Struberg
> >  > > >:
> > > >>
> > > >> Hi folks!
> > > >>
> > > >> I'm currently preparing the release for commons-pool2-2.6.1
> > > >>
> > > >> So far I did
> > > >>
> > > >> * fix the missing parts in changes.xml
> > > >> * generate + copy the RELEASE_NOTES
> > > >> * run the maven release (after fixing the setup...)
> > > >>
> > > >> The ASF staging repository is at
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > > >>
> > > >> The source zip is at
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > > >> The sha1 of the source-release zip is
> > > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > > >> The sha512 is
> > >
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > > >>
> > > >> I added my KEY (struberg at apache.org) to our dist KEYS file
> > > >> https://dist.apache.org/repos/dist/release/commons/KEYS
> > > >>
> > > >> I will now continue with the follow up steps and then call an
> official
> > > VOTE.
> > > >>
> > > >> Please let me know if something went wrong so far!
> > > >>
> > > >> LieGrue,
> > > >> strub
> > > >>
> > > >>
> > > >>
>

Re: [VOTE] Release Apache Commons Pool2 2.6.1

2018-11-16 Thread Romain Manni-Bucau 
Le ven. 16 nov. 2018 22:54, Gary Gregory  a écrit :

> On Fri, Nov 16, 2018 at 2:32 PM Romain Manni-Bucau 
> wrote:
>
> > Le ven. 16 nov. 2018 21:23, Gary Gregory  a
> écrit
> > :
> >
> > > On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg
>  > >
> > > wrote:
> > >
> > > > Oki, now the full VOTE text!
> > > >
> > > > I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> > > > The release was run with JDK-1.7 to ensure Java7 compatibility.
> > > >
> > > >
> > > > The ASF staging repository is at
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > > >
> > > > The source zip is at
> > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > > > The sha1 of the source-release zip is
> > > > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > > > The sha512 is
> > > >
> > >
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > > >
> > >
> > > For me:
> > >
> > > $ sha512sum commons-pool2-2.6.1-src.zip
> > >
> > >
> >
> 2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
> > > *commons-pool2-2.6.1-src.zip
> > >
> > > Which is not what you list above. Please advise.
> > >
> >
> > Src vs source-release?
> >
>
> That's the problem with inventing a new release process... why do we have
> BOTH:
>
>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-src.zip
> AND
>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-source-release.zip
>
> And more importantly why are they _different_? Which one will be used in
> the dist/release area?
>


Looks like pool didnt do its homework and kept the old assembly (src),
source-release comes from the parent and is likely the one to keep IMHO


> Gary
>
>
>
> >
> >
> >
> >
> >
> > > Gary
> > >
> > >
> > > >
> > > > I added my KEY (struberg at apache.org) to our dist KEYS file
> > > > https://dist.apache.org/repos/dist/release/commons/KEYS
> > > >
> > > > I've created the release in a GIT manner and pushed the according
> > changes
> > > > to my ASF-linked github repo
> > > >
> > > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > > the sha1 of the commit is
> > > >
> > > >
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > > >
> > > > the tag is
> > > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > > c910171
> > > > <
> > >
> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171
> > >
> > > >
> > > > This will get pushed to the ASF cannonical repo once the VOTE
> succeeds.
> > > >
> > > > Site will be updated once the release has passed.
> > > >
> > > > Please VOTE:
> > > >
> > > > [+1] go ship it!
> > > > [+0] meh, I don't care
> > > > [-1] stop there is a ${showstopper} (that means something _important_
> > is
> > > > missing!)
> > > >
> > > >
> > > > Here is my own +1
> > > > checked:
> > > > * signature
> > > > * hashes
> > > > * LICENSE
> > > > * NOTICE
> > > > * rat
> > > > * builds fine with various JDKs
> > > >
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > > Am 14.11.2018 um 10:13 schrieb Mark Struberg
> >  > > > >:
> > > > >
> > > > > PS: I've created the release in a GIT manner and pushed the
> according
> > > > changes to my ASF-linked github repo
> > > > >
> > > > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > > > the sha1 of the commit is
> > > > >
> > > >
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > > > >
> > > > > the tag is
> > > > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > > > c910171
> > > > >
> > > > > This will get pushed to the ASF cannonical repo once the VOTE
> > succeeds.
> > > > > Yay, this is the way GIT works and before someone not familiar with
> > GIT
> > > > screams that this is not hosted on ASF: This got discussed on the
> board
> > > > level a long time ago (when we did DeltaSpike and CouchDB as the very
> > > first
> > > > GIT repos at the ASF) and is perfectly fine as all this is based on
> > > > cryptographically strong steps.
> > > > >
> > > > > LieGrue,
> > > > > strub
> > > > >
> > > > >
> > > > >> Am 14.11.2018 um 09:17 schrieb Mark Struberg
> > >  > > > >:
> > > > >>
> > > > >> Hi folks!
> > > > >>
> > > > >> I'm currently preparing the release for commons-pool2-2.6.1
> > > > >>
> > > > >> So far I did
> > > > >>
> > > > >> * fix the missing parts in changes.xml
> > > > >> * generate + copy the RELEASE_NOTES
> > > > >> * run the maven release (after fixing the setup...)
> > > > >>
> > > > >> The ASF staging

Re: [VOTE] Release Apache Commons Pool2 2.6.1

2018-11-16 Thread Gary Gregory 
Should we cancel this RC to include:

https://issues.apache.org/jira/browse/POOL-359

?

Gary

On Wed, Nov 14, 2018 at 1:17 AM Mark Struberg 
wrote:

> Hi folks!
>
> I'm currently preparing the release for commons-pool2-2.6.1
>
> So far I did
>
> * fix the missing parts in changes.xml
> * generate + copy the RELEASE_NOTES
> * run the maven release (after fixing the setup...)
>
> The ASF staging repository is at
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>
> The source zip is at
>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> The sha1 of the source-release zip is
> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> The sha512 is
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>
> I added my KEY (struberg at apache.org) to our dist KEYS file
> https://dist.apache.org/repos/dist/release/commons/KEYS
>
> I will now continue with the follow up steps and then call an official
> VOTE.
>
> Please let me know if something went wrong so far!
>
> LieGrue,
> strub
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] Release Apache Commons Pool2 2.6.1

2018-11-16 Thread Gary Gregory 
On Fri, Nov 16, 2018 at 2:32 PM Romain Manni-Bucau 
wrote:

> Le ven. 16 nov. 2018 21:23, Gary Gregory  a écrit
> :
>
> > On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg  >
> > wrote:
> >
> > > Oki, now the full VOTE text!
> > >
> > > I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> > > The release was run with JDK-1.7 to ensure Java7 compatibility.
> > >
> > >
> > > The ASF staging repository is at
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > >
> > > The source zip is at
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > > The sha1 of the source-release zip is
> > > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > > The sha512 is
> > >
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > >
> >
> > For me:
> >
> > $ sha512sum commons-pool2-2.6.1-src.zip
> >
> >
> 2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
> > *commons-pool2-2.6.1-src.zip
> >
> > Which is not what you list above. Please advise.
> >
>
> Src vs source-release?
>

That's the problem with inventing a new release process... why do we have
BOTH:

https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-src.zip
AND
https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/commons-pool2-2.6.1-source-release.zip

And more importantly why are they _different_? Which one will be used in
the dist/release area?

Gary



>
>
>
>
>
> > Gary
> >
> >
> > >
> > > I added my KEY (struberg at apache.org) to our dist KEYS file
> > > https://dist.apache.org/repos/dist/release/commons/KEYS
> > >
> > > I've created the release in a GIT manner and pushed the according
> changes
> > > to my ASF-linked github repo
> > >
> > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > the sha1 of the commit is
> > >
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > >
> > > the tag is
> > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > c910171
> > > <
> > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171
> >
> > >
> > > This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> > >
> > > Site will be updated once the release has passed.
> > >
> > > Please VOTE:
> > >
> > > [+1] go ship it!
> > > [+0] meh, I don't care
> > > [-1] stop there is a ${showstopper} (that means something _important_
> is
> > > missing!)
> > >
> > >
> > > Here is my own +1
> > > checked:
> > > * signature
> > > * hashes
> > > * LICENSE
> > > * NOTICE
> > > * rat
> > > * builds fine with various JDKs
> > >
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > >
> > >
> > >
> > > > Am 14.11.2018 um 10:13 schrieb Mark Struberg
>  > > >:
> > > >
> > > > PS: I've created the release in a GIT manner and pushed the according
> > > changes to my ASF-linked github repo
> > > >
> > > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > > the sha1 of the commit is
> > > >
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > > >
> > > > the tag is
> > > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > > c910171
> > > >
> > > > This will get pushed to the ASF cannonical repo once the VOTE
> succeeds.
> > > > Yay, this is the way GIT works and before someone not familiar with
> GIT
> > > screams that this is not hosted on ASF: This got discussed on the board
> > > level a long time ago (when we did DeltaSpike and CouchDB as the very
> > first
> > > GIT repos at the ASF) and is perfectly fine as all this is based on
> > > cryptographically strong steps.
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > >
> > > >> Am 14.11.2018 um 09:17 schrieb Mark Struberg
> >  > > >:
> > > >>
> > > >> Hi folks!
> > > >>
> > > >> I'm currently preparing the release for commons-pool2-2.6.1
> > > >>
> > > >> So far I did
> > > >>
> > > >> * fix the missing parts in changes.xml
> > > >> * generate + copy the RELEASE_NOTES
> > > >> * run the maven release (after fixing the setup...)
> > > >>
> > > >> The ASF staging repository is at
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > > >>
> > > >> The source zip is at
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > > >> The sha1 of the source-release zip is
> > > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > > >> The sha512 is
> > >
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > > >>
> > > >> I

Re: [VOTE] Release Apache Commons Pool2 2.6.1

2018-11-16 Thread Romain Manni-Bucau 
Le ven. 16 nov. 2018 21:23, Gary Gregory  a écrit :

> On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg 
> wrote:
>
> > Oki, now the full VOTE text!
> >
> > I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> > The release was run with JDK-1.7 to ensure Java7 compatibility.
> >
> >
> > The ASF staging repository is at
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> >
> > The source zip is at
> >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > The sha1 of the source-release zip is
> > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > The sha512 is
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> >
>
> For me:
>
> $ sha512sum commons-pool2-2.6.1-src.zip
>
> 2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
> *commons-pool2-2.6.1-src.zip
>
> Which is not what you list above. Please advise.
>

Src vs source-release?






> Gary
>
>
> >
> > I added my KEY (struberg at apache.org) to our dist KEYS file
> > https://dist.apache.org/repos/dist/release/commons/KEYS
> >
> > I've created the release in a GIT manner and pushed the according changes
> > to my ASF-linked github repo
> >
> > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > the sha1 of the commit is
> >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> >
> > the tag is
> > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > c910171
> > <
> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1c910171>
> >
> > This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> >
> > Site will be updated once the release has passed.
> >
> > Please VOTE:
> >
> > [+1] go ship it!
> > [+0] meh, I don't care
> > [-1] stop there is a ${showstopper} (that means something _important_ is
> > missing!)
> >
> >
> > Here is my own +1
> > checked:
> > * signature
> > * hashes
> > * LICENSE
> > * NOTICE
> > * rat
> > * builds fine with various JDKs
> >
> >
> > LieGrue,
> > strub
> >
> >
> >
> >
> >
> > > Am 14.11.2018 um 10:13 schrieb Mark Struberg  > >:
> > >
> > > PS: I've created the release in a GIT manner and pushed the according
> > changes to my ASF-linked github repo
> > >
> > > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > > the sha1 of the commit is
> > >
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> > >
> > > the tag is
> > > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > > c910171
> > >
> > > This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> > > Yay, this is the way GIT works and before someone not familiar with GIT
> > screams that this is not hosted on ASF: This got discussed on the board
> > level a long time ago (when we did DeltaSpike and CouchDB as the very
> first
> > GIT repos at the ASF) and is perfectly fine as all this is based on
> > cryptographically strong steps.
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > >> Am 14.11.2018 um 09:17 schrieb Mark Struberg
>  > >:
> > >>
> > >> Hi folks!
> > >>
> > >> I'm currently preparing the release for commons-pool2-2.6.1
> > >>
> > >> So far I did
> > >>
> > >> * fix the missing parts in changes.xml
> > >> * generate + copy the RELEASE_NOTES
> > >> * run the maven release (after fixing the setup...)
> > >>
> > >> The ASF staging repository is at
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> > >>
> > >> The source zip is at
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> > >> The sha1 of the source-release zip is
> > 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> > >> The sha512 is
> >
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> > >>
> > >> I added my KEY (struberg at apache.org) to our dist KEYS file
> > >> https://dist.apache.org/repos/dist/release/commons/KEYS
> > >>
> > >> I will now continue with the follow up steps and then call an official
> > VOTE.
> > >>
> > >> Please let me know if something went wrong so far!
> > >>
> > >> LieGrue,
> > >> strub
> > >>
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > >> For additional commands, e-mail: dev-h...@commons.apache.org
> > >>
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > For additional commands, e-mail: dev-h...@commons.apache.org
> > >
> >
> >
> > -
> > To

[math] Proposal: logsumexp

2018-11-16 Thread Ahmed Fasih 
Hello friends, I'm new to Java, and to Apache Commons Math, and I'm porting 
some code to Java. One useful function that's available in Scipy is `logsumexp`:

https://docs.scipy.org/doc/scipy/reference/generated/scipy.special.logsumexp.html

In a nutshell, given a list of values in the log domain, the function 
numerically-stably sums them, yielding the result still in the log domain.

This is useful for me because I need to add and subtract the results of the 
log-Gamma function (via your `Gamma.logGamma`). For *subtraction,* Scipy's 
`logsumexp` can accept a *second* list giving the scalars to apply to each 
value (e.g., +1, -1), and returns both the magnitude *and* sign of the result.

I would like feedback on adding `logsumexp` to Apache Commons Math. I have 
ported the Python version, from

https://github.com/scipy/scipy/blob/5e5a2d2a47b9011be2f73971bba94b3e158936c5/scipy/special/_logsumexp.py#L9-L130

to Java, which lives at:

https://github.com/fasiha/ebisu-java/blob/2b651071b37aac5f85e8cb4c07ea7a1e14bb175c/src/main/java/me/aldebrn/ebisu/Ebisu.java#L33-L69

As mentioned above, I'm a beginner, and am experimenting with Java 8 
Collections, etc., so I am embarrassed by my mixing of `List` and plain arrays 
in this last link above. Assuming that you think it would be a good addition to 
Math, I'm totally open to suggestions to improve the API.

Many thanks,

Ahmed

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-pool pull request #17: POOL-359: prevent NPE closing multiple Generi...

2018-11-16 Thread mswintermeyer 
GitHub user mswintermeyer opened a pull request:

https://github.com/apache/commons-pool/pull/17

POOL-359: prevent NPE closing multiple GenericObjectPool's



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mswintermeyer/commons-pool fixNPEClosePools

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/commons-pool/pull/17.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #17


commit 0fdde72475b378cbd0fb707d52385196d928a1da
Author: Michael Wintermeyer 
Date:   2018-11-16T20:23:51Z

POOL-359: prevent NPE closing multiple GenericObjectPool's




---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons Pool2 2.6.1

2018-11-16 Thread Gary Gregory 
On Wed, Nov 14, 2018 at 8:59 AM Mark Struberg 
wrote:

> Oki, now the full VOTE text!
>
> I'd like to call a VOTE on releasing Apache Commons pool2 2.6.1
> The release was run with JDK-1.7 to ensure Java7 compatibility.
>
>
> The ASF staging repository is at
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
>
> The source zip is at
>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> The sha1 of the source-release zip is
> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> The sha512 is
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
>

For me:

$ sha512sum commons-pool2-2.6.1-src.zip
2b95b00a22bf72a7cdf77f2e40796d126b4a0d7b669564b8b04cd0c884252acd3dac356fe55a9fdaadd4767e13eef560995989cb2d39f862f8d3b7e1d06c773e
*commons-pool2-2.6.1-src.zip

Which is not what you list above. Please advise.

Gary


>
> I added my KEY (struberg at apache.org) to our dist KEYS file
> https://dist.apache.org/repos/dist/release/commons/KEYS
>
> I've created the release in a GIT manner and pushed the according changes
> to my ASF-linked github repo
>
> https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> the sha1 of the commit is
>
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
>
> the tag is
> https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> c910171
> 
>
> This will get pushed to the ASF cannonical repo once the VOTE succeeds.
>
> Site will be updated once the release has passed.
>
> Please VOTE:
>
> [+1] go ship it!
> [+0] meh, I don't care
> [-1] stop there is a ${showstopper} (that means something _important_ is
> missing!)
>
>
> Here is my own +1
> checked:
> * signature
> * hashes
> * LICENSE
> * NOTICE
> * rat
> * builds fine with various JDKs
>
>
> LieGrue,
> strub
>
>
>
>
>
> > Am 14.11.2018 um 10:13 schrieb Mark Struberg  >:
> >
> > PS: I've created the release in a GIT manner and pushed the according
> changes to my ASF-linked github repo
> >
> > https://github.com/struberg/commons-pool/tree/release_branch_2.6.1
> > the sha1 of the commit is
> >
> https://github.com/struberg/commons-pool/commit/c910171d9d8c8f5f895b7d18381fc03a51b2a019
> >
> > the tag is
> > https://github.com/struberg/commons-pool/tree/commons-pool2-2.6.1
> > c910171
> >
> > This will get pushed to the ASF cannonical repo once the VOTE succeeds.
> > Yay, this is the way GIT works and before someone not familiar with GIT
> screams that this is not hosted on ASF: This got discussed on the board
> level a long time ago (when we did DeltaSpike and CouchDB as the very first
> GIT repos at the ASF) and is perfectly fine as all this is based on
> cryptographically strong steps.
> >
> > LieGrue,
> > strub
> >
> >
> >> Am 14.11.2018 um 09:17 schrieb Mark Struberg  >:
> >>
> >> Hi folks!
> >>
> >> I'm currently preparing the release for commons-pool2-2.6.1
> >>
> >> So far I did
> >>
> >> * fix the missing parts in changes.xml
> >> * generate + copy the RELEASE_NOTES
> >> * run the maven release (after fixing the setup...)
> >>
> >> The ASF staging repository is at
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/
> >>
> >> The source zip is at
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-1396/org/apache/commons/commons-pool2/2.6.1/
> >> The sha1 of the source-release zip is
> 17b01d1e776b7e2b9987b665e1b4e456c02ffa1c
> >> The sha512 is
> 982275c963c09e11dd38a3b6621f2a67bab42b6744a1629ab97b7323208b31730b756a7d5bc6dabee54ba0e9f72c8296904f36919fd421fee8e59786c587c388
> >>
> >> I added my KEY (struberg at apache.org) to our dist KEYS file
> >> https://dist.apache.org/repos/dist/release/commons/KEYS
> >>
> >> I will now continue with the follow up steps and then call an official
> VOTE.
> >>
> >> Please let me know if something went wrong so far!
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

[GitHub] commons-rng issue #12: RNG-57: Cache values for provision of nextBoolean and...

2018-11-16 Thread coveralls 
Github user coveralls commented on the issue:

https://github.com/apache/commons-rng/pull/12
  

[![Coverage 
Status](https://coveralls.io/builds/20148825/badge)](https://coveralls.io/builds/20148825)

Coverage decreased (-0.2%) to 97.358% when pulling 
**91a5eec2d8a3318cf8fc8e6d222ac3edf3a0d969 on aherbert:improvement-RNG-57** 
into **0fdcd9007c708aa48f1989cb2211ea56c1fcd702 on apache:master**.



---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-rng pull request #12: RNG-57: Cache values for provision of nextBool...

2018-11-16 Thread aherbert 
GitHub user aherbert opened a pull request:

https://github.com/apache/commons-rng/pull/12

RNG-57: Cache values for provision of nextBoolean and nextInt

This PR contains the suggested changes to implement a cache to speed up the 
`nextInt` and `nextBoolean` methods in the core provider implementations.

These changes improve performance but the effect on the `nextInt` method of 
`LongProvider` is unknown. A repeat of the DieHarder and TestU01 test suites is 
currently in progress.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/aherbert/commons-rng improvement-RNG-57

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/commons-rng/pull/12.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #12


commit 91a5eec2d8a3318cf8fc8e6d222ac3edf3a0d969
Author: aherbert 
Date:   2018-11-16T13:10:51Z

RNG-57: Cache values for provision of nextBoolean and nextInt




---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org