On Oct 8, 3:31 pm, David Harvey [EMAIL PROTECTED] wrote:
Hello David,
When I start up sage, I get different random number seeds every time,
e.g.
$ ./sage
sage: ZZ.random_element()
2
.
$ ./sage
sage: ZZ.random_element()
-4
The seeding --- at least for this case --- seems to
On 10/8/07, mabshoff [EMAIL PROTECTED] wrote:
On Oct 8, 3:31 pm, David Harvey [EMAIL PROTECTED] wrote:
Hello David,
When I start up sage, I get different random number seeds every time,
e.g.
$ ./sage
sage: ZZ.random_element()
2
.
$ ./sage
sage: ZZ.random_element()
I just looked and this is already
http://trac.sagemath.org/sage_trac/ticket/658
I added my comments to that ticket.
On 10/8/07, William Stein [EMAIL PROTECTED] wrote:
On 10/8/07, mabshoff [EMAIL PROTECTED] wrote:
On Oct 8, 3:31 pm, David Harvey [EMAIL PROTECTED] wrote:
Hello David,
On Oct 8, 7:36 am, William Stein [EMAIL PROTECTED] wrote:
I do encourage David to open a trac ticket about this. He's right that
seeding the random number generator should be possible via a command
line argument at startup.
But which random number generator? libc, Python, libpari, NTL,
On Oct 8, 2007, at 9:34 AM, cwitty wrote:
On Oct 8, 7:36 am, William Stein [EMAIL PROTECTED] wrote:
I do encourage David to open a trac ticket about this. He's right
that
seeding the random number generator should be possible via a command
line argument at startup.
But which random
On Oct 8, 2007, at 9:34 AM, cwitty wrote:
On Oct 8, 7:36 am, William Stein [EMAIL PROTECTED] wrote:
I do encourage David to open a trac ticket about this. He's right
that
seeding the random number generator should be possible via a command
line argument at startup.
But which random
On 10/8/07, Justin C. Walker [EMAIL PROTECTED] wrote:
On Oct 8, 2007, at 9:34 AM, cwitty wrote:
True. However, a few days ago I realized there is a much better
solution to this problem. Use ... in the output. E.g., instead
of something like
sage: sin(1.0)# random low-order bits
On Oct 8, 2007, at 10:37 AM, William Stein wrote:
On 10/8/07, Justin C. Walker [EMAIL PROTECTED] wrote:
On Oct 8, 2007, at 9:34 AM, cwitty wrote:
True. However, a few days ago I realized there is a much better
solution to this problem. Use ... in the output. E.g., instead
of something
Hello,
I'm receving an error message
502 - Bad gateway
The proxy server received an invalid response from an upstream server.
when trying to access to
http://sagetrac.org/sage_trac/
(through an http proxy)
Pablo
--~--~-~--~~~---~--~~
To post to this group,
On Oct 8, 10:10 am, William Stein [EMAIL PROTECTED] wrote:
I agree. However, I strongly encourage people to discuss
this a bit longer in sage-devel before implementing something.
Whatever we do it will likely be easy to implement but hard
to design.
OK, here's my preliminary proposal for a
Hi Carl,
I haven't yet thought hard about the details of what you propose, but
I'm just curious why you are suggesting to use gmp_randstate_t as the
most basic type.
One property I would like the system to have is: the most basic
random number generator should be insanely fast, even if
Hi,
I wanted to let you know that I've started uploading video links for
the Sage Days 5 talks
here (there are links from the schedule to Google Video):
http://wiki.sagemath.org/days5/sched
Video for all the talks will eventually be uploaded, though it takes a while. ..
The above is just a
12 matches
Mail list logo
