Hi!
I was executing the examples of the Sage Beginner's Guide book when I found a
curious behavior in Sage.
Whenever I launch Sage and define the variable
sage: R = 250e3
and issue the command
sage: who
the output is
Interactive namespace is empty.
If I define other variables and issue aga
"who" prints the newly-defined variables, but R is already defined as the
r-system.org interface. You can redefine it as you want, but as far as
Python is concerned that just changes a variable but doesn't add a new one.
On Tuesday, April 23, 2013 10:34:15 PM UTC+1, João Alberto Ferreira wrote
In Sage 5.8 on a mac. I have a functioning (and licensed) magma on my
computer, and apparently sage is trying to call it.
Victor
R. = QQ[]
F = x^3 + 2*x*(y^2 + y*z + z^2) + y*z*(y + z)
F(0,0,1)
> 0
E = EllipticCurve_from_cubic(F,(0,0,1))
Traceback (most recent call last):
File "", l
Ah, I just found that I should specify the point as a list and not a tuple.
Now it works. However, the error is sure weird and indecipherable!
Victor
On Wednesday, April 24, 2013 8:22:33 AM UTC-4, Victor Miller wrote:
>
> In Sage 5.8 on a mac. I have a functioning (and licensed) magma on my
One more thing: it would be really nice (required?) if
Elliptic_curve_from_cubic would return the morphism that it found (and
perhaps an inverse).
Victor
On Wednesday, April 24, 2013 8:22:33 AM UTC-4, Victor Miller wrote:
>
> In Sage 5.8 on a mac. I have a functioning (and licensed) magma on m
I'm pretty sure I removed that in #3416
On Wednesday, April 24, 2013 1:27:58 PM UTC+1, Victor Miller wrote:
>
> E = EllipticCurve_from_cubic(F,(0,0,1))
>>
>>
>> Traceback (most recent call last):
>> File "", line 1, in
>> File "_sage_input_8.py", line 10, in
>> exec compile(u'ope
Victor,
The code at trac #3416 implements all this properly in Sage. It's an
ancient ticket but the work on it is new, and it is one of the ones where
so many people have wprked on it that there's no-onle left to revview it.
That is a pity since Volker did a very nice job on it. But if you are a
On Tuesday, April 23, 2013 6:15:00 PM UTC+4, kcrisman wrote:
>
>
>
> On Tuesday, April 23, 2013 6:15:23 AM UTC-4, LRN wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> I've attached a sample tex file.
>>
>>
> You are totally cutting-edge! But remember, even with imagemagick,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So, i can do things like:
M = units.length.meter
S = units.time.second
speed = 2 * M/S
speed
and get:
2*meter/second
or (in typesetting mode):
\frac{2 \, \mbox{meter}}{\mbox{second}}
I have three problems with this.
1) Sage prints full names - "mete
On Wednesday, April 24, 2013 9:44:47 AM UTC-4, LRN wrote:
>
>
> On Tuesday, April 23, 2013 6:15:00 PM UTC+4, kcrisman wrote:
>>
>>
>>
>> On Tuesday, April 23, 2013 6:15:23 AM UTC-4, LRN wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> I've attached a sample tex file.
>>
On Wed, 24 Apr 2013 at 06:09PM +0400, LRN wrote:
> So, i can do things like:
> M = units.length.meter
> S = units.time.second
> speed = 2 * M/S
> speed
>
> and get:
> 2*meter/second
>
> or (in typesetting mode):
> \frac{2 \, \mbox{meter}}{\mbox{second}}
>
> I have three problems with this.
I wo
I just installed Sage 5.8 and am running it from the command line. For
some reason, it is filling up my directory with what looks like temporary
files, e.g., threshold.sageJmarTS.py, threshold.sageR9Gfg9, and on and
on. (I attached code contained in a file called 'threshold.sage'. I get
th
On Wed, 24 Apr 2013 at 06:44AM -0700, LRN wrote:
> That said, i've noticed that you're using [scale=.4]. How would it look
> without scale=.4? The point is that DPI info should allow typesetter to
> guess image size correctly, and it should look OK without scaling.
Let me admit my ignorance here
I think this problem has to do with attaching a file. I noticed that
"attach" has been deprecated. Using either 'attach' or '%attach' seems to
cause the proliferation of extra files. The 'load' command or '%runfile'
does not seem to have this behavior. The problem with the 'attach' command
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24.04.2013 20:00, Dan Drake wrote:
> On Wed, 24 Apr 2013 at 06:44AM -0700, LRN wrote:
>> That said, i've noticed that you're using [scale=.4]. How would
>> it look without scale=.4? The point is that DPI info should
>> allow typesetter to guess ima
On Wed, 24 Apr 2013 at 10:31PM +0400, LRN wrote:
> As an experiment, try creating a simple image (say, a rectangle of
> 100x100 pixels), then save it as png, create multiple copies and give
> them different DPI values in Gimp.
The key idea, it seems to me, is that *I* am the one giving the image
d
I've used attach and load for years without ever encountering this
problem. So there must be something about the code in your
threshold.sage file. Without seeing it, it's not likely we can help you.
On Wed, 24 Apr 2013 at 10:57AM -0700, davidp wrote:
> I think this problem has to do with attaching
Ok! thank you!
On Wednesday, April 24, 2013 6:15:06 AM UTC-3, Volker Braun wrote:
>
> "who" prints the newly-defined variables, but R is already defined as the
> r-system.org interface. You can redefine it as you want, but as far as
> Python is concerned that just changes a variable but doesn't
On Wednesday, April 24, 2013 8:53:56 AM UTC-7, davidp wrote:
>
> I just installed Sage 5.8 and am running it from the command line. For
> some reason, it is filling up my directory with what looks like temporary
> files, e.g., threshold.sageJmarTS.py, threshold.sageR9Gfg9, and on and
> on.
I have been using attach and load for years, too, with no problem. I just
checked by attaching a file containing only a simple function called
'hello' that prints 'hello world' when called. I have the same problem.
Thanks,
Dave
On Wednesday, April 24, 2013 2:18:24 PM UTC-7, Dan Drake wrote:
>
Yes! This looks right.
Thanks,
Dave
On Wednesday, April 24, 2013 2:30:09 PM UTC-7, John H Palmieri wrote:
>
>
>
> On Wednesday, April 24, 2013 8:53:56 AM UTC-7, davidp wrote:
>>
>> I just installed Sage 5.8 and am running it from the command line. For
>> some reason, it is filling up my direct
John, Thanks. I just tried downloading the patch and applying it. I have
Sage 5.8. However, when I did
patch constructor.py trac_3416_fixes.patch
all of the patches were rejected :-(.
Victor
On Wednesday, April 24, 2013 8:47:39 AM UTC-4, John Cremona wrote:
>
> Victor,
>
> The code at trac #
The workaround is: use sage's attach() function instead of the python one.
On 04/25/2013 05:53 AM, davidp wrote:
Yes! This looks right.
Thanks,
Dave
On Wednesday, April 24, 2013 2:30:09 PM UTC-7, John H Palmieri wrote:
On Wednesday, April 24, 2013 8:53:56 AM UTC-7, davidp wrote:
Hi,
I've never heard of this "who" function, but evidently it is in Ipython so
the sage command line automatically has it. Having never heard of "who", I
had implemented something similar for Sage back in 2004 (!) called
"show_identifiers()", which is like the same function in Magma (which is
cal
24 matches
Mail list logo
