Re: [MATH] - Truncated Normal Distribution

2020-11-30 Thread Marko Malenic
Awesome.

Should I submit a jira ticket for this?

On Tue, Dec 1, 2020 at 12:11 PM Gilles Sadowski 
wrote:

> Hello.
>
> Le mar. 1 déc. 2020 à 01:42, Marko Malenic  a écrit :
> >
> >  Hi,
> >
> > I'm a bit new to all this stuff, so bear with me while I ask some
> questions
> > :)
> >
> > There's a few ways to do this.
> >
> > In terms of number generation, there's a few algorithms, some of which at
> > described at:
> >
> https://en.wikipedia.org/wiki/Truncated_normal_distribution#Computational_methods
> > Any preferences on how to generate the numbers?
> >
> > I noticed sampling is split off to commons rng.
> > Should another sampler be added, depending on the algorithm?
> > Or maybe just using inverse transform sampling would be okay.
>
> Some of the implemented distributions use the inverse transform.
> It's fine and sane to not do everything at once. ;-)
>
> Indeed, if you implement another sampler, it must go into the
> "sampling" module of "Commons RNG", reusing functionality
> already implemented there (if applicable).
>
> Regards,
> Gilles
>
> > [...]
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


Re: [MATH] - Truncated Normal Distribution

2020-11-30 Thread Gilles Sadowski
Hello.

Le mar. 1 déc. 2020 à 01:42, Marko Malenic  a écrit :
>
>  Hi,
>
> I'm a bit new to all this stuff, so bear with me while I ask some questions
> :)
>
> There's a few ways to do this.
>
> In terms of number generation, there's a few algorithms, some of which at
> described at:
> https://en.wikipedia.org/wiki/Truncated_normal_distribution#Computational_methods
> Any preferences on how to generate the numbers?
>
> I noticed sampling is split off to commons rng.
> Should another sampler be added, depending on the algorithm?
> Or maybe just using inverse transform sampling would be okay.

Some of the implemented distributions use the inverse transform.
It's fine and sane to not do everything at once. ;-)

Indeed, if you implement another sampler, it must go into the
"sampling" module of "Commons RNG", reusing functionality
already implemented there (if applicable).

Regards,
Gilles

> [...]

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



Re: [MATH] - Truncated Normal Distribution

2020-11-30 Thread Marko Malenic
 Hi,

I'm a bit new to all this stuff, so bear with me while I ask some questions
:)

There's a few ways to do this.

In terms of number generation, there's a few algorithms, some of which at
described at:
https://en.wikipedia.org/wiki/Truncated_normal_distribution#Computational_methods
Any preferences on how to generate the numbers?

I noticed sampling is split off to commons rng.
Should another sampler be added, depending on the algorithm?
Or maybe just using inverse transform sampling would be okay.

Let me know your thoughts,
Marko

On Tue, Dec 1, 2020 at 12:42 AM Gilles Sadowski 
wrote:

> Hello.
>
> Le lun. 30 nov. 2020 à 08:22, Marko Malenic  a écrit
> :
> >
> > Hi all,
> >
> > I'm interested in contributing here, and have been wanting to implement
> and
> > add a truncated normal distribution. Would anyone be interested in this?
>
> Contributions welcome. ;-)
>
> This would be an addition for the new "Commons Statistics" component:
> http://commons.apache.org/proper/commons-statistics/
> in module "distribution":
>
> https://gitbox.apache.org/repos/asf?p=commons-statistics.git;a=tree;f=commons-statistics-distribution
>
> Thanks for your interest,
> Gilles
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


Re: [MATH] - Truncated Normal Distribution

2020-11-30 Thread Gilles Sadowski
Hello.

Le lun. 30 nov. 2020 à 08:22, Marko Malenic  a écrit :
>
> Hi all,
>
> I'm interested in contributing here, and have been wanting to implement and
> add a truncated normal distribution. Would anyone be interested in this?

Contributions welcome. ;-)

This would be an addition for the new "Commons Statistics" component:
http://commons.apache.org/proper/commons-statistics/
in module "distribution":

https://gitbox.apache.org/repos/asf?p=commons-statistics.git;a=tree;f=commons-statistics-distribution

Thanks for your interest,
Gilles

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



Re: [LOGGING] Build errors

2020-11-30 Thread Romain Manni-Bucau
Have to admit I find the setup quite complex for a "commons" project too
(and the fact tests don't run in the IDE without configuring the failsafe
system properties is quite an issue IMHO).

Guess the maven way is to split it in modules instead of doing N real
artifacts (3 here) in one module (a bit like tomcat does with ant).

I also don't know if the intent is to really test the packaging or more the
features in failsafe run but if it is only the feature a better classloader
implementation (with filtering in loadClass and using target/classes and
target/test-classes folder instead of .jar) would make the test runnable
with surefire and way simpler to work on IMHO.

Just my 2 cts.
Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le lun. 30 nov. 2020 à 10:26, Mark Thomas  a écrit :

> On 30/11/2020 09:14, Romain Manni-Bucau wrote:
> > I think you need to adjust failsafe configuration, it passes the jar
> paths
> > as system properties.
> > Setting classifier without  (instead of ) you move
> from
> > c-l--.jar to c-l-- so tests
> will
> > likely fail.
> >
> > Another weird thing is the last "full jar" dependency which has a
> > classifier, I think the id of the execution should just be renamed
> > "default-jar" to be the "default jar" of the build and not have any
> > classifier, no?
>
> I have no idea. We are now way out of my comfort zone with Maven. I was
> just trying to get the build to complete without error.
>
> Mark
>
>
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github <
> https://github.com/rmannibucau> |
> > LinkedIn  | Book
> > <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
> >
> >
> > Le lun. 30 nov. 2020 à 10:09, Mark Thomas  a écrit :
> >
> >> On 30/11/2020 08:50, Romain Manni-Bucau wrote:
> >>> Hi Mark
> >>>
> >>> my guess is that apijar execution must add api
> >> (or
> >>> any value)
> >>>
> >>> this way you get the default jar but also this particular one.
> >>
> >> Thanks. That did it. Fix pushed.
> >>
> >> Mark
> >>
> >>
> >>>
> >>>
> >>> Romain Manni-Bucau
> >>> @rmannibucau  |  Blog
> >>>  | Old Blog
> >>>  | Github <
> >> https://github.com/rmannibucau> |
> >>> LinkedIn  | Book
> >>> <
> >>
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >>>
> >>>
> >>>
> >>> Le lun. 30 nov. 2020 à 09:40, Mark Thomas  a écrit :
> >>>
>  Hi,
> 
>  I've stumbled across the following error when trying to build a clean
>  clone of commons-logging with Maven 3.6.3 and Java 8u275
> 
>  git clone g...@github.com:apache/commons-logging.git
> asf-commons-logging
>  cd asf-commons-logging
>  mvn clean package
>  ...
>  Failed to execute goal
>  org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (apijar) on
> project
>  commons-logging: You have to use a classifier to attach supplemental
>  artifacts to the project instead of replacing them. -> [Help 1]
> 
>  My Maven foo is limited. Any hints on what needs changing in the POM
> to
>  fix this?
> 
>  Mark
> 
>  -
>  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
>
>


Re: [LOGGING] Build errors

2020-11-30 Thread Mark Thomas
On 30/11/2020 09:14, Romain Manni-Bucau wrote:
> I think you need to adjust failsafe configuration, it passes the jar paths
> as system properties.
> Setting classifier without  (instead of ) you move from
> c-l--.jar to c-l-- so tests will
> likely fail.
> 
> Another weird thing is the last "full jar" dependency which has a
> classifier, I think the id of the execution should just be renamed
> "default-jar" to be the "default jar" of the build and not have any
> classifier, no?

I have no idea. We are now way out of my comfort zone with Maven. I was
just trying to get the build to complete without error.

Mark


> 
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  |
> LinkedIn  | Book
> 
> 
> 
> Le lun. 30 nov. 2020 à 10:09, Mark Thomas  a écrit :
> 
>> On 30/11/2020 08:50, Romain Manni-Bucau wrote:
>>> Hi Mark
>>>
>>> my guess is that apijar execution must add api
>> (or
>>> any value)
>>>
>>> this way you get the default jar but also this particular one.
>>
>> Thanks. That did it. Fix pushed.
>>
>> Mark
>>
>>
>>>
>>>
>>> Romain Manni-Bucau
>>> @rmannibucau  |  Blog
>>>  | Old Blog
>>>  | Github <
>> https://github.com/rmannibucau> |
>>> LinkedIn  | Book
>>> <
>> https://www.packtpub.com/application-development/java-ee-8-high-performance
>>>
>>>
>>>
>>> Le lun. 30 nov. 2020 à 09:40, Mark Thomas  a écrit :
>>>
 Hi,

 I've stumbled across the following error when trying to build a clean
 clone of commons-logging with Maven 3.6.3 and Java 8u275

 git clone g...@github.com:apache/commons-logging.git asf-commons-logging
 cd asf-commons-logging
 mvn clean package
 ...
 Failed to execute goal
 org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (apijar) on project
 commons-logging: You have to use a classifier to attach supplemental
 artifacts to the project instead of replacing them. -> [Help 1]

 My Maven foo is limited. Any hints on what needs changing in the POM to
 fix this?

 Mark

 -
 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



Re: [LOGGING] Build errors

2020-11-30 Thread Romain Manni-Bucau
I think you need to adjust failsafe configuration, it passes the jar paths
as system properties.
Setting classifier without  (instead of ) you move from
c-l--.jar to c-l-- so tests will
likely fail.

Another weird thing is the last "full jar" dependency which has a
classifier, I think the id of the execution should just be renamed
"default-jar" to be the "default jar" of the build and not have any
classifier, no?

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le lun. 30 nov. 2020 à 10:09, Mark Thomas  a écrit :

> On 30/11/2020 08:50, Romain Manni-Bucau wrote:
> > Hi Mark
> >
> > my guess is that apijar execution must add api
> (or
> > any value)
> >
> > this way you get the default jar but also this particular one.
>
> Thanks. That did it. Fix pushed.
>
> Mark
>
>
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github <
> https://github.com/rmannibucau> |
> > LinkedIn  | Book
> > <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
> >
> >
> > Le lun. 30 nov. 2020 à 09:40, Mark Thomas  a écrit :
> >
> >> Hi,
> >>
> >> I've stumbled across the following error when trying to build a clean
> >> clone of commons-logging with Maven 3.6.3 and Java 8u275
> >>
> >> git clone g...@github.com:apache/commons-logging.git asf-commons-logging
> >> cd asf-commons-logging
> >> mvn clean package
> >> ...
> >> Failed to execute goal
> >> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (apijar) on project
> >> commons-logging: You have to use a classifier to attach supplemental
> >> artifacts to the project instead of replacing them. -> [Help 1]
> >>
> >> My Maven foo is limited. Any hints on what needs changing in the POM to
> >> fix this?
> >>
> >> Mark
> >>
> >> -
> >> 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
>
>


Re: [LOGGING] Build errors

2020-11-30 Thread Mark Thomas
On 30/11/2020 08:50, Romain Manni-Bucau wrote:
> Hi Mark
> 
> my guess is that apijar execution must add api (or
> any value)
> 
> this way you get the default jar but also this particular one.

Thanks. That did it. Fix pushed.

Mark


> 
> 
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  |
> LinkedIn  | Book
> 
> 
> 
> Le lun. 30 nov. 2020 à 09:40, Mark Thomas  a écrit :
> 
>> Hi,
>>
>> I've stumbled across the following error when trying to build a clean
>> clone of commons-logging with Maven 3.6.3 and Java 8u275
>>
>> git clone g...@github.com:apache/commons-logging.git asf-commons-logging
>> cd asf-commons-logging
>> mvn clean package
>> ...
>> Failed to execute goal
>> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (apijar) on project
>> commons-logging: You have to use a classifier to attach supplemental
>> artifacts to the project instead of replacing them. -> [Help 1]
>>
>> My Maven foo is limited. Any hints on what needs changing in the POM to
>> fix this?
>>
>> Mark
>>
>> -
>> 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



Re: [LOGGING] Build errors

2020-11-30 Thread Romain Manni-Bucau
Hi Mark

my guess is that apijar execution must add api (or
any value)

this way you get the default jar but also this particular one.


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le lun. 30 nov. 2020 à 09:40, Mark Thomas  a écrit :

> Hi,
>
> I've stumbled across the following error when trying to build a clean
> clone of commons-logging with Maven 3.6.3 and Java 8u275
>
> git clone g...@github.com:apache/commons-logging.git asf-commons-logging
> cd asf-commons-logging
> mvn clean package
> ...
> Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (apijar) on project
> commons-logging: You have to use a classifier to attach supplemental
> artifacts to the project instead of replacing them. -> [Help 1]
>
> My Maven foo is limited. Any hints on what needs changing in the POM to
> fix this?
>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


[LOGGING] Build errors

2020-11-30 Thread Mark Thomas
Hi,

I've stumbled across the following error when trying to build a clean
clone of commons-logging with Maven 3.6.3 and Java 8u275

git clone g...@github.com:apache/commons-logging.git asf-commons-logging
cd asf-commons-logging
mvn clean package
...
Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (apijar) on project
commons-logging: You have to use a classifier to attach supplemental
artifacts to the project instead of replacing them. -> [Help 1]

My Maven foo is limited. Any hints on what needs changing in the POM to
fix this?

Mark

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