I'm working on bringing __call__ into the coercion framework. Unlike
coerce, we need to worry about additional arguments besides just the object
x to be cast into the parent (I've included the list of all parent __call__
methods currently defined at the bottom of this e-mail).
Define call_map_fro
On Oct 8, 5:47 pm, David Harvey <[EMAIL PROTECTED]> wrote:
> 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".
Well, it's not a very good reason. It's because I said "Cyt
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 "
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 t
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
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, s
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
>>>
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
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
On 10/8/07, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
> > This would have several advantages. Randomized algorithms could be
> > run repeatably, for testing or debugging. All of our "random"
> > doctests could be tested, instead of ignored.
>
> Some (many?) of the random doctests are the result
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 wh
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
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:
> >
> > Hel
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
> >
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
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 be happening in
random.pxi.
We *really* need a way of specifying a random seed a
Thank you for the information, Micheal.
There is just one minor problem: I'm serving my Civil Service (instead of
miltary service, for conscientious objectors; in German: "Zivildienst") and
I tried IRC right now. I found that all the needed ports are blocked, I
can't even use web access. So I will
17 matches
Mail list logo
