- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] WELL512 PRNG

by Stephane Ducasse

I remember that I collected many of them and put them in PolyMath. On Fri, Nov 9, 2018 at 6:40 PM Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > > On Fri, Nov 9, 2018 at 5:54 PM Norbert Hartl <norbert(a)hartl.name> wrote: > >> I was about to say letâs add this to the Cryptography package ð >> >> > How much RNGs are implemented in the crypto packages ? > Maybe we need to sync one day :-) > > -- > Serge Stinckwic > h > > Int. Research Unit > on Modelling/Simulation of Complex Systems (UMMISCO) > Sorbonne University > (SU) > French National Research Institute for Sustainable Development (IRD) > U > niversity of YaoundÃ© I, Cameroun > "Programs must be written for people to read, and only incidentally for > machines to execute." > https://twitter.com/SergeStinckwich >

Nov. 9, 2018

Action list for Pharo 70 release

by Stephane Ducasse

Hi The team got a meeting about the final points to address before the release. Here is the summary of action points one and to do to the meeting next month. Done: Release - version info from tag Calypso - Traits (In calypso repository, not yet in Pharo) - Extensions (In calypso repository, not yet in Pharo) Doing: Release - File name / repository should take tag information => Esteban - Launcher should be updated automatically without having to touch it => Christophe - Update Zeronconf => Esteban + Vincent Calypso - Review refactorings => Vincent - Integrated Spotter shortcut => Esteban - Selection/Navigation => ??? Selection glitches (see why sometimes focus is broken and cmd+W is wrong) => Pavel FFI recompilation of Structures => Guille Backport Unicode Support from Launcher => Guille FT2 bug, update Freetype library => Esteban Cleaning pharo-scripts repository => ??? Start preparing changes log => Marcus >From what I understood the window 64 bits is to unstable to be proposed. Stef

Nov. 9, 2018

Re: [Pharo-dev] PharoLauncher : Image version determination error

by Esteban Maringolo

El vie., 9 nov. 2018 a las 15:02, Alistair Grant (<akgrant0710(a)gmail.com>) escribiÃ³: > Hi Christophe, > > On Fri, 9 Nov 2018 at 15:15, Christophe Demarey > <christophe.demarey(a)inria.fr> wrote: > > > > For now, to work around the problem, I will add a windows to easily > update the VMs from the launcher UI. > > It should be possible to check if there is a new VM by just requesting > the headers for the download URL. You could then add a "Check for > new VM" button / menu item, and maybe even have a setting to do it > each time the launcher is started. > > Or "check for new VMs on startup" kind of thing. I like that approach. Esteban A. Maringolo

Nov. 9, 2018

Re: [Pharo-dev] PharoLauncher : Image version determination error

by Alistair Grant

Hi Christophe, On Fri, 9 Nov 2018 at 15:15, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > For now, to work around the problem, I will add a windows to easily update the VMs from the launcher UI. It should be possible to check if there is a new VM by just requesting the headers for the download URL. You could then add a "Check for new VM" button / menu item, and maybe even have a setting to do it each time the launcher is started. Cheers, Alistair

Nov. 9, 2018

Re: [Pharo-dev] WELL512 PRNG

by Serge Stinckwich

On Fri, Nov 9, 2018 at 5:54 PM Norbert Hartl <norbert(a)hartl.name> wrote: > I was about to say letâs add this to the Cryptography package ð > > How much RNGs are implemented in the crypto packages ? Maybe we need to sync one day :-) -- Serge Stinckwic h Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) Sorbonne University (SU) French National Research Institute for Sustainable Development (IRD) U niversity of YaoundÃ© I, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich

Nov. 9, 2018

Re: [Pharo-dev] WELL512 PRNG

by Norbert Hartl

I was about to say letâs add this to the Cryptography package ð > Am 09.11.2018 um 15:34 schrieb Serge Stinckwich <serge.stinckwich(a)gmail.com>: > > Can you contribute your code to PolyMath: https://github.com/PolyMathOrg/PolyMath > We have other RNGs available. > > Thank you. > >> On Fri, Nov 9, 2018 at 3:23 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Hi, >> >> By accident I came across a pseudo random number generator that I never heard off before. It is supposed to be pretty good and had a very simple implementation. So I ported it to Pharo. >> >> <class comment> >> >> I am RandomWELL512, a random number generator. >> >> I use the PRNG (Pseudo Randon Number Generator) WELL (Well equidistributed long-period linear) with a 512 bit state. >> >> https://en.wikipedia.org/wiki/Well_equidistributed_long-period_linear >> http://www.iro.umontreal.ca/~lecuyer/myftp/papers/wellrng.pdf >> >> Implementation algorithm (See #nextUInt32) >> >> http://www.lomont.org/Math/Papers/2008/Lomont_PRNG_2008.pdf (Chris Lomont, www.lomont.org) >> >> Usage >> >> RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextUInt32 ] ]. >> >> RandomWELL512 new useUnixRandomGeneratorSeed; in: [ :r | (1 to: 10) collect: [ :i | r next ] ]. >> >> RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextInt: 1000 ] ]. >> >> RandomWELL512 new in: [ :random | | count all | >> random useUnixRandomGeneratorSeed. >> count := 1024 * 1024. >> all := Array new: count streamContents: [ :out | >> count timesRepeat: [ out nextPut: random next ] ]. >> { all min. all max. all average. all stdev } ]. >> >> [ RandomWELL512 new in: [ :random | 1 to: 1e6 do: [ :i | random next ] ] ] timeToRun. >> >> Note that you should create one instance, seed it properly, and keep using it. >> >> </class comment> >> >> It is acceptably fast, generating 1M [0,1) Floats in about 0.1s. I compared the output with a fixed initial state to the C code that I started from and I got the same numbers. Maybe some people find this interesting. >> >> I attached a file out. >> >> Sven >> >> >> > > > -- > Serge Stinckwich > Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) > Sorbonne University (SU) > French National Research Institute for Sustainable Development (IRD) > University of YaoundÃ© I, Cameroun > "Programs must be written for people to read, and only incidentally for machines to execute." > https://twitter.com/SergeStinckwich

Nov. 9, 2018

Re: [Pharo-dev] PharoLauncher : Image version determination error

by Mariano Martinez Peck

On Fri, Nov 9, 2018 at 11:15 AM Christophe Demarey < christophe.demarey(a)inria.fr> wrote: > Hi, > > Le 9 nov. 2018 Ã 14:11, Mariano Martinez Peck <marianopeck(a)gmail.com> a > Ã©crit : > > > > On Fri, Nov 9, 2018, 10:06 Christophe Demarey <christophe.demarey(a)inria.fr > wrote: > >> Hi Mariano, >> >> Le 8 nov. 2018 Ã 20:47, Mariano Martinez Peck <marianopeck(a)gmail.com> a >> Ã©crit : >> > >> > Hi All, >> > >> > I am having this same problem with the #fileDescriptorType: in a >> PharoLauncher 1.4.6 64 bits trying to launch a >> Pharo-7.0.0+rc1.build.1373.sha.c50749c3452952c3572527bed9ea18ec8c674855 (64 >> Bit). >> > >> > Any ideas? >> >> It is because your pharo 70 vm is too old. >> You can drop the pharo/vm folder (or just 70 vm in pharo/vm and in >> pharo/vm/private) and it should work. >> >> >> >> > Hi Christophe, > > Thanks for the workaround. But let me ask.. Wasn't one of the launcher > purposes to automatically download the necessary correct VM for the image > you are creating? To avoid this exact kind of issue? > > > Launcher magic has its boundaries. > The information available to the launcher to determine the appropriate VM > to run an image is: > - the image format number (encoded in the image header) > - the pharo version (system version) of the image (need to run the image > to know that information). > > In your case, you have an image with the same image format number, same > pharo version (7.0) but with incompatible changes requiring a new VM. Pharo > Launcher has no way to get this information. > This problem only happens with moving Pharo versions : the development > version. > > The best option would be to encode the Pharo version as a semantic version > in the header of the image file but it requires a lot of changes. > > For now, to work around the problem, I will add a windows to easily update > the VMs from the launcher UI. > > OK, I understand. Thanks for the explanation Christophe. I can also confirm that the workaround of removing by hand the VM directory did fix my issue. Thanks! -- Mariano http://marianopeck.wordpress.com

Nov. 9, 2018

Re: [Pharo-dev] WELL512 PRNG

by Serge Stinckwich

Can you contribute your code to PolyMath: https://github.com/PolyMathOrg/PolyMath We have other RNGs available. Thank you. On Fri, Nov 9, 2018 at 3:23 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > By accident I came across a pseudo random number generator that I never > heard off before. It is supposed to be pretty good and had a very simple > implementation. So I ported it to Pharo. > > <class comment> > > I am RandomWELL512, a random number generator. > > I use the PRNG (Pseudo Randon Number Generator) WELL (Well equidistributed > long-period linear) with a 512 bit state. > > https://en.wikipedia.org/wiki/Well_equidistributed_long-period_linear > http://www.iro.umontreal.ca/~lecuyer/myftp/papers/wellrng.pdf > > Implementation algorithm (See #nextUInt32) > > http://www.lomont.org/Math/Papers/2008/Lomont_PRNG_2008.pdf (Chris > Lomont, www.lomont.org) > > Usage > > RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextUInt32 ] > ]. > > RandomWELL512 new useUnixRandomGeneratorSeed; in: [ :r | (1 to: 10) > collect: [ :i | r next ] ]. > > RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextInt: 1000 > ] ]. > > RandomWELL512 new in: [ :random | | count all | > random useUnixRandomGeneratorSeed. > count := 1024 * 1024. > all := Array new: count streamContents: [ :out | > count timesRepeat: [ out nextPut: random next ] ]. > { all min. all max. all average. all stdev } ]. > > [ RandomWELL512 new in: [ :random | 1 to: 1e6 do: [ :i | random next ] ] > ] timeToRun. > > Note that you should create one instance, seed it properly, and keep using > it. > > </class comment> > > It is acceptably fast, generating 1M [0,1) Floats in about 0.1s. I > compared the output with a fixed initial state to the C code that I started > from and I got the same numbers. Maybe some people find this interesting. > > I attached a file out. > > Sven > > > > -- Serge Stinckwic h Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) Sorbonne University (SU) French National Research Institute for Sustainable Development (IRD) U niversity of YaoundÃ© I, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich

Nov. 9, 2018

WELL512 PRNG

by Sven Van Caekenberghe

Hi, By accident I came across a pseudo random number generator that I never heard off before. It is supposed to be pretty good and had a very simple implementation. So I ported it to Pharo. <class comment> I am RandomWELL512, a random number generator. I use the PRNG (Pseudo Randon Number Generator) WELL (Well equidistributed long-period linear) with a 512 bit state. https://en.wikipedia.org/wiki/Well_equidistributed_long-period_linear http://www.iro.umontreal.ca/~lecuyer/myftp/papers/wellrng.pdf Implementation algorithm (See #nextUInt32) http://www.lomont.org/Math/Papers/2008/Lomont_PRNG_2008.pdf (Chris Lomont, www.lomont.org) Usage RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextUInt32 ] ]. RandomWELL512 new useUnixRandomGeneratorSeed; in: [ :r | (1 to: 10) collect: [ :i | r next ] ]. RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextInt: 1000 ] ]. RandomWELL512 new in: [ :random | | count all | random useUnixRandomGeneratorSeed. count := 1024 * 1024. all := Array new: count streamContents: [ :out | count timesRepeat: [ out nextPut: random next ] ]. { all min. all max. all average. all stdev } ]. [ RandomWELL512 new in: [ :random | 1 to: 1e6 do: [ :i | random next ] ] ] timeToRun. Note that you should create one instance, seed it properly, and keep using it. </class comment> It is acceptably fast, generating 1M [0,1) Floats in about 0.1s. I compared the output with a fixed initial state to the C code that I started from and I got the same numbers. Maybe some people find this interesting. I attached a file out. Sven

Nov. 9, 2018

Re: [Pharo-dev] PharoLauncher : Image version determination error

by Christophe Demarey

Hi, > Le 9 nov. 2018 Ã 14:11, Mariano Martinez Peck <marianopeck(a)gmail.com> a Ã©crit : > > > > On Fri, Nov 9, 2018, 10:06 Christophe Demarey <christophe.demarey(a)inria.fr <mailto:christophe.demarey@inria.fr> wrote: > Hi Mariano, > > Le 8 nov. 2018 Ã 20:47, Mariano Martinez Peck <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> a Ã©crit : > > > > Hi All, > > > > I am having this same problem with the #fileDescriptorType: in a PharoLauncher 1.4.6 64 bits trying to launch a Pharo-7.0.0+rc1.build.1373.sha.c50749c3452952c3572527bed9ea18ec8c674855 (64 Bit). > > > > Any ideas? > > It is because your pharo 70 vm is too old. > You can drop the pharo/vm folder (or just 70 vm in pharo/vm and in pharo/vm/private) and it should work. > > > > > Hi Christophe, > > Thanks for the workaround. But let me ask.. Wasn't one of the launcher purposes to automatically download the necessary correct VM for the image you are creating? To avoid this exact kind of issue? Launcher magic has its boundaries. The information available to the launcher to determine the appropriate VM to run an image is: - the image format number (encoded in the image header) - the pharo version (system version) of the image (need to run the image to know that information). In your case, you have an image with the same image format number, same pharo version (7.0) but with incompatible changes requiring a new VM. Pharo Launcher has no way to get this information. This problem only happens with moving Pharo versions : the development version. The best option would be to encode the Pharo version as a semantic version in the header of the image file but it requires a lot of changes. For now, to work around the problem, I will add a windows to easily update the VMs from the launcher UI.

Nov. 9, 2018