Re: ***UNCHECKED*** [parent] Introducing Automatic-Module-Name

Le mar. 9 avr. 2019 à 13:03, sebb a écrit : > > On Tue, 9 Apr 2019 at 11:43, Gilles Sadowski wrote: > > > > > [...] > > > > > > > > $ git diff pom.xml > > > > diff --git a/pom.xml b/pom.xml > > > > index 2612dd6..54a88e4 100644

Re: ***UNCHECKED*** [parent] Introducing Automatic-Module-Name

1.3 > > 1.3 > > > > + > > +${project.artifactId} No default should be defined (to avoid the risk of creating incompatible but identically named modules). Then the release plugin could be enhanced (?) so that it w

Re: [rng] Split and Jump functions

may not be flexible enough going forward. I'm missing many points, and this one too as a consequence. My (simplistic?) idea was to have methods added to the "UniformRandomProvider" interface: public interface UniformRandomProvider { // ... boolean isJumpable(); UniformRando

Re: [commons-lang] branch master updated: (docs) update user use -> user explore

Hi Rob. Le lun. 8 avr. 2019 à 14:16, Rob Tompkins a écrit : > > I think that maybe hits what you guys were getting after with my wording. You probably missed a thread. I've just committed the alternative text. Regards, Gilles > > And you know me, english as a first language, s

Re: [lang] LANG-1442

Le sam. 6 avr. 2019 à 16:59, Rob Tompkins a écrit : > > @Gilles - thoughts on this wording: > https://github.com/apache/commons-lang/commit/3f43706192b1b75c5023f165534a12b192c31442 > > <https://github.com/apache/commons-lang/commit/3f43706192b1b75c5023f1

Re: [lang] Towards 3.9

Le sam. 6 avr. 2019 à 16:00, Jochen Wiedmann a écrit : > > On Fri, Apr 5, 2019 at 4:27 AM Rob Tompkins wrote: > > > > > On Apr 4, 2019, at 9:20 AM, Gilles Sadowski wrote: > > > > > >> Any thoughts on doing a 3.9 release of [lang]. I think Benedikt wa

Re: [lang] Towards 3.9

Hi Rob. Le ven. 5 avr. 2019 à 04:27, Rob Tompkins a écrit : > > > > > On Apr 4, 2019, at 9:20 AM, Gilles Sadowski wrote: > > > >> Any thoughts on doing a 3.9 release of [lang]. I think Benedikt want’s us > >> to go up with what we have. Any thoughts for

Re: [GSoC] Submission of Final Draft for GSoC Proposal

Le ven. 5 avr. 2019 à 15:14, Javin Paul a écrit : > > How to unsubscribe from this email list? can someone please help? This is indicated in the messages' footer (see below). HTH, Gilles > > > > - > >

Re: [all] Should we use MathJaX in Javadoc on all repos? (Was: Re: [jira] [Commented] (NUMBERS-58) Javadoc: Use MathJaX)

the processing to be optional, e.g. > > via a marker file. Not all projects might expect improvement with MathJaX; if so, they should not use it. But deactivating MathJaX when it is used in the Javadoc does not seem very user-friendly (if the marker file would not include the HTML snippet neces

Re: [GSoC] Submission of Final Draft for GSoC Proposal

the "commons-rng-core" module), the code need not be Apache-compatible. [But then, the port *must* be implemented "from scratch", i.e. there must be reference to a paper that describe (not necessarily in code) everything necessary for producing the correct output.] R

Re: [GSoC] Submission of Final Draft for GSoC Proposal

t; benchmark tests on the SecureRandom algorithms as discussed ? If so, are > there any guidelines/ data on doing so ? This is in module "commons-rng-examples/exmaples-jmh". Regards, Gilles > PS: Thanks for the feedback! > > Regards, > Abhishek > > On Tue, Apr 2, 2019 at 4:34 AM Gille

Re: [all] Should we use MathJaX in Javadoc on all repos?

> > For those unfamiliar with MathJaX, is the javascript mechanism for > accommodating for LaTeX (the math typesetting language, written by Donald > Knuth) in html. > > It could be convenient to use mathematical notation in our javadoc generally. +1 > That said, Java doesn’t do this so it

Re: [Rng] New stress test application

t verses OpenJDK rather than the hardware. > > For the stress test the processor speed is not relevant (output of an RNG > should be the same) unless studying the run times for the test. > > Thoughts? I'd tend

Re: [Rng] New stress test application

eneric amd64 > # > # Analyzer: > /home/ah403/git/commons-rng/commons-rng-examples/examples-stress/stdin2testu01 > SmallCrush > # > # Start: 2019-04-03 16:40:30 > # > # > # End: 2019-04-03 16:40:55 > # > # Exit val

Re: [lang] Towards 3.9

> Any thoughts on doing a 3.9 release of [lang]. I think Benedikt want’s us to > go up with what we have. Any thoughts for or against doing a release? Any objection to fixing https://issues.apache.org/jira/projects/LANG/issues/LANG-1442 ?

Re: [GSoC] Submission of Final Draft for GSoC Proposal

gle.com/document/d/1dKwGTDYWrqae26v3DdLljvZw9reEfaO5h2vyO1rWRG8/edit?usp=sharing Looks OK to me. Gilles P.S. Whenever you have time, don't hesitate to start contributing. > > Regards, > Abhishek - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.

Re: [GSoC] Agile approach to project mentoring

working in a > geographically remote agile group would be useful to know.) > > Opinions are welcome. > > Alex > > > [1] https://google.github.io/gsocguides/student/writing-a-proposal > > [2] https://

Re: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

two "steps" can be repeated for each RNG which you are going to contribute. But as I said there is no strict order: if you are stuck with one (e.g. missing a reference implementation, or cannot compile it for some reason), you could start working on another that may prove more straightfor

Re: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

ou actually find all the needed resources for a given task, the schedule will be quite different... Regards, Gilles Le mar. 26 mars 2019 à 19:02, Abhishek Dhadwal a écrit : > > Dear Gilles Sir, > Thank you for the feedback! I’ve made the changes as requested. Would you > kindly rev

Re: [numbers-fraction] merging changes

Hello Eric. Le mar. 26 mars 2019 à 17:22, Eric Barnhill a écrit : > > I'm rebasing fraction to master and the next merge is looking tricky. > Gilles, am I correct that you have added an interface and some methods to > Fraction, and pushed this to master? I don't think so. Last c

Re: [All][RNG][Numbers] Broken links on the generated site

Anyone has a clue about those issues? Le jeu. 21 mars 2019 à 16:48, Gilles Sadowski a écrit : > > Hi. > > Somehow, that page contains invalid links (for un/subscribe): > http://commons.apache.org/proper/commons-rng/mailing-lists.html > > Furthermore, the page itself has

Re: [Rng] JDK 11 javadoc support for JPMS modules

do we target to use for the release? Is it JDK 9 or do we > switch to 11? >From other discussion threads on this ML, it's seems that the interesting targets are now 8 and 11. So, I'd say that for "commons-rng-examples", it's fine to switch from 9 to 11 (if you think it's the b

Re: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

Thanks for the document. I've made some comments. Let's see whether Alex has something to add. Regards, Gilles Le lun. 25 mars 2019 à 14:30, Abhishek Dhadwal a écrit : > > Dear Sir, > The revised GSoC proposal has been created(minus the about me section), and > the Goog

Re: [commons-rng] 01/04: RNG-82: Add XorShift1024StarPhi generator

gt; + * be used; if smaller, the remaining elements will be automatically > + * set. > + * A seed containing all zeros will create a non-functional generator. > + */ > +protected XorShift1024Star(long multiplier, long[] seed) { > +this.multiplier = multiplier; > s

Re: [Rng] PractRand

JIRA report created: https://issues.apache.org/jira/projects/RNG/issues/RNG-86 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Re: [Rng] User Guide Quality section

agined that one would want to be able to explicitly see the limitation of some algorithm. A "null" seed is convention for telling the library to provide a good sequence without much hassle, but if a user says that the seed is zero, then it might b

Re: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

he "Commons Math" library and tried to provide a framework that would be easy to use[3] (for users and contributors), but it's hard to know how newcomers approach the result. Alex went through this, so he can probably share his experience. Best, Gilles [1] http://commons.apache.org/pro

Re: [Rng] PractRand

NG" page. > > It may provide a useful alternative to Dieharder or TestU01. I supports > direct calls to the test suite using an API or piped data from stdin. Sure; it would be nice to expand the "quality" table of the userguide. [And IIUC there are RNG implementations wh

Re: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

20 lines of code each. Most time will probably be spent porting from C (with its caveat of data type adaptation), ensuring full coverage and reproducibility of the reference implementation's output. That is to say that we should perhaps add additional task(s)... An obvious one would be to mentio

Re: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

uses 0.8.0 > commons parent 47 defines 0.8.1 > commons parent 48-SNAPSHOT defines 0.8.2 > > So I’ve upgraded to 0.8.3 in commons-rng-parent. You should be able to build > the package now. Thanks! Gilles > > Note: I still get a problem on Java 11 when building the site. This is

Re: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

Hi. I see that you use Java 11. Can you try with a different version? We only know that the build should work with Java 6, 7, 8, and 9. Actually, it would be a nice "micro-task" to figure out how to fix that issue (confirmed to also happen with Java 10). Regards, Gilles Le sam. 23 m

Re: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

es) > > >Perhaps start to fill the "application template".[1] > >That way, we can perhaps focus on specific questions > >you may have for the particular task that interested > >you. > Yes sir, I’ll fill up the form application and send it via mail here ? Yes.

Re: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

these forms of projects. Perhaps start to fill the "application template".[1] That way, we can perhaps focus on specific questions you may have for the particular task that interested you. > But, I would be open for any and all suggestions, sir. > A suggestion is to have a look at

Re: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

ainly not a requirement; usage is pretty straightforward in the context of this project, and most of the "magic" is handled by the configuration file(s) shipped with the project's code. At this point, you should be fine with running this command (from within the directory where you "clone"d the

Re: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

missing > from the description. > I wanted to know about any and all micro tasks/screening tests I should > undergo before preparing and submitting my draft proposal for the project on > 25th. I don't understand what yo

Re: [all] What versions of java do we support?

e work for Java 11. Regarding later > versions of Java I’m a tad agnostic currently as we are less certain with > their stability. > > What are folks’ thoughts? I don't understand the question/issue. Isn't Java motto "Build Onc

Re: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

ore specific about what you are missing from the description. >I read the JIRA site about the issues it faces, the user guide and the > Wikipedia site about the generator. Hence, on the recommendation of Gilles > sir from the project’s JIRA site, I joined this mailing list in

[All][RNG][Numbers] Broken links on the generated site

] available from the repositories [local (/home/gilles/.m2/repository), central (https://repo.maven.apache.org/maven2)] -> [Help 1] ---CUT--- Regards, Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additio

Re: [Rng] New XoShiRo generators

tXorComposite : 0, 0, 0 : 625.8 +/- 0.2 > >> > >> The incorrect big-endian byte order: > >> > >> XorShiftXorComposite : 92, 89, 90 : 986.7 +/- 4.3 > >> XorShiftSerialComposite : 75, 74, 76 : 632.0 +/- 2.3 > >> > >> (I did not run th

Re: [Rng] New XoShiRo generators

2 > > The incorrect big-endian byte order: > > XorShiftXorComposite : 92, 89, 90 : 986.7 +/- 4.3 > XorShiftSerialComposite : 75, 74, 76 : 632.0 +/- 2.3 > > (I did not run the control.) > > This makes a fair bit of difference as it did for dieharder. So the byte > ord

Re: [Rng] New XoShiRo generators

undefined Le mer. 20 mars 2019 à 21:39, Alex Herbert a écrit : > > > > > On 20 Mar 2019, at 18:22, Gilles Sadowski wrote: > > > >>> [...] > >>> Perhaps the "RandomStressTester" should be made more flexible > >>> an

Re: [Rng] New XoShiRo generators

llow e.g.: TWO_CMRES 3 TWO_CMRES() 3 TWO_CMRES(1,2) 3 > I suppose it could be updated to require an input text list (as per your > example) but if called with no arguments it can print out a default text &

Re: [Rng] New XoShiRo generators

Le mer. 20 mars 2019 à 15:04, Alex Herbert a écrit : > > > On 20/03/2019 13:08, Gilles Sadowski wrote: > > > >> - Perhaps there is another place for them? > >> > >> I am happy to not clutter the source repo and keep them somewhere for > >>

Re: Google Summer of Code 2019 Mentor Registration

Hi Eric. Le mar. 12 mars 2019 à 20:02, Eric Barnhill a écrit : > > On Tue, Mar 12, 2019 at 11:48 AM Gilles Sadowski > wrote: > > > > > There are also a couple of CM packages that would be worth porting > > to [Numbers] or their own component: > >

Re: [Rng] New XoShiRo generators

erestingly passing the correct byte order lowers the number of > failures. There are still lots. > > And BigCrush (with the fix for passing the correct byte order): > > XorShiftSerialComposite : 40, 39, 39 : 608.2 +/- 3.9 > XorShiftXorComposite : 54, 53, 53 : 646.8 +/- 10.9 > SplitXorComposite : 0, 0, 0 : 625.8 +/- 0.2 Curious to know whether it is also affected by the byte ordering. > > So I think this means we deprecate XOR_SHIFT_1024_S. > > I can rebase the PRs for the new generators and merge them in. > > > For reference here are the systematic failures (in case you like to read > about the tests that are failing): > > [...] Hmm, I'm among those happy enough to be able to choose a generator better than "java.util.Random". ;-) Best regards, Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Re: [Rng] New XoShiRo generators

Hi Alex. Le mer. 20 mars 2019 à 01:32, Alex Herbert a écrit : > > > > > On 19 Mar 2019, at 15:24, Gilles Sadowski wrote: > >> > >> I am currently rerunning the dieharder test for the XorShift1024Star > >> composites since that requires a littl

Re: [Rng] New XoShiRo generators

dumper and stress test launcher). > I think the functionality is better as two programs to avoid doing too > much in the RandomStressTester. Also I do not see the need to dump > output from a list of 15+ generators. +1 > I can add flag arguments to be used to specify which file to

Re: [Rng] New XoShiRo generators

Le mar. 19 mars 2019 à 10:26, Alex Herbert a écrit : > > > > > On 19 Mar 2019, at 10:35, Gilles Sadowski wrote: > > > >>> [...] > >> > >> Given all the stress tests will be rerun shall I go ahead and reorder the > >>

Re: [Rng] New XoShiRo generators

of bits with n from 1 to 16. Other tests using non overlapping > tuples such as rgb_bitdist (-d 200) use n 1 to 12. > > Reversing the bytes in the Java code is the easiest option. +1 [With an option flag for selecting whether the output should be BE or LE.] Best, Gilles > Others are

Re: [Rng] New XoShiRo generators

Le lun. 18 mars 2019 à 16:49, Alex Herbert a écrit : > > > On 18/03/2019 14:12, Gilles Sadowski wrote: > > Hi. > > > >>>> [...] > >>>> > >>>> One actual issue is that we are testing long providers using the long to > >>

Re: [Rng] New XoShiRo generators

The XorShiftXorComposite crashed after 2 hours about 1/4 of the results file > complete. I am running again so I can monitor it for memory usage. Something > in the BigCrush suite just cannot handle this generator output. Strange... Regards, Gilles >>> [...] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Re: [Rng] New XoShiRo generators

Le dim. 17 mars 2019 à 01:01, Alex Herbert a écrit : > > > > > On 16 Mar 2019, at 23:10, Alex Herbert wrote: > > > > > > > >> On 16 Mar 2019, at 02:54, Gilles Sadowski >> <mailto:gillese...@gmail.com>> wrote: > >>> T

Re: [Rng] New XoShiRo generators

below ... ] Gilles > > > > > > The c standard for long states that it can be 32-bits or more! So to check > > what happens on my 64-bit test machine: > > > > #include > > #include > > #include > > > > int main(void){ > > pri

Re: [Rng] New XoShiRo generators

Hi. Le ven. 15 mars 2019 à 19:00, Alex Herbert a écrit : > > > > > On 15 Mar 2019, at 17:37, Gilles Sadowski wrote: > > > > Hi Alex. > > > > Le ven. 15 mars 2019 à 14:08, Alex Herbert a > > écrit : > >> > >> FYI. > >> &g

Re: [Rng] New XoShiRo generators

am already seeing a > lot of failures for the composites. Thanks for the update. It's not clear to me why the other version of the interfacing code would be more forgiving. Gilles > > Results should be complete before the end of today. > > Alex > > ---

Re: [Rng] User Guide Quality section

At first sight, I don't think it's worth making this sort of requirements (unless everything can be automated to provide the sorted output for free). Regards, Gilles > > > The order in PR #30 for the XorShift1024StarPhi generator adds to the > RandomSource enum directly after XOR_SHIFT

Re: [Rng] New XoShiRo generators

Hello Alex. Le mer. 13 mars 2019 à 15:37, Alex Herbert a écrit : > > On 13/03/2019 02:20, Gilles Sadowski wrote: > > Le mar. 12 mars 2019 à 22:34, Alex Herbert a > > écrit : > >> > >> > >>> On 12 Mar 2019, at 17:12, Gilles Sadowski wrote: > &

Re: [Rng] Merge outstanding PRs for construction speed baseline

Le mer. 13 mars 2019 à 00:19, Alex Herbert a écrit : > > > > > On 12 Mar 2019, at 16:58, Gilles Sadowski wrote: > > > > [Replying to the ML.] > > > > Le mar. 12 mars 2019 à 13:00, Alex Herbert > <mailto:alex.d.herb...@gmail.com>> a écrit :

Re: [Rng] New XoShiRo generators

Le mar. 12 mars 2019 à 22:34, Alex Herbert a écrit : > > > > > On 12 Mar 2019, at 17:12, Gilles Sadowski wrote: > > > > [Replying to list.] > > > > Le mar. 12 mars 2019 à 15:39, Alex Herbert > <mailto:alex.d.herb...@gmail.com>> a écrit : > &

Re: Google Summer of Code 2019 Mentor Registration

" package). As for the "o.a.c.math4.ml" package, it should be fairly easy to port it to its own component, as there are no dependencies towards other CM packages. It could be worth having a small component focused on classification. WDYT? Gilles > > Eric > > > > > On

Re: [GSoC] Example Issues From 2018 or upcoming 2019

Hi Rob. Le mar. 12 mars 2019 à 16:09, Rob Tompkins a écrit : > > Hey guys (or maybe Gilles specifically), > > It looks like a good example for GSoC jira issues is: > https://issues.apache.org/jira/browse/RNG-32 > <https://issues.apache.org/jira/browse/RNG-32>. Sure; al

Re: [Rng] New XoShiRo generators

[Replying to list.] Le mar. 12 mars 2019 à 15:39, Alex Herbert a écrit : > > > On 12/03/2019 15:33, Gilles Sadowski wrote: > > Hi Alex. > > Le mar. 12 mars 2019 à 12:53, Alex Herbert a écrit > : > > On 11/03/2019 23:44, Gilles Sadowski wrote: > > Hello. &

Re: [Rng] Merge outstanding PRs for construction speed baseline

[Replying to the ML.] Le mar. 12 mars 2019 à 13:00, Alex Herbert a écrit : > > > On 11/03/2019 23:54, Gilles Sadowski wrote: > > Le ven. 8 mars 2019 à 18:12, Alex Herbert a > > écrit : > >> Hi, > >> > >> I'd like to start on improving the metho

[Geometry] GSoC 2019

Hello. If there are tasks which you think could be completed as part of GSoC, now is the time to advertize them on JIRA (by applying the label "gsoc2019"). Regards, Gilles - To unsubscribe, e-mail: de

Re: Google Summer of Code 2019 Mentor Registration

at of course (DRY), but in practice, I've witnessed from up close (it happened right here) that people prefer duplication over modularization ("dogfooding"). Best, Gilles > > CheersBruno > > On Tuesday, 12 March 2019, 1:24:24 pm NZDT, Eric Barnhill > wrote: >

Re: Google Summer of Code 2019 Mentor Registration

Hello. Le mar. 12 mars 2019 à 01:24, Eric Barnhill a écrit : > > On Sat, Mar 9, 2019 at 4:56 PM Gilles Sadowski wrote: > > > Hi Eric. > > > > Le ven. 8 mars 2019 à 22:22, Eric Barnhill a > > écrit : > > > > > > I am definitely willin

Re: [Rng] Merge outstanding PRs for construction speed baseline

place than in package "o.a.c.rng.simple"? > > RNG-76: Added primitive long constructor to SplitMix64 > > This is something that will effect the benchmark so I'll merge it after. > It is a trivial change with a noticeable performance gain by avoiding > auto-boxin

Re: [Rng] New XoShiRo generators

Hello. Le jeu. 7 mars 2019 à 00:44, Alex Herbert a écrit : > > > > > On 6 Mar 2019, at 22:57, Gilles Sadowski wrote: > > > >>> > >>> However I will test if XorShift1024Star and XorShift1024StarPhi are > >>> correlated just fo

Re: Google Summer of Code 2019 Mentor Registration

n today's world this is NOT too distant a subject > for commons to cover and I am using those models every day, also it > integrates tightliy with stats. > > However Gilles and I recruited someone to work on stats last year and due > to some sort of communications disaster, they were re

Re: [Parent] RAT check

Le sam. 9 mars 2019 à 23:45, Gary Gregory a écrit : > > Hi all: > > How about making apache-rat:check run automatically in commons-parent? In > the Maven validate phase? > > That would mean one less thing to check when integrating a patch and > validating an RC. +1 [Why

Re: Google Summer of Code 2019 Mentor Registration

Hi. Please send a mail to "private@" as requested in the announce mail. The more people subscribed to "mentors@", the less likely we'll miss administrivia. [In addition to "Commons" as the project, we should probably specify which component(s) we are able to pro

Fwd: Google Summer of Code 2019 Mentor Registration

Hi. Anyone willing to apply (cf. message below)? Regards, Gilles -- Forwarded message - From: Ulrich Stärk Date: ven. 8 mars 2019 à 20:49 Subject: Google Summer of Code 2019 Mentor Registration To: Cc: d...@community.apache.org Dear PMCs, I'm happy to announce that the ASF

Re: [Rng] New XoShiRo generators

Le mer. 6 mars 2019 à 23:07, Alex Herbert a écrit :> > > > > On 6 Mar 2019, at 21:42, Alex Herbert wrote: > > > > > > > >> On 6 Mar 2019, at 21:24, Gilles Sadowski wrote: > >> > >> Hello. > >> > >> Le mer. 6 mars 2019

Re: [Rng] New XoShiRo generators

Hello. Le mer. 6 mars 2019 à 21:49, Alex Herbert a écrit : > > > > > On 6 Mar 2019, at 17:11, Gilles Sadowski wrote: > > > > Do the two variants produce uncorrelated sequences? > > I will test this when I branch a new PR for just this code. IMHO, it's stra

Re: [Rng] New XoShiRo generators

at nothing is obviously bad. In the PR, you mention: > Further changes to the other projects to add the extra providers will be > required when accepted. What changes are you referring to? Gilles > > Thanks, > > Alex > --

Re: [Rng] New XoShiRo generators

Le mer. 6 mars 2019 à 17:27, Alex Herbert a écrit : > > > > > On 6 Mar 2019, at 16:22, Gilles Sadowski wrote: > > > > Hi Alex. > > > > Le mer. 6 mars 2019 à 16:50, Alex Herbert a > > écrit : > >> > >> I would like to merge

Re: [Rng] New XoShiRo generators

Hi Alex. Le mer. 6 mars 2019 à 16:50, Alex Herbert a écrit : > > I would like to merge this PR introducing the new XoShiRo generators: > > https://github.com/apache/commons-rng/pull/20 > > > Can I get a review to check that nothing is obviously

Re: [ALL] Avoiding duplication of work between GitHub PRs and JIRA

ke to stress again that using GitHub for discussion is also duplicating work, and potentially leaves out reviewers. Gilles > > Benedikt > > Am Mi., 6. März 2019 um 15:14 Uhr schrieb Gary Gregory < > garydgreg...@gmail.com>: > > > On Wed, Mar 6, 2019 at 9:06 AM sebb wr

Re: [numbers-fraction] Maven surefire plugin error

Le mar. 5 mars 2019 à 00:29, Alex Herbert a écrit : > > > > On 4 Mar 2019, at 23:10, Gilles Sadowski wrote: > > > > Hi. > > > > Le lun. 4 mars 2019 à 23:21, Eric Barnhill a écrit > > : > >> > >> I am getting a maven error for the s

Re: [numbers-fraction] Maven surefire plugin error

n.plugin.surefire.AbstractSurefireMojo.getForkConfiguration (AbstractSurefireMojo.java:1976) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider (AbstractSurefireMojo.java:) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked (AbstractSurefireMojo.java:954) ---CUT--- Regards, Gilles -

Re: [Rng] Sonar 'bugs'

ps the sonar bugs can be added to the > ‘won’t fix’ list. Done. Regards, Gilles > > UnitSphereSamplerTest.testNextNormSquaredAfterZeroIsValid > GeometricSamplerTest.testProbabilityOfSuccessUnderOneIsValid > > Alex > >

Re: [ALL][RFC] Github subjects don't contain the repo name

+1 Le ven. 1 mars 2019 à 22:27, sebb a écrit : > > The [GitHub] messages sent by g...@apache.org don't say what repo they relate > to. > > This make it difficult to know which component is involved. > > Sometimes the subject includes a JIRA issue, but many subjects give no clue. > > I think it

Re: [CANCEL][LAZY][VOTE] Release Apache Commons Build Plugin Maven Mojo 1.10 based on RC1

Le mar. 26 févr. 2019 à 15:53, sebb a écrit : > > On Tue, 26 Feb 2019 at 14:49, Rob Tompkins wrote: > > > > With the -1, I cancel this RC. And, with Gary’s comment, I’ll release the > > release plugin first then build, then patent. > > What does 'patent' mean here? CP maybe. ;-) >> [...]

Re: [Rng] Jira permissions

nk issue as my apache login is aherbert and > Jira is alexherbert. Better first ask INFRA: https://issues.apache.org/jira/projects/INFRA Regards, Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For addi

Re: [VOTE] Redirect github notifications to issues@

-1 to keep things as is +1 Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Re: [Rng] README.md and broken javadoc link

ofile became mandatory. Is there a > > way to have it activated automatically when necessary (e.g. when compiling > > with a JKD >= 8)? > > > > Gilles > > I’ve removed the linux distribution version of OpenJDK 9 and manually > installed OpenJDK 9, 10 and 11. >

Re: [Rng] README.md and broken javadoc link

Hello. Le dim. 17 févr. 2019 à 23:57, Alex Herbert a écrit : > > Hi Gilles, > > This is related to the fix I made for MathJax. It apparently is not as simple > as I thought, i.e. this was a hidden tag only for JDK 8. This tag is not > officially documented so there is no

Re: [Rng] README.md and broken javadoc link

@options @package ---CUT--- Command line was: $ JAVA_HOME=/usr/lib/jvm/java-9-openjdk-amd64/ mvn -Pcommons-rng-examples clean site site:stage Regards, Gilles P.S. I'd wait for the new RNG implementations to be in "master" before updating the live site (so that "current" will re

Re: [Rng] README.md and broken javadoc link

doc; the modules can be seen as separate libraries with different target audiences. The broken link in README.md should be replaced by links to the each of the modules. Regards, Gilles > > Alex > - To unsubscribe,

Re: [All, Math, Statistics] MathJax support

Le ven. 15 févr. 2019 à 12:15, Alex Herbert a écrit : > > > On 15/02/2019 02:56, Gilles Sadowski wrote: > > Le jeu. 14 févr. 2019 à 16:54, Alex Herbert a > > écrit : > >> Commons RNG uses MathJax as a script to add support for rendering > >> equations

Re: [All, Math, Statistics] MathJax support

h all the projects but e.g. [Math, Statistics] still > use . Thanks. Don't hesitate to fix them too. Gilles > > Regards, > > Alex > > [1] > http://maven.apache.org/plugins-archives/maven-javadoc-plugin-2.10.4/javadoc-mojo.html#additionalparam > > [2] > https://mav

Re: [commons-rng] 02/02: The commons-math distributions can use a null random generator

Hi. Le mer. 13 févr. 2019 à 21:21, Alex Herbert a écrit : > > > > > On 13 Feb 2019, at 17:52, Gilles Sadowski wrote: > > > >> Le mer. 13 févr. 2019 à 18:47, Alex Herbert a > >> écrit : > >> > >>> On 13/02/2019 17:35, Gilles Sadowski

Re: [STATISTICS] Possible imprecision or bias of BinomialDistribution.inverseCumulativeProbability() or NormalDistribution.inverseCumulativeProbability()

as in either > BinomialDistribution.inverseCumulativeProbability(), or > NormalDistribution.inverseCumulativeProbability(), or both. Thanks for your interest. Review, documentation, unit tests and patches are welcome. :-) Regards, Gilles > > See > https://stats.stackexchange.com/questions/392281/a

Re: [RNG] Allow exceptions from random generator constructors

;RandomSource" (or use at your own risk); hence the logic for ensuring, as much as possible, a good RNG must be done there (if not already implemented by the reference implementation, as is the case e.g. for "MersenneTwister"[1]). Best, Gilles [1] http://commons.apache.org

Re: [commons-rng] 02/02: The commons-math distributions can use a null random generator

Le mer. 13 févr. 2019 à 18:47, Alex Herbert a écrit : > > On 13/02/2019 17:35, Gilles Sadowski wrote: > > Hello. > > > > Le mer. 13 févr. 2019 à 17:20, a écrit : > >> This is an automated email from the ASF dual-hosted git repository. > >> >

Re: [commons-rng] 02/02: The commons-math distributions can use a null random generator

d3ec655fffe8 > Author: aherbert > AuthorDate: Wed Feb 13 16:20:21 2019 + > > The commons-math distributions can use a null random generator Not a good move, I 'd think: this constructor has disappeared from the development version of CM.[1] Regards, Gilles [1] http://commo

Re: Reply-To settings (was: [vote] fix the misconfiguration of the dev@ mailing list)

n, 11 Feb 2019 at 07:08, sebb wrote: > > > > On Mon, 11 Feb 2019 at 12:33, Gilles Sadowski wrote: > > > > > > Le lun. 11 févr. 2019 à 11:16, sebb a écrit : > > > > > > > > On Mon, 11 Feb 2019 at 09:24, Gilles Sadowski > > > >

Re: [RNG, ALL] Checkstyle version

he current workaround to get functionality within an IDE is to maintain > a local copy of the checkstyle.xml outside the source tree, updated for > checkstyle 8, and point the IDE plugin at that. Unless I'm missing something that needn't be so. Regards, Gilles > > Thanks for th

Re: Reply-To settings (was: [vote] fix the misconfiguration of the dev@ mailing list)

Hi. Le lun. 11 févr. 2019 à 16:08, sebb a écrit : > > On Mon, 11 Feb 2019 at 12:33, Gilles Sadowski wrote: > > > > Le lun. 11 févr. 2019 à 11:16, sebb a écrit : > > > > > > On Mon, 11 Feb 2019 at 09:24, Gilles Sadowski > > > wrote: > > >

Re: [RNG, ALL] Checkstyle version

used across commons No need; people upgrade the default version in CP without consensus; each project can easily override the property defined in CP to use another version. > and > any reason to not upgrade. There may be legacy reasons I am unaware of. Probably no reason. Regards, Gilles

<    8   9   10   11   12   13   14   15   16   17   >