Hi Pablo,
At the moment the PPA is 64bit only. I might do 32bit in a few months.
There is a binary for 13.04 here:
http://boxen.math.washington.edu/home/sagemath/sage-mirror/linux/32bit/sage-5.10-linux-32bit-ubuntu_13.04-i686-Linux.tar.lzma
Regards,
Jan
-- Forwarded message --
F
Yes that line looks suspicious...
On Monday, July 15, 2013 7:40:36 PM UTC-4, Ursula wrote:
>
> # Direct conversion "a/b" to F does not work in Sage-4.6.alpha3,
> # so we go through SR, even though it is quite slow.
> coefficients = (F(SR(coef)) for coef in coefficients)
>
--
You received this me
On Monday, July 15, 2013 3:09:29 PM UTC-7, Volker Braun wrote:
>
> That is correct. The change_ring() methods in Sage return a new object and
> do _not_ modify the original object:
Fair enough. I think we have found a true coercion problem involving
finite fields & toric varieties, though. Th
That is correct. The change_ring() methods in Sage return a new object and
do _not_ modify the original object:
sage: x = toric_varieties.P2()
sage: x.base_ring()
Rational Field
sage: x.change_ring(GF(3)).base_ring()
Finite Field of size 3
sage: x.base_ring()
Rational Field
Similar:
sage: R = P
When you change the ring for a toric variety, that ring change does not
propagate to the affine patches on the toric variety.
Here's an example:
o = lattice_polytope.octahedron(3)
cube = o.polar()
VRes = CPRFanoToricVariety(Delta_polar=cube, coordinate_points="all")
q =5^2
field = GF(q, 'a')
VRe
2013/7/15 Peter Bruin :
> Hi Marco and all,
>
>> I had Darij's problem as well, and many others probably did as well.
>> In a right action, I would prefer p(1) to give a warning. In a right
>> action, I would want some notation where p is on the right, preferably
>> 1^p (1 hat p).
>
>
> That would
On Mon, Jul 15, 2013 at 10:34 AM, Peter Bruin wrote:
> Hi Marco and all,
>
>> I had Darij's problem as well, and many others probably did as well.
>> In a right action, I would prefer p(1) to give a warning. In a right
>> action, I would want some notation where p is on the right, preferably
>> 1^
Hi Marco and all,
I had Darij's problem as well, and many others probably did as well.
> In a right action, I would prefer p(1) to give a warning. In a right
> action, I would want some notation where p is on the right, preferably
> 1^p (1 hat p).
>
That would make sense (except that I don't
Dear all,
I was wondering about a way to get a custom derivative output,
that is more readable for an end-user. For example, in pynac.pyx,
py_print_fderivative() returns the operator as
ostr = ''.join(['D[', ', '.join([repr(int(x)) for x in params]), ']'])
whereas it would be nice to hav
Ideally there would not be a user-visible way to find out how Sage is being
run. Otherwise we'll just end up with code that only works with the
interface that the developer prefers (like the OSI disaster in ACPI
tables).
The differences should be abstracted away by the Sage api, so to show
gr
Hello,
what sequence of instructions could tell what Sage 5.10 "user-interface" is
currently being used ?
Possible answers are:
- cloud.sagemath.org
- Sage Notebook
- "linux" command line
- "windows" command line (?)
- "cygwin" command line (?)
- new others...
Long ago I used to check if
> What happened to the graph editor that was written by Rado? I forget how it
> was supposed to be called.
I actually remembered its existence yesterday, hence after sending my
message. Here it is :
sage: graph_editor?
The problem with this is that one needs to run the notebook to give it
a try.
On Mon, Jul 15, 2013 at 1:29 AM, R. Andrew Ohana wrote:
> I've created a daemon on the trac server that will do one direction of the
> sync, but it shouldn't be too hard to make it a two way sync.
one way is good enough, i just didn't hear back when I asked about
this earlier. thank's for upgrad
On 07/14/2013 12:17 AM, Nathann Cohen wrote:
Hello everybody !!!
Have you ever seen this thing ?
https://github.com/mbostock/d3/wiki/Gallery
It's a javascript library which seems to handle quite a range of things,
and I am thinking of writing a patch that would let us draw Sage
2013/7/13 Volker Braun :
> But the question is, how is this right action that you speak of implemented
> in Sage?
+1 to this comment of Volker. And the notation should be "^" (hat)
I had Darij's problem as well, and many others probably did as well.
In a right action, I would prefer p(1) to give
I would argue that P.root_field() should return a p-adic field here, not a
polynomial quotient ring. This would be consistent with the behaviour of
root_field for polynomials over QQ and number fields; generally, when we
have a choice of several different Sage representations of the same
mathem
16 matches
Mail list logo
