On Thu, 25 Mar 2010 at 09:37PM -0700, William Stein wrote:
> This is at least the 20th email I've seen over the years that starts
> "I'm trying to use a piecewise function, and it doesn't seem to work".
...and I was thinking, "there's been, what, 19 or so emails about
this, so surely these problem
You could try
sage: R. = QQ[]
sage: f1 = x
sage: f2 = R(1)
sage: f = Piecewise([[(0,1),f1],[(1,2),f2]])
sage: f.plot()
sage: f(3/2)
1
or
sage: f1 = lambda x: x
sage: f2 = lambda x: 1
sage: f = Piecewise([[(0,1),f1],[(1,2),f2]])
sage: f(3/2)
1
sage: f.plot()
or
sage: x = var("x")
sage: f1(x
2010/3/25 Dan Drake :
> Hello,
>
> I'm trying to use a piecewise function, and it doesn't seem to work very
> well.
This is at least the 20th email I've seen over the years that starts
"I'm trying to use a piecewise function, and it doesn't seem to work".
Whoever rewrites Piecewise function (and
On 03/25/2010 08:49 PM, William Stein wrote:
Hi,
I was trying to understand why certain modular symbols code was too
slow, and ran across a method that looked like this (in
modular/modsym/element.py):
def modular_symbol_rep(self):
try:
return self.__modular_symbols
On 03/25/2010 09:40 PM, Tom Boothby wrote:
My guess is that it would be very easy to speed up the @cached_method and
@cached_function decorators.
I agree. IIRC, the majority of the problem is in
sage/misc/function_mangling.py, and my fault.
There is a lot of code in there that gets executed
Hello,
I'm trying to use a piecewise function, and it doesn't seem to work very
well. If I do
f = Piecewise([((0, 1), x), ((1, 2), 1)], x)
and try to evaluate f(3/2), it complains that Integer objects are not
callable. The docstring for Piecewise says "if the optional var is
specified, then
> My guess is that it would be very easy to speed up the @cached_method and
> @cached_function decorators.
I agree. IIRC, the majority of the problem is in
sage/misc/function_mangling.py, and my fault.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from th
On 03/25/2010 08:49 PM, William Stein wrote:
Hi,
I was trying to understand why certain modular symbols code was too
slow, and ran across a method that looked like this (in
modular/modsym/element.py):
def modular_symbol_rep(self):
try:
return self.__modular_symbols
Hi,
I was trying to understand why certain modular symbols code was too
slow, and ran across a method that looked like this (in
modular/modsym/element.py):
def modular_symbol_rep(self):
try:
return self.__modular_symbols
except AttributeError:
A = self.
I don't seem able to edit my previous message to add this information,
but the GiNaC team seems to have picked up the bug report and patched
it:
http://www.cebix.net/pipermail/ginac-devel/2010-March/001724.html
On Mar 24, 4:19 pm, G B wrote:
> Thanks Burcin. I'm having problems getting sage to d
On Thursday 25 March 2010, Minh Nguyen wrote:
> Hi folks,
>
> Computer news site CNET has a story [1] on the 2010 CanSecWest Pwn2Own
> security contest. One of the contest winners is a researcher from
> Université du Luxembourg by the name of Ralf-Philipp Weinmann [2]. I
> wonder if this person is
Hi folks,
Computer news site CNET has a story [1] on the 2010 CanSecWest Pwn2Own
security contest. One of the contest winners is a researcher from
Université du Luxembourg by the name of Ralf-Philipp Weinmann [2]. I
wonder if this person is the same person who wrote a cryptanalysis PhD
thesis as l
Greetings everyone,
This year, there will be two days of tutorials (June 28th and 29th) before the
main SciPy 2010 conference. Each of the two tutorial tracks (intro, advanced)
will have a 3-4 hour morning and afternoon session both days, for a total of 4
intro sessions and 4 advanced sessions.
T
2010/3/25 Jason Grout :
> On 03/25/2010 12:53 PM, William Stein wrote:
>>
>> 2010/3/25 slabbe:
>>>
>>> Hi sage-devel,
>>>
>>> If I want to draw a 3d point of size 100 in Sage, I do :
>>>
>>> sage: point((2,3,4), size=100)
>>>
>>> but for a 2d point, the argument is not the same :
>>>
>>> sage: poin
On 03/25/2010 12:53 PM, William Stein wrote:
2010/3/25 slabbe:
Hi sage-devel,
If I want to draw a 3d point of size 100 in Sage, I do :
sage: point((2,3,4), size=100)
but for a 2d point, the argument is not the same :
sage: point((2,3), pointsize=100)
In the ticket #8599 (which needs review)
2010/3/25 slabbe :
> Hi sage-devel,
>
> If I want to draw a 3d point of size 100 in Sage, I do :
>
> sage: point((2,3,4), size=100)
>
> but for a 2d point, the argument is not the same :
>
> sage: point((2,3), pointsize=100)
>
> In the ticket #8599 (which needs review), I propose to change
> ``poin
On 03/25/2010 12:16 PM, Andrey Novoseltsev wrote:
Are the decorators used in these patches (rename_keyword and options)
documented somewhere? I cannot find their description.
Yes. In plots/misc.py
I agree. It would be nice to make these more generally available than
plots.
Thanks,
Jaso
Are the decorators used in these patches (rename_keyword and options)
documented somewhere? I cannot find their description.
In general, it could be good to have a list of all the decorators
available in Sage somewhere (like in the Developer's Guide, perhaps).
Thank you,
Andrey
--
To post to th
On 03/25/2010 08:30 AM, slabbe wrote:
No objection. But you need to provide deprecation warnings before
removing any long used things in Sage.
For now, I use the rename_keyword(pointsize='size') so that both
works. I replaced every occurence of pointsize for size in the doc so
that people shoul
On 03/25/2010 03:15 AM, Minh Nguyen wrote:
Hi folks,
I apologize for this belated celebration note.
March 24th of each year is observed as Ada Lovelace Day [1]. It is an
international celebration of the achievements of women in science and
technology. The daughter of the English poet Lord Byron
> No objection. But you need to provide deprecation warnings before
> removing any long used things in Sage.
For now, I use the rename_keyword(pointsize='size') so that both
works. I replaced every occurence of pointsize for size in the doc so
that people should forget soon about pointsize. Maybe
> No objection. But you need to provide deprecation warnings before
> removing any long used things in Sage.
For now, I use the rename_keyword(pointsize='size') so that both
works. I replaced every occurence of pointsize for size in the doc so
that people should forget soon about pointsize. Maybe
On Thu, 25 Mar 2010 at 05:39AM -0700, Dima Pasechnik wrote:
> What exactly are your virtual machines?
64-bit Ubuntu Lucid in VirtualBox 3.0.8; 64-bit Ubuntu Hardy in
VirtualBox 2.1.4. I've built 4.3.4 in 32- and 64-bit in a bunch of other
configurations and they all work. I don't know what is spec
What exactly are your virtual machines?
I tried your example on a VMWare VM (x86_64) running Debian testing
distro,
all works..
Dima
On Mar 25, 11:58 am, Dan Drake wrote:
> Hello,
>
> Two builds of 4.3.4 are not doctesting properly for me; both are failing
> the doctest for free_module.py becau
Ah hah. That looks much better to me. Thanks Alec.
Gonna have a little play around with this now. :D
Joal Heagney
On Mar 15, 10:35 am, Alec Mihailovs wrote:
> On Mar 12, 4:22 am, Joal Heagney wrote:
>
>
>
> > Hi guys and gals,
> > Currently I'm attempting to fit the following data to the genera
Hi!
For the simple case of exterior algebras
there exists already ring creation code in
the track ticket.
It might be a little bit hacky, but it works for now.
What is mainly needed, is cleaning the construction for Sage
class hierarchies and coercions.
Cheers,
Michael
Am 25.03.2010 um 10:10 s
Ok, i have seen how to define them in singular properly. Something
like this:
ring r=0,(x,y,z),lp;
def a=nc_algebra(-1,0);
setring a;
ideal i=x2,y2z2;
i=std(i);
qring e=i;
setring e;
creates an exterior algebra. The command Exterior() from the package
nctools.lib does essentially the same.
I thi
Hi,
No objection. But you need to provide deprecation warnings before
removing any long used things in Sage.
Kwankyu
--
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
Hi sage-devel,
If I want to draw a 3d point of size 100 in Sage, I do :
sage: point((2,3,4), size=100)
but for a 2d point, the argument is not the same :
sage: point((2,3), pointsize=100)
In the ticket #8599 (which needs review), I propose to change
``pointsize`` for ``size`` because I think `
Hi folks,
I apologize for this belated celebration note.
March 24th of each year is observed as Ada Lovelace Day [1]. It is an
international celebration of the achievements of women in science and
technology. The daughter of the English poet Lord Byron, Ada Lovelace
is recognized as the first com
30 matches
Mail list logo
