Hi Mike!
On 7 Sep., 01:05, Mike Hansen <mhan...@gmail.com> wrote:
> On Mon, Sep 6, 2010 at 3:56 PM, Simon King <simon.k...@nuigalway.ie> wrote:
> > So indeed, it is not "Solaris vs. non-Solaris" but "little vs. big
> > endian", as the GAP people suspected.
>
> This is what I said in my first response and can be taken care of with
> current_randstate().set_seed_gap().
>
> Core2:
>
> sage: set_random_seed(100)
> sage: current_randstate().set_seed_gap()
> sage: gap.eval('List([1..10],i->Random(1,100000));')
> '[ 80761, 80557, 8462, 25730, 32000, 92371, 85402, 52347, 17181, 2889 ]'
>
> t2:
>
> sage: set_random_seed(100)
> sage: current_randstate().set_seed_gap()
> sage: gap.eval('List([1..10],i->Random(1,100000));')
> '[ 80761, 80557, 8462, 25730, 32000, 92371, 85402, 52347, 17181, 2889 ]'
That's VERY cool!
I did not expect that it is so carefully implemented - I thought it is
just calling the GAP commands, without a special case for endianness.
So, I will try this. Probably I have to rewrite the tests anyway (the
above sequence is different from the one that I get with
Reset(GlobalMersenneTwister), but at least it probably means that
eventually the ring structures will be computationally unique on all
platforms.
Best regards,
Simon
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
