sage_tutorial
sage_tutorial
Release 10.6
1 Introduction 3
1.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Ways to Use Sage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3 Longterm Goals for Sage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 A Guided Tour 7
2.1 Assignment, Equality, and Arithmetic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Functions, Indentation, and Counting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.4 Basic Algebra and Calculus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.5 Plotting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.6 Some Common Issues with Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.7 Basic Rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.8 Linear Algebra . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.9 Polynomials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.10 Parents, Conversion and Coercion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.11 Finite Groups, Abelian Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.12 Number Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
2.13 Some More Advanced Mathematics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4 Interfaces 109
4.1 GP/PARI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4.2 GAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
4.3 Singular . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
4.4 Maxima . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
i
5.2 Customizing LaTeX Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.3 Customizing LaTeX Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
5.4 SageTeX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
6 Programming 125
6.1 Loading and Attaching Sage files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
6.2 Creating Compiled Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
6.3 Standalone Python/Sage Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
6.4 Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
6.5 Lists, Tuples, and Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
6.6 Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
6.7 Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
6.8 Iterators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
6.9 Loops, Functions, Control Statements, and Comparisons . . . . . . . . . . . . . . . . . . . . . . . . . 137
6.10 Profiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
8 Afterword 149
8.1 Why Python? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
8.2 I would like to contribute somehow. How can I? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
8.3 How do I reference Sage? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
9 Appendix 153
9.1 Arithmetical binary operator precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
10 Bibliography 155
Bibliography 159
Index 161
ii
Tutorial, Release 10.6
Sage is free, open-source math software that supports research and teaching in algebra, geometry, number theory, cryptog-
raphy, numerical computation, and related areas. Both the Sage development model and the technology in Sage itself are
distinguished by an extremely strong emphasis on openness, community, cooperation, and collaboration: we are building
the car, not reinventing the wheel. The overall goal of Sage is to create a viable, free, open-source alternative to Maple,
Mathematica, Magma, and MATLAB.
This tutorial is the best way to become familiar with Sage in only a few hours. You can read it in HTML or PDF versions,
or from the Sage notebook (click Help, then click Tutorial to interactively work through the tutorial from within Sage).
This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License.
CONTENTS 1
Tutorial, Release 10.6
2 CONTENTS
CHAPTER
ONE
INTRODUCTION
This tutorial should take at most 3-4 hours to fully work through. You can read it in HTML or PDF versions, or from the
Sage notebook click Help, then click Tutorial to interactively work through the tutorial from within Sage.
Though much of Sage is implemented using Python, no Python background is needed to read this tutorial. You will want
to learn Python (a very fun language!) at some point, and there are many excellent free resources for doing so: the Python
Beginner’s Guide [PyB] lists many options. If you just want to quickly try out Sage, this tutorial is the place to start. For
example:
sage: 2 + 2
4
sage: factor(-2007)
-1 * 3^2 * 223
sage: factor(A.charpoly())
x^2 * (x^2 - 30*x - 80)
sage: E = EllipticCurve([1,2,3,4,5]);
sage: E
Elliptic Curve defined by y^2 + x*y + 3*y = x^3 + 2*x^2 + 4*x + 5
over Rational Field
sage: E.anlist(10)
[0, 1, 1, 0, -1, -3, 0, -1, -3, -3, -3]
sage: E.rank()
1
3
Tutorial, Release 10.6
>>> factor(A.charpoly())
x^2 * (x^2 - 30*x - 80)
>>> E = EllipticCurve([Integer(1),Integer(2),Integer(3),Integer(4),Integer(5)]);
>>> E
Elliptic Curve defined by y^2 + x*y + 3*y = x^3 + 2*x^2 + 4*x + 5
over Rational Field
>>> E.anlist(Integer(10))
[0, 1, 1, 0, -1, -3, 0, -1, -3, -3, -3]
>>> E.rank()
1
1.1 Installation
If you do not have Sage installed on a computer and just want to try some commands, use it online at http://sagecell.
sagemath.org.
See the Sage Installation Guide in the documentation section of the main Sage webpage [SA] for instructions on installing
Sage on your computer. Here we merely make a few comments.
4 Chapter 1. Introduction
Tutorial, Release 10.6
1. The Sage download file comes with “batteries included”. In other words, although Sage uses Python, IPython,
PARI, GAP, Singular, Maxima, NTL, GMP, and so on, you do not need to install them separately as they are
included with the Sage distribution. However, to use certain Sage features, e.g., Macaulay or KASH, you must
have the relevant programs installed on your computer already.
2. The pre-compiled binary version of Sage (found on the Sage web site) may be easier and quicker to install than the
source code version. Just unpack the file and run sage.
3. If you’d like to use the SageTeX package (which allows you to embed the results of Sage computations into a LaTeX
file), you will need to make SageTeX known to your TeX distribution. To do this, see the section “Make SageTeX
known to TeX” in the Sage installation guide (this link should take you to a local copy of the installation guide).
It’s quite easy; you just need to set an environment variable or copy a single file to a directory that TeX will search.
The documentation for using SageTeX is located in $SAGE_ROOT/venv/share/texmf/tex/latex/
sagetex/, where “$SAGE_ROOT” refers to the directory where you installed Sage – for example, /opt/sage-9.
6.
• User friendly: It should be easy to understand what functionality is provided for a given object and to view docu-
mentation and source code. Also attain a high level of user support.
6 Chapter 1. Introduction
CHAPTER
TWO
A GUIDED TOUR
This section is a guided tour of some of what is available in Sage. For many more examples, see “Sage Constructions”,
which is intended to answer the general question “How do I construct …?”. See also the “Sage Reference Manual”, which
has thousands more examples. Also note that you can interactively work through this tour in the Sage notebook by clicking
the Help link.
(If you are viewing the tutorial in the Sage notebook, press shift-enter to evaluate any input cell. You can even edit the
input before pressing shift-enter. On some Macs you might have to press shift-return rather than shift-enter.)
sage: a = 5
sage: a
5
sage: 2 == 2
True
sage: 2 == 3
False
sage: 2 < 3
True
sage: a == 5
True
7
Tutorial, Release 10.6
2
>>> Integer(4) * (Integer(10) // Integer(4)) + Integer(10) % Integer(4) == Integer(10)
True
>>> Integer(3)**Integer(2)*Integer(4) + Integer(2)%Integer(5)
38
The computation of an expression like 3^2*4 + 2%5 depends on the order in which the operations are applied; this is
specified in the “operator precedence table” in Arithmetical binary operator precedence.
Sage also provides many familiar mathematical functions; here are just a few examples:
sage: sqrt(3.4)
1.84390889145858
sage: sin(5.135)
-0.912021158525540
sage: sin(pi/3)
1/2*sqrt(3)
As the last example shows, some mathematical expressions return ‘exact’ values, rather than numerical approximations.
To get a numerical approximation, use either the function N or the method n (and both of these have a longer name,
numerical_approx, and the function N is the same as n)). These take optional arguments prec, which is the requested
number of bits of precision, and digits, which is the requested number of decimal digits of precision; the default is 53
bits of precision.
sage: exp(2)
e^2
sage: n(exp(2))
7.38905609893065
sage: sqrt(pi).numerical_approx()
1.77245385090552
sage: sin(10).n(digits=5)
-0.54402
sage: N(sin(10),digits=10)
-0.5440211109
sage: numerical_approx(pi, prec=200)
3.1415926535897932384626433832795028841971693993751058209749
Python is dynamically typed, so the value referred to by each variable has a type associated with it, but a given variable
may hold values of any Python type within a given scope:
sage: a = 5 # a is an integer
sage: type(a)
<class sage.rings.integer.Integer >
sage: a = 5/3 # now a is a rational number
sage: type(a)
<class sage.rings.rational.Rational >
sage: a = hello # now a is a string
sage: type(a)
<... str >
The C programming language, which is statically typed, is much different; a variable declared to hold an int can only hold
an int in its scope.
sage: tan?
Type: <class sage.calculus.calculus.Function_tan >
Definition: tan( [noargspec] )
Docstring:
EXAMPLES:
sage: tan(pi)
0
sage: tan(3.1415)
-0.0000926535900581913
sage: tan(3.1415/4)
0.999953674278156
sage: tan(pi/4)
1
sage: tan(1/2)
tan(1/2)
sage: RR(tan(1/2))
0.546302489843790
sage: log2?
Type: <class sage.functions.constants.Log2 >
Definition: log2( [noargspec] )
Docstring:
EXAMPLES:
sage: log2
log2
sage: float(log2)
0.69314718055994529
sage: RR(log2)
0.693147180559945
sage: R = RealField(200); R
Real Field with 200 bits of precision
sage: R(log2)
0.69314718055994530941723212145817656807550013436025525412068
sage: l = (1-log2)/(1+log2); l
(1 - log(2))/(log(2) + 1)
sage: R(l)
(continues on next page)
EXAMPLE:
sage: A = matrix(ZZ,9,[5,0,0, 0,8,0, 0,4,9, 0,0,0, 5,0,0,
0,3,0, 0,6,7, 3,0,0, 0,0,1, 1,5,0, 0,0,0, 0,0,0, 0,0,0, 2,0,8, 0,0,0,
0,0,0, 0,0,0, 0,1,8, 7,0,0, 0,0,4, 1,5,0, 0,3,0, 0,0,2,
0,0,0, 4,9,0, 0,5,0, 0,0,3])
sage: A
[5 0 0 0 8 0 0 4 9]
[0 0 0 5 0 0 0 3 0]
[0 6 7 3 0 0 0 0 1]
[1 5 0 0 0 0 0 0 0]
[0 0 0 2 0 8 0 0 0]
[0 0 0 0 0 0 0 1 8]
[7 0 0 0 0 4 1 5 0]
[0 3 0 0 0 2 0 0 0]
[4 9 0 0 5 0 0 0 3]
sage: sudoku(A)
[5 1 3 6 8 7 2 4 9]
[8 4 9 5 2 1 6 3 7]
[2 6 7 3 4 9 5 8 1]
[1 5 8 4 6 3 9 7 2]
[9 7 4 2 1 8 3 6 5]
[3 2 6 7 9 5 4 1 8]
[7 8 2 9 3 4 1 5 6]
[6 3 5 1 7 2 8 9 4]
[4 9 1 8 5 6 7 2 3]
EXAMPLES:
>>> tan(pi)
(continues on next page)
EXAMPLES:
>>> log2
log2
>>> float(log2)
0.69314718055994529
>>> RR(log2)
0.693147180559945
>>> R = RealField(Integer(200)); R
Real Field with 200 bits of precision
>>> R(log2)
0.69314718055994530941723212145817656807550013436025525412068
>>> l = (Integer(1)-log2)/(Integer(1)+log2); l
(1 - log(2))/(log(2) + 1)
>>> R(l)
0.18123221829928249948761381864650311423330609774776013488056
>>> maxima(log2)
log(2)
>>> maxima(log2).float()
.6931471805599453
>>> gp(log2)
0.6931471805599453094172321215 # 32-bit
0.69314718055994530941723212145817656807 # 64-bit
>>> sudoku?
File: sage/local/lib/python2.5/site-packages/sage/games/sudoku.py
Type: <... function >
Definition: sudoku(A)
Docstring:
EXAMPLE:
>>> A = matrix(ZZ,Integer(9),[Integer(5),Integer(0),Integer(0), Integer(0),Integer(8),
˓→Integer(0), Integer(0),Integer(4),Integer(9), Integer(0),Integer(0),Integer(0),␣
˓→Integer(5),Integer(0),Integer(0),
Sage also provides ‘Tab completion’: type the first few letters of a function and then hit the Tab key. For example, if you
type ta followed by Tab, Sage will print tachyon, tan, tanh, taylor. This provides a good way to find the names
of functions and other structures in Sage.
Note: Depending on which version of the tutorial you are viewing, you may see three dots ....: on the second line of
this example. Do not type them; they are just to emphasize that the code is indented. Whenever this is the case, press
[Return/Enter] once at the end of the block to insert a blank line and conclude the function definition.
You do not specify the types of any of the input arguments. You can specify multiple inputs, each of which may have an
optional default value. For example, the function below defaults to divisor=2 if divisor is not specified.
You can also explicitly specify one or either of the inputs when calling the function; if you specify the inputs explicitly,
you can give them in any order:
In Python, blocks of code are not indicated by curly braces or begin and end blocks as in many other languages. Instead,
blocks of code are indicated by indentation, which must match up exactly. For example, the following is a syntax error
because the return statement is not indented the same amount as the other lines above it.
Semicolons are not needed at the ends of lines; a line is in most cases ended by a newline. However, you can put multiple
statements on one line, separated by semicolons:
sage: a = 5; b = a + 3; c = b^2; c
64
If you would like a single line of code to span multiple lines, use a terminating backslash:
sage: 2 + \
....: 3
5
In Sage, you count by iterating over a range of integers. For example, the first line below is exactly like for(i=0; i<3;
i++) in C++ or Java:
The third argument controls the step, so the following is like for(i=1;i<6;i+=2).
Often you will want to create a nice table to display numbers you have computed using Sage. One easy way to do this is
to use string formatting. Below, we create three columns each of width exactly 6 and make a table of squares and cubes.
The most basic data structure in Sage is the list, which is – as the name suggests – just a list of arbitrary objects. For
example, using range, the following command creates a list:
sage: list(range(2,10))
[2, 3, 4, 5, 6, 7, 8, 9]
sage: v[0]
1
sage: v[3]
sin(x^3)
Use len(v) to get the length of v, use v.append(obj) to append a new object to the end of v, and use del v[i] to
delete the 𝑖𝑡ℎ entry of v:
sage: len(v)
4
sage: v.append(1.5)
sage: v
[1, hello , 2/3, sin(x^3), 1.50000000000000]
sage: del v[1]
(continues on next page)
Another important data structure is the dictionary (or associative array). This works like a list, except that it can be
indexed with almost any object (the indices must be immutable):
You can also define new data types using classes. Encapsulating mathematical objects with classes is a powerful technique
that can help to simplify and organize your Sage programs. Below, we define a class that represents the list of even positive
integers up to n; it derives from the builtin type list.
The __init__ method is called to initialize the object when it is created; the __repr__ method prints the object out.
We call the list constructor method in the second line of the __init__ method. We create an object of class Evens as
follows:
sage: e = Evens(10)
sage: e
Even positive numbers up to n.
Note that e prints using the __repr__ method that we defined. To see the underlying list of numbers, use the list
function:
sage: list(e)
[2, 4, 6, 8, 10]
sage: e.n
10
sage: e[2]
6
sage: u = var( u )
sage: diff(sin(u), u)
cos(u)
If you get a NameError, check to see if you misspelled something, or forgot to define a variable with var(...).
sage: x = var( x )
sage: solve(x^2 + 3*x + 2, x)
[x == -2, x == -1]
sage: x, b, c = var( x b c )
sage: solve([x^2 + b*x + c == 0],x)
[x == -1/2*b - 1/2*sqrt(b^2 - 4*c), x == -1/2*b + 1/2*sqrt(b^2 - 4*c)]
sage: x, y = var( x, y )
sage: solve([x+y==6, x-y==4], x, y)
[[x == 5, y == 1]]
The following example of using Sage to solve a system of non-linear equations was provided by Jason Grout: first, we
solve the system symbolically:
sage: var( x y p q )
(x, y, p, q)
sage: eq1 = p+q==9
sage: eq2 = q*y+p*x==-6
sage: eq3 = q*y^2+p*x^2==24
sage: solve([eq1,eq2,eq3,p==1],p,q,x,y)
[[p == 1, q == 8, x == -4/3*sqrt(10) - 2/3, y == 1/6*sqrt(10) - 2/3], [p == 1, q == 8,
˓→ x == 4/3*sqrt(10) - 2/3, y == -1/6*sqrt(10) - 2/3]]
(The function n prints a numerical approximation, and the argument is the number of bits of precision.)
On the other hand, we can use find_root to find a solution to the above equation in the range 0 < 𝜑 < 𝜋/2:
sage: u = var( u )
sage: diff(sin(u), u)
cos(u)
sage: diff(sin(x^2), x, 4)
16*x^4*sin(x^2) - 48*x^2*cos(x^2) - 12*sin(x^2)
sage: integral(x*sin(x^2), x)
-1/2*cos(x^2)
sage: integral(x/(x^2+1), x, 0, 1)
1/2*log(2)
sage: f = 1/((1+x)*(x-1))
sage: f.partial_fraction(x)
-1/2/(x + 1) + 1/2/(x - 1)
This uses Sage’s interface to Maxima [Max], and so its output may be a bit different from other Sage output. In this case,
this says that the general solution to the differential equation is 𝑥(𝑡) = 𝑒−𝑡 (𝑒𝑡 + 𝑐).
You can compute Laplace transforms also; the Laplace transform of 𝑡2 𝑒𝑡 − sin(𝑡) is computed as follows:
sage: s = var("s")
sage: t = var("t")
sage: f = t^2*exp(t) - sin(t)
sage: f.laplace(t,s)
-1/(s^2 + 1) + 2/(s - 1)^3
Here is a more involved example. The displacement from equilibrium (respectively) for a coupled spring attached to a
wall on the left
|------\/\/\/\/\---|mass1|----\/\/\/\/\/----|mass2|
spring1 spring2
where 𝑚𝑖 is the mass of object i, 𝑥𝑖 is the displacement from equilibrium of mass i, and 𝑘𝑖 is the spring constant for
spring i.
Example: Use Sage to solve the above problem with 𝑚1 = 2, 𝑚2 = 1, 𝑘1 = 4, 𝑘2 = 2, 𝑥1 (0) = 3, 𝑥′1 (0) = 0,
𝑥2 (0) = 3, 𝑥′2 (0) = 0.
Solution: Take the Laplace transform of the first equation (with the notation 𝑥 = 𝑥1 , 𝑦 = 𝑥2 ):
(where the Laplace transform of a lower case function like 𝑥(𝑡) is the upper case function 𝑋(𝑠)). Take the Laplace
transform of the second equation:
This says
Plug in the initial conditions for 𝑥(0), 𝑥′ (0), 𝑦(0), and 𝑦 ′ (0), and solve the resulting two equations:
sage: var( s X Y )
(s, X, Y)
sage: eqns = [(2*s^2+6)*X-2*Y == 6*s, -2*X +(s^2+2)*Y == 3*s]
sage: solve(eqns, X,Y)
[[X == 3*(s^3 + 3*s)/(s^4 + 5*s^2 + 4),
Y == 3*(s^3 + 5*s)/(s^4 + 5*s^2 + 4)]]
sage: var( s t )
(s, t)
sage: inverse_laplace((3*s^3 + 9*s)/(s^4 + 5*s^2 + 4),s,t)
cos(2*t) + 2*cos(t)
sage: inverse_laplace((3*s^3 + 15*s)/(s^4 + 5*s^2 + 4),s,t)
-cos(2*t) + 4*cos(t)
cos(2*t) + 2*cos(t)
>>> inverse_laplace((Integer(3)*s**Integer(3) + Integer(15)*s)/(s**Integer(4) +␣
˓→Integer(5)*s**Integer(2) + Integer(4)),s,t)
-cos(2*t) + 4*cos(t)
sage: t = var( t )
sage: P = parametric_plot((cos(2*t) + 2*cos(t), 4*cos(t) - cos(2*t) ),
....: (t, 0, 2*pi), rgbcolor=hue(0.9))
sage: show(P)
sage: t = var( t )
sage: p1 = plot(cos(2*t) + 2*cos(t), (t,0, 2*pi), rgbcolor=hue(0.3))
sage: p2 = plot(4*cos(t) - cos(2*t), (t,0, 2*pi), rgbcolor=hue(0.6))
sage: show(p1 + p2)
For more on plotting, see Plotting. See section 5.5 of [NagleEtAl2004] for further information on differential equations.
If we call ℎ·𝑓 (𝑥, 𝑦(𝑥)) the “correction term” (for lack of anything better), call 𝑦(𝑥) the “old value of 𝑦”, and call 𝑦(𝑥+ℎ)
the “new value of 𝑦”, then this approximation can be re-expressed as
𝑥 𝑦 ℎ · 𝑓 (𝑥, 𝑦)
𝑎 𝑐 ℎ · 𝑓 (𝑎, 𝑐)
𝑎+ℎ 𝑐 + ℎ · 𝑓 (𝑎, 𝑐) …
𝑎 + 2ℎ …
…
𝑏 = 𝑎 + 𝑛ℎ ??? …
The goal is to fill out all the blanks of the table, one row at a time, until we reach the ??? entry, which is the Euler’s
method approximation for 𝑦(𝑏).
The idea for systems of ODEs is similar.
Example: Numerically approximate 𝑧(𝑡) at 𝑡 = 1 using 4 steps of Euler’s method, where 𝑧 ′′ + 𝑡𝑧 ′ + 𝑧 = 0, 𝑧(0) = 1,
𝑧 ′ (0) = 0.
We must reduce the 2nd order ODE down to a system of two first order DEs (using 𝑥 = 𝑧, 𝑦 = 𝑧 ′ ) and apply Euler’s
method:
t x h*f(t,x,y) y h*g(t,x,y)
0 1 0.00 0 -0.25
1/4 1.0 -0.062 -0.25 -0.23
1/2 0.94 -0.12 -0.48 -0.17
3/4 0.82 -0.16 -0.66 -0.081
1 0.65 -0.18 -0.74 0.022
At this point, P is storing two plots: P[0], the plot of 𝑥 vs. 𝑡, and P[1], the plot of 𝑦 vs. 𝑡. We can plot both of these as
follows:
sage: x = polygen(QQ, x )
sage: chebyshev_U(2,x)
4*x^2 - 1
sage: bessel_I(1,1).n(250)
0.56515910399248502720769602760986330732889962162109200948029448947925564096
sage: bessel_I(1,1).n()
0.565159103992485
sage: bessel_I(2,1.1).n()
0.167089499251049
At this point, Sage has only wrapped these functions for numerical use. For symbolic use, please use the Maxima interface
directly, as in the following example:
2.5 Plotting
Sage can produce two-dimensional and three-dimensional plots.
You can also create a circle by assigning it to a variable; this does not plot it:
sage: c.show()
Alternatively, evaluating c.save( filename.png ) will save the plot to the given file.
Now, these ‘circles’ look more like ellipses because the axes are scaled differently. You can fix this:
sage: c.show(aspect_ratio=1)
The command show(c, aspect_ratio=1) accomplishes the same thing, or you can save the picture using c.
save( filename.png , aspect_ratio=1).
It’s easy to plot basic functions:
2.5. Plotting 29
Tutorial, Release 10.6
Once you specify a variable name, you can create parametric plots also:
sage: x = var( x )
sage: parametric_plot((cos(x),sin(x)^3),(x,0,2*pi),rgbcolor=hue(0.6))
Graphics object consisting of 1 graphics primitive
It’s important to notice that the axes of the plots will only intersect if the origin is in the viewing range of the graph, and
that with sufficiently large values scientific notation may be used:
sage: plot(x^2,(x,300,500))
Graphics object consisting of 1 graphics primitive
sage: x = var( x )
sage: p1 = parametric_plot((cos(x),sin(x)),(x,0,2*pi),rgbcolor=hue(0.2))
sage: p2 = parametric_plot((cos(x),sin(x)^2),(x,0,2*pi),rgbcolor=hue(0.4))
sage: p3 = parametric_plot((cos(x),sin(x)^3),(x,0,2*pi),rgbcolor=hue(0.6))
sage: show(p1+p2+p3, axes=false)
>>> p2 = parametric_plot((cos(x),sin(x)**Integer(2)),(x,Integer(0),Integer(2)*pi),
˓→rgbcolor=hue(RealNumber( 0.4 )))
>>> p3 = parametric_plot((cos(x),sin(x)**Integer(3)),(x,Integer(0),Integer(2)*pi),
˓→rgbcolor=hue(RealNumber( 0.6 )))
A good way to produce filled-in shapes is to produce a list of points (L in the example below) and then use the polygon
command to plot the shape with boundary formed by those points. For example, here is a green deltoid:
sage: L = [[-1+cos(pi*i/100)*(1+cos(pi*i/100)),
....: 2*sin(pi*i/100)*(1-cos(pi*i/100))] for i in range(200)]
sage: p = polygon(L, rgbcolor=(1/8,3/4,1/2))
sage: p
Graphics object consisting of 1 graphics primitive
>>> p
Graphics object consisting of 1 graphics primitive
sage: L = [[6*cos(pi*i/100)+5*cos((6/2)*pi*i/100),
....: 6*sin(pi*i/100)-5*sin((6/2)*pi*i/100)] for i in range(200)]
sage: p = polygon(L, rgbcolor=(1/8,1/4,1/2))
sage: t = text("hypotrochoid", (5,4), rgbcolor=(1,0,0))
sage: show(p+t)
... Integer(6)*sin(pi*i/Integer(100))-Integer(5)*sin((Integer(6)/Integer(2))*pi*i/
˓→Integer(100))] for i in range(Integer(200))]
>>> show(p+t)
Calculus teachers draw the following plot frequently on the board: not just one branch of arcsin but rather several of them:
i.e., the plot of 𝑦 = sin(𝑥) for 𝑥 between −2𝜋 and 2𝜋, flipped about the 45 degree line. The following Sage commands
construct this:
>>> line(v)
Graphics object consisting of 1 graphics primitive
Since the tangent function has a larger range than sine, if you use the same trick to plot the inverse tangent, you should
change the minimum and maximum coordinates for the x-axis:
Sage also computes polar plots, contour plots and vector field plots (for special types of functions). Here is an example
of a contour plot:
2.5. Plotting 31
Tutorial, Release 10.6
Graphics3d Object
Alternatively, you can use parametric_plot3d to graph a parametric surface where each of 𝑥, 𝑦, 𝑧 is determined by
a function of one or two variables (the parameters, typically 𝑢 and 𝑣). The previous plot can be expressed parametrically
as follows:
sage: u, v = var( u, v )
sage: f_x(u, v) = u
sage: f_y(u, v) = v
sage: f_z(u, v) = u^2 + v^2
sage: parametric_plot3d([f_x, f_y, f_z], (u, -2, 2), (v, -2, 2))
Graphics3d Object
Graphics3d Object
The third way to plot a 3D surface in Sage is implicit_plot3d, which graphs a contour of a function like 𝑓 (𝑥, 𝑦, 𝑧) = 0
(this defines a set of points). We graph a sphere using the classical formula:
sage: x, y, z = var( x, y, z )
sage: implicit_plot3d(x^2 + y^2 + z^2 - 4, (x,-2, 2), (y,-2, 2), (z,-2, 2))
Graphics3d Object
Graphics3d Object
Cross cap:
Twisted torus:
2.5. Plotting 33
Tutorial, Release 10.6
Lemniscate:
>>> implicit_plot3d(f, (x, -RealNumber( 0.5 ), RealNumber( 0.5 )), (y, -Integer(1),␣
˓→Integer(1)), (z, -Integer(1), Integer(1)))
Graphics3d Object
In the last line, note the syntax. Using plot(f(z), 0, 2) instead will give a NameError, because z is a dummy
variable in the definition of f and is not defined outside of that definition. In order to be able to use f(z) in the plot
command, z (or whatever is desired) needs to be defined as a variable. We can use the syntax below, or in the next item
in our list.
At this point, f(z) is a symbolic expression, the next item in our list.
2. Define a “callable symbolic expression”. These can be plotted, differentiated, and integrated.
Note that while g is a callable symbolic expression, g(x) is a related, but different sort of object, which can also be
plotted, differentated, etc., albeit with some issues: see item 5 below for an illustration.
sage: g(x)
x^2
sage: type(g(x))
<class sage.symbolic.expression.Expression >
sage: g(x).derivative()
2*x
sage: plot(g(x), 0, 2)
Graphics object consisting of 1 graphics primitive
3. Use a pre-defined Sage ‘calculus function’. These can be plotted, and with a little help, differentiated, and integrated.
sage: type(sin)
<class sage.functions.trig.Function_sin >
sage: plot(sin, 0, 2)
Graphics object consisting of 1 graphics primitive
sage: type(sin(x))
<class sage.symbolic.expression.Expression >
sage: plot(sin(x), 0, 2)
Graphics object consisting of 1 graphics primitive
sage: f = sin
sage: f.derivative()
Traceback (most recent call last):
...
AttributeError: ...
Using f = sin(x) instead of sin works, but it is probably even better to use f(x) = sin(x) to define a callable
symbolic expression.
The issue: plot(h(x), 0, 4) plots the line 𝑦 = 𝑥 − 2, not the multi-line function defined by h. The reason? In the
command plot(h(x), 0, 4), first h(x) is evaluated: this means plugging the symbolic variable x into the function
h. So, the inequality x < 2 evaluates to False first, and hence h(x) evaluates to x - 2. This can be seen with
Note that here there are two different x: the Python variable used to define the function h (which is local to its definition)
and the symbolic variable x which is available on startup in Sage.
The solution: don’t use plot(h(x), 0, 4); instead, use
sage: plot(h, 0, 4)
Graphics object consisting of 1 graphics primitive
sage: f = x
sage: g = f.derivative()
sage: g
1
The problem: g(3), for example, returns an error, saying “ValueError: the number of arguments must be less than or
equal to 0.”
sage: type(f)
<class sage.symbolic.expression.Expression >
sage: type(g)
<class sage.symbolic.expression.Expression >
g is not a function, it’s a constant, so it has no variables associated to it, and you can’t plug anything into it.
The solution: there are several options.
• Define f initially to be a symbolic expression.
>>> g = f.derivative()
>>> g
x |--> 1
>>> g(Integer(3))
1
>>> type(g)
<class sage.symbolic.expression.Expression >
• Or with f and g as defined originally, specify the variable for which you are substituting.
sage: f = x
sage: g = f.derivative()
sage: g
1
sage: g(x=3) # instead of g(3)
1
Finally, here’s one more way to tell the difference between the derivatives of f = x and f(x) = x
sage: f(x) = x
sage: g = f.derivative()
sage: g.variables() # the variables present in g
()
sage: g.arguments() # the arguments which can be plugged into g
(x,)
sage: f = x
sage: h = f.derivative()
sage: h.variables()
()
sage: h.arguments()
()
As this example has been trying to illustrate, h accepts no arguments, and this is why h(3) returns an error.
The sets are named “ratpoly” and “realpoly”, but these aren’t important here; however, note that the strings “.<t>” and
“.<z>” name the variables used in the two cases.
sage: factor(t^2-2)
t^2 - 2
sage: factor(z^2-2)
(z - 1.41421356237310) * (z + 1.41421356237310)
Similar comments apply to matrices: the row-reduced form of a matrix can depend on the ring over which it is defined,
as can its eigenvalues and eigenvectors. For more about constructing polynomials, see Polynomials, and for more about
matrices, see Linear Algebra.
The symbol I represents the square root of −1; i is a synonym for I. Of course, this is not a rational number:
Note: The above code may not work as expected if the variable i has been assigned a different value, for example, if it
was used as a loop variable. If this is the case, type
sage: reset( i )
0.766666666666667
>>> RealNumber( 0.1 ) + Integer(2)/Integer(3) # coercion rules are symmetric in␣
˓→Sage
0.766666666666667
Here are more examples of basic rings in Sage. As noted above, the ring of rational numbers may be referred to using
QQ, or also RationalField() (a field is a ring in which the multiplication is commutative and in which every nonzero
element has a reciprocal in that ring, so the rationals form a field, but the integers don’t):
sage: RationalField()
Rational Field
sage: QQ
Rational Field
sage: 1/2 in QQ
True
The decimal number 1.2 is considered to be in QQ: decimal numbers which happen to√ also be rational can be “coerced”
into the rational numbers (see Parents, Conversion and Coercion). The numbers 𝜋 and 2 are not rational, though:
sage: 1.2 in QQ
True
sage: pi in QQ
False
sage: pi in RR
True
sage: sqrt(2) in QQ
False
sage: sqrt(2) in CC
True
For use in higher mathematics, Sage also knows about other rings, such as finite fields, 𝑝-adic integers, the ring of algebraic
numbers, polynomial rings, and matrix rings. Here are constructions of some of these:
sage: GF(3)
Finite Field of size 3
sage: GF(27, a ) # need to name the generator if not a prime field
Finite Field in a of size 3^3
sage: Zp(5)
5-adic Ring with capped relative precision 20
sage: sqrt(3) in QQbar # algebraic closure of QQ
True
sage: A = Matrix([[1,2,3],[3,2,1],[1,1,1]])
sage: w = vector([1,1,-4])
sage: w*A
(0, 0, 0)
sage: A*w
(-9, 1, -2)
sage: kernel(A)
Free module of degree 3 and rank 1 over Integer Ring
Echelon basis matrix:
[ 1 1 -4]
>>> w = vector([Integer(1),Integer(1),-Integer(4)])
>>> w*A
(0, 0, 0)
>>> A*w
(-9, 1, -2)
>>> kernel(A)
Free module of degree 3 and rank 1 over Integer Ring
Echelon basis matrix:
[ 1 1 -4]
Note that in Sage, the kernel of a matrix 𝐴 is the “left kernel”, i.e. the space of vectors 𝑤 such that 𝑤𝐴 = 0.
Solving matrix equations is easy, using the method solve_right. Evaluating A.solve_right(Y) returns a matrix
(or vector) 𝑋 so that 𝐴𝑋 = 𝑌 :
(The syntax for the output of eigenvectors_left is a list of triples: (eigenvalue, eigenvector, multiplicity).) Eigen-
values and eigenvectors over QQ or RR can also be computed using Maxima (see Maxima below).
As noted in Basic Rings, the ring over which a matrix is defined affects some of its properties. In the following, the first
argument to the matrix command tells Sage to view the matrix as a matrix of integers (the ZZ case), a matrix of rational
numbers (QQ), or a matrix of reals (RR):
sage: AZ = matrix(ZZ, [[2,0], [0,1]])
sage: AQ = matrix(QQ, [[2,0], [0,1]])
sage: AR = matrix(RR, [[2,0], [0,1]])
sage: AZ.echelon_form()
[2 0]
[0 1]
sage: AQ.echelon_form()
(continues on next page)
For computing eigenvalues and eigenvectors of matrices over floating point real or complex numbers, the matrix should
be defined over RDF (Real Double Field) or CDF (Complex Double Field), respectively. If no ring is specified and floating
point real or complex numbers are used then by default the matrix is defined over the RR or CC fields, respectively, which
do not support these computations for all the cases:
sage: M = MatrixSpace(QQ,3)
sage: M
Full MatrixSpace of 3 by 3 dense matrices over Rational Field
(To specify the space of 3 by 4 matrices, you would use MatrixSpace(QQ,3,4). If the number of columns is omitted,
it defaults to the number of rows, so MatrixSpace(QQ,3) is a synonym for MatrixSpace(QQ,3,3).) The space of
matrices is equipped with its canonical basis:
sage: B = M.basis()
sage: len(B)
9
sage: B[0,1]
[0 1 0]
[0 0 0]
[0 0 0]
sage: A = M(range(9)); A
[0 1 2]
[3 4 5]
[6 7 8]
sage: A.echelon_form()
[ 1 0 -1]
[ 0 1 2]
[ 0 0 0]
sage: A.kernel()
Vector space of degree 3 and dimension 1 over Rational Field
Basis matrix:
[ 1 -2 1]
˓→Integer(0),Integer(1),Integer(1),
˓→Integer(1),Integer(1),Integer(0)])
>>> A
[1 1 0 0 1 1 1 1]
[0 1 0 0 1 0 1 1]
[0 0 1 0 1 1 0 1]
[0 0 1 1 1 1 1 0]
>>> rows = A.rows()
>>> A.columns()
[(1, 0, 0, 0), (1, 1, 0, 0), (0, 0, 1, 1), (0, 0, 0, 1),
(1, 1, 1, 1), (1, 0, 1, 1), (1, 1, 0, 1), (1, 1, 1, 0)]
>>> rows
[(1, 1, 0, 0, 1, 1, 1, 1), (0, 1, 0, 0, 1, 0, 1, 1),
(0, 0, 1, 0, 1, 1, 0, 1), (0, 0, 1, 1, 1, 1, 1, 0)]
sage: V = VectorSpace(GF(2),8)
sage: S = V.subspace(rows)
(continues on next page)
The basis of 𝑆 used by Sage is obtained from the non-zero rows of the reduced row echelon form of the matrix of
generators of 𝑆.
The multi-modular algorithm in Sage is good for square matrices (but not so good for non-square matrices):
2.9 Polynomials
In this section we illustrate how to create and use polynomials in Sage.
sage: R = PolynomialRing(QQ, t )
sage: R
Univariate Polynomial Ring in t over Rational Field
This creates a polynomial ring and tells Sage to use (the string) ‘t’ as the indeterminate when printing to the screen.
However, this does not define the symbol t for use in Sage, so you cannot use it to enter a polynomial (such as 𝑡2 + 1)
belonging to R.
An alternate way is
sage: S = QQ[ t ]
sage: S == R
True
or
or even
This has the additional side effect that it defines the variable t to be the indeterminate of the polynomial ring, so you can
easily construct elements of R, as follows. (Note that the third way is very similar to the constructor notation in Magma,
and just as in Magma it can be used for a wide range of objects.)
Whatever method you use to define a polynomial ring, you can recover the indeterminate as the 0𝑡ℎ generator:
sage: R = PolynomialRing(QQ, t )
sage: t = R.0
sage: t in R
True
2.9. Polynomials 51
Tutorial, Release 10.6
Note that a similar construction works with the complex numbers: the complex numbers can be viewed as being generated
over the real numbers by the symbol i; thus we have the following:
sage: CC
Complex Field with 53 bits of precision
sage: CC.0 # 0th generator of CC
1.00000000000000*I
For polynomial rings, you can obtain both the ring and its generator, or just the generator, during ring creation as follows:
>>> g
7*t^16 + 7*t^15 + 7*t^14 + 7*t^13 + 77*t^12 + 91*t^11 + 91*t^10 + 84*t^9
+ 84*t^8 + 84*t^7 + 84*t^6 + 14*t^5
>>> F = factor(g); F
(7) * t^5 * (t^5 + 10*t + 2) * (t^6 + t^5 + t^4 + t^3 + t^2 + t + 1)
>>> F.unit()
7
>>> list(F)
[(t, 5), (t^5 + 10*t + 2, 1), (t^6 + t^5 + t^4 + t^3 + t^2 + t + 1, 1)]
Notice that the factorization correctly takes into account and records the unit part.
If you were to use, e.g., the R.cyclotomic_polynomial function a lot for some research project, in addition to citing
Sage you should make an attempt to find out what component of Sage is being used to actually compute the cyclotomic
polynomial and cite that as well. In this case, if you type R.cyclotomic_polynomial?? to see the source code, you’ll
quickly see a line f = pari.polcyclo(n) which means that PARI is being used for computation of the cyclotomic
polynomial. Cite PARI in your work as well.
Dividing two polynomials constructs an element of the fraction field (which Sage creates automatically).
Using Laurent series, one can compute series expansions in the fraction field of QQ[x]:
2.9. Polynomials 53
Tutorial, Release 10.6
The ring is determined by the variable. Note that making another ring with variable called x does not return a different
ring.
Sage also has support for power series and Laurent series rings over any base ring. In the following example, we create
an element of F7 [[𝑇 ]] and divide to create an element of F7 ((𝑇 )).
You can also create power series rings using a double-brackets shorthand:
sage: GF(7)[[ T ]]
Power Series Ring in T over Finite Field of size 7
Just as for defining univariate polynomial rings, there are alternative ways:
2.9. Polynomials 55
Tutorial, Release 10.6
Also, if you want the variable names to be single letters then you can use the following shorthand:
You can also use more mathematical notation to construct a polynomial ring.
Multivariate polynomials are implemented in Sage using Python dictionaries and the “distributive representation” of a
polynomial. Sage makes some use of Singular [Si], e.g., for computation of gcd’s and Gröbner basis of ideals.
Next we create the ideal (𝑓, 𝑔) generated by 𝑓 and 𝑔, by simply multiplying (f,g) by R (we could also write ideal([f,
g]) or ideal(f,g)).
Incidentally, the Gröbner basis above is not a list but an immutable sequence. This means that it has a universe, parent,
and cannot be changed (which is good because changing the basis would break other routines that use the Gröbner basis).
sage: B.universe()
Multivariate Polynomial Ring in x, y over Rational Field
sage: B[1] = x
Traceback (most recent call last):
...
ValueError: object is immutable; please change a copy instead.
Some (read: not as much as we would like) commutative algebra is available in Sage, implemented via Singular. For
example, we can compute the primary decomposition and associated primes of 𝐼:
sage: I.primary_decomposition()
[Ideal (x^2) of Multivariate Polynomial Ring in x, y over Rational Field,
Ideal (y^2, x^6) of Multivariate Polynomial Ring in x, y over Rational Field]
sage: I.associated_primes()
(continues on next page)
2.9. Polynomials 57
Tutorial, Release 10.6
2.10.1 Elements
If one wants to implement a ring in Python, a first approximation is to create a class for the elements X of that ring and
provide it with the required double underscore methods such as __add__, __sub__, __mul__, of course making sure
that the ring axioms hold.
As Python is a strongly typed (yet dynamically typed) language, one might, at least at first, expect that one implements
one Python class for each ring. After all, Python contains one type <int> for the integers, one type <float> for the
reals, and so on. But that approach must soon fail: There are infinitely many rings, and one can not implement infinitely
many classes.
Instead, one may create a hierarchy of classes designed to implement elements of ubiquitous algebraic structures, such as
groups, rings, skew fields, commutative rings, fields, algebras, and so on.
But that means that elements of fairly different rings can have the same type.
sage: P.<x,y> = GF(3)[]
sage: Q.<a,b> = GF(4, z )[]
sage: type(x)==type(a)
True
On the other hand, one could also have different Python classes providing different implementations of the same math-
ematical structure (e.g., dense matrices versus sparse matrices)
sage: P.<a> = PolynomialRing(ZZ)
sage: Q.<b> = PolynomialRing(ZZ, sparse=True)
sage: R.<c> = PolynomialRing(ZZ, implementation= NTL )
sage: type(a); type(b); type(c)
(continues on next page)
<class sage.rings.polynomial.polynomial_ring.PolynomialRing_integral_domain_with_
˓→category.element_class >
<class sage.rings.polynomial.polynomial_integer_dense_ntl.Polynomial_integer_dense_
˓→ntl >
<class sage.rings.polynomial.polynomial_ring.PolynomialRing_integral_domain_with_
˓→category.element_class >
<class sage.rings.polynomial.polynomial_integer_dense_ntl.Polynomial_integer_dense_
˓→ntl >
That poses two problems: On the one hand, if one has elements that are two instances of the same class, then one may
expect that their __add__ method will allow to add them; but one does not want that, if the elements belong to very
different rings. On the other hand, if one has elements belonging to different implementations of the same ring, then one
wants to add them, but that is not straight forward if they belong to different Python classes.
The solution to these problems is called “coercion” and will be explained below.
However, it is essential that each element knows what it is element of. That is available by the method parent():
sage: isinstance(QQ,Field)
True
sage: isinstance(QQ, Ring)
True
sage: isinstance(ZZ,Field)
(continues on next page)
In algebra, objects sharing the same kind of algebraic structures are collected in so-called “categories”. So, there is a rough
analogy between the class hierarchy in Sage and the hierarchy of categories. However, this analogy of Python classes and
categories shouldn’t be stressed too much. After all, mathematical categories are implemented in Sage as well:
sage: Rings()
Category of rings
sage: ZZ.category()
Join of Category of Dedekind domains
and Category of euclidean domains
and Category of noetherian rings
and Category of infinite enumerated sets
and Category of metric spaces
sage: ZZ.category().is_subcategory(Rings())
True
sage: ZZ in Rings()
True
sage: ZZ in Fields()
False
sage: QQ in Fields()
True
While Sage’s class hierarchy is centered at implementation details, Sage’s category framework is more centered on math-
ematical structure. It is possible to implement generic methods and tests independent of a specific implementation in the
categories.
Parent structures in Sage are supposed to be unique Python objects. For example, once a polynomial ring over a certain
base ring and with a certain list of generators is created, the result is cached:
sage: M = Matrix(ZZ,2,2); M
[0 0]
[0 0]
sage: isinstance(M, RingElement)
False
While parents are unique, equal elements of a parent in Sage are not necessarily identical. This is in contrast to the
behaviour of Python for some (albeit not all) integers:
It is important to observe that elements of different rings are in general not distinguished by their type, but by their parent:
sage: a = GF(2)(1)
sage: b = GF(5)(1)
sage: type(a) is type(b)
True
sage: parent(a)
Finite Field of size 2
sage: parent(b)
Finite Field of size 5
Hence, from an algebraic point of view, the parent of an element is more important than its type.
sage: a = GF(2)(1)
sage: b = GF(5)(1)
sage: GF(5)(a) == b
True
sage: GF(2)(b) == a
True
However, an implicit (or automatic) conversion will only happen if this can be done thoroughly and consistently. Math-
ematical rigour is essential at that point.
Such an implicit conversion is called coercion. If coercion is defined, then it must coincide with conversion. Two
conditions must be satisfied for a coercion to be defined:
1. A coercion from P1 to P2 must be given by a structure preserving map (e.g., a ring homomorphism). It does not
suffice that some elements of P1 can be mapped to P2, and the map must respect the algebraic structure of P1.
2. The choice of these coercion maps must be consistent: If P3 is a third parent structure, then the composition of the
chosen coercion from P1 to P2 with the coercion from P2 to P3 must coincide with the chosen coercion from P1
to P3. In particular, if there is a coercion from P1 to P2 and P2 to P1, the composition must be the identity map
of P1.
So, although it is possible to convert each element of GF(2) into GF(5), there is no coercion, since there is no ring
homomorphism between GF(2) and GF(5).
The second aspect - consistency - is a bit more difficult to explain. We illustrate it with multivariate polynomial rings. In
applications, it certainly makes most sense to have name preserving coercions. So, we have:
If there is no name preserving ring homomorphism, coercion is not defined. However, conversion may still be possible,
namely by mapping ring generators according to their position in the list of generators:
sage: R3 = ZZ[ z , x ]
sage: R3.has_coerce_map_from(R1)
False
sage: R3(x)
z
sage: R3(y)
x
sage: R3.coerce(y)
Traceback (most recent call last):
...
TypeError: no canonical coercion
from Multivariate Polynomial Ring in x, y over Integer Ring
to Multivariate Polynomial Ring in z, x over Integer Ring
But such position preserving conversions do not qualify as coercion: By composing a name preserving map from ZZ[ x ,
y ] to ZZ[ y , x ] with a position preserving map from ZZ[ y , x ] to ZZ[ a , b ], a map would result that
is neither name preserving nor position preserving, in violation to consistency.
If there is a coercion, it will be used to compare elements of different rings or to do arithmetic. This is often convenient,
but the user should be aware that extending the ==-relation across the borders of different parents may easily result in
overdoing it. For example, while == is supposed to be an equivalence relation on the elements of one ring, this is not
necessarily the case if different rings are involved. For example, 1 in ZZ and in a finite field are considered equal, since
there is a canonical coercion from the integers to any finite field. However, in general there is no coercion between two
different finite fields. Therefore we have
sage: GF(5)(1) == 1
True
sage: 1 == GF(2)(1)
True
sage: GF(5)(1) == GF(2)(1)
False
sage: GF(5)(1) != GF(2)(1)
True
Similarly, we have
Another consequence of the consistency condition is that coercions can only go from exact rings (e.g., the rationals QQ)
to inexact rings (e.g., real numbers with a fixed precision RR), but not the other way around. The reason is that the
composition of the coercion from QQ to RR with a conversion from RR to QQ is supposed to be the identity on QQ. But this
is impossible, since some distinct rational numbers may very well be treated equal in RR, as in the following example:
True
>>> Integer(1)/Integer(10)**Integer(200)+Integer(1)/Integer(10)**Integer(100) ==␣
˓→Integer(1)/Integer(10)**Integer(100)
False
When comparing elements of two parents P1 and P2, it is possible that there is no coercion between the two rings, but
there is a canonical choice of a parent P3 so that both P1 and P2 coerce into P3. In this case, coercion will take place as
well. A typical use case is the sum of a rational number and a polynomial with integer coefficients, yielding a polynomial
with rational coefficients:
Note that in principle the result would also make sense in the fraction field of ZZ[ x ]. However, Sage tries to choose a
canonical common parent that seems to be most natural (QQ[ x ] in our example). If several potential common parents
seem equally natural, Sage will not pick one of them at random, in order to have a reliable result. The mechanisms which
that choice is based upon is explained in the thematic tutorial.
No coercion into a common parent will take place in the following example:
The reason is that Sage would not choose one of the potential candidates QQ[ x ][ y ], QQ[ y ][ x ], QQ[ x ,
y ] or QQ[ y , x ], because all of these four pairwise different structures seem natural common parents, and there
is no apparent canonical choice.
You can also obtain the character table (in LaTeX format) in Sage:
sage: G = PermutationGroup([[(1,2),(3,4)], [(1,2,3)]])
sage: latex(G.character_table())
\left(\begin{array}{rrrr}
1 & 1 & 1 & 1 \\
1 & -\zeta_{3} - 1 & \zeta_{3} & 1 \\
1 & \zeta_{3} & -\zeta_{3} - 1 & 1 \\
3 & 0 & 0 & -1
\end{array}\right)
>>> latex(G.character_table())
\left(\begin{array}{rrrr}
1 & 1 & 1 & 1 \\
1 & -\zeta_{3} - 1 & \zeta_{3} & 1 \\
1 & \zeta_{3} & -\zeta_{3} - 1 & 1 \\
3 & 0 & 0 & -1
(continues on next page)
Sage also includes classical and matrix groups over finite fields:
sage: MS = MatrixSpace(GF(7), 2)
sage: gens = [MS([[1,0],[-1,1]]),MS([[1,1],[0,1]])]
sage: G = MatrixGroup(gens)
sage: G.conjugacy_classes_representatives()
(
[1 0] [0 6] [0 4] [6 0] [0 6] [0 4] [0 6] [0 6] [0 6] [4 0]
[0 1], [1 5], [5 5], [0 6], [1 2], [5 2], [1 0], [1 4], [1 3], [0 2],
[5 0]
[0 3]
)
sage: G = Sp(4,GF(7))
sage: G
Symplectic Group of degree 4 over Finite Field of size 7
sage: G.random_element() # random output
[5 5 5 1]
[0 2 6 3]
[5 0 1 0]
[4 6 3 4]
sage: G.order()
276595200
>>> G = MatrixGroup(gens)
>>> G.conjugacy_classes_representatives()
(
[1 0] [0 6] [0 4] [6 0] [0 6] [0 4] [0 6] [0 6] [0 6] [4 0]
[0 1], [1 5], [5 5], [0 6], [1 2], [5 2], [1 0], [1 4], [1 3], [0 2],
<BLANKLINE>
[5 0]
[0 3]
)
>>> G = Sp(Integer(4),GF(Integer(7)))
>>> G
Symplectic Group of degree 4 over Finite Field of size 7
>>> G.random_element() # random output
[5 5 5 1]
[0 2 6 3]
[5 0 1 0]
[4 6 3 4]
>>> G.order()
276595200
You can also compute using abelian groups (infinite and finite):
sage: R = IntegerModRing(97)
sage: a = R(2) / R(3)
sage: a
33
sage: a.rational_reconstruction()
2/3
sage: b = R(47)
sage: b^20052005
50
sage: b.modulus()
97
sage: b.is_square()
True
Perfect!
Sage’s sigma(n,k) function adds up the 𝑘 𝑡ℎ powers of the divisors of n:
sage: sigma(28,0); sigma(28,1); sigma(28,2)
6
(continues on next page)
6
56
1050
We next illustrate the extended Euclidean algorithm, Euler’s 𝜑-function, and the Chinese remainder theorem:
sage: n = 2005
sage: for i in range(1000):
....: n = 3*odd_part(n) + 1
(continues on next page)
sage: K = Qp(11); K
11-adic Field with capped relative precision 20
sage: a = K(211/17); a
4 + 4*11 + 11^2 + 7*11^3 + 9*11^5 + 5*11^6 + 4*11^7 + 8*11^8 + 7*11^9
+ 9*11^10 + 3*11^11 + 10*11^12 + 11^13 + 5*11^14 + 6*11^15 + 2*11^16
+ 3*11^17 + 11^18 + 7*11^19 + O(11^20)
sage: b = K(3211/11^2); b
10*11^-2 + 5*11^-1 + 4 + 2*11 + O(11^18)
Much work has been done implementing rings of integers in 𝑝-adic fields and number fields. The interested reader is
invited to read Introduction to the p-adics and ask the experts on the sage-support Google group for further details.
A number of related methods are already implemented in the NumberField class.
sage: K.galois_group()
Galois group 3T2 (S3) with order 6 of x^3 + x^2 - 2*x + 8
sage: K.polynomial_quotient_ring()
Univariate Quotient Polynomial Ring in a over Rational Field with modulus
x^3 + x^2 - 2*x + 8
sage: K.units()
(-3*a^2 - 13*a - 13,)
sage: K.discriminant()
(continues on next page)
We can also find all points of intersection of the two curves by intersecting them and computing the irreducible compo-
nents.
sage: V = C2.intersection(C3)
sage: V.irreducible_components()
[Closed subscheme of Affine Space of dimension 2 over Rational Field defined by:
y - 1,
x,
Closed subscheme of Affine Space of dimension 2 over Rational Field defined by:
y,
x - 1,
Closed subscheme of Affine Space of dimension 2 over Rational Field defined by:
x + y + 2,
2*y^2 + 4*y + 3]
Thus, e.g., (1, 0) and (0, 1) are on both curves (visibly clear), as are certain (quadratic) points whose 𝑦 coordinates satisfy
2𝑦 2 + 4𝑦 + 3 = 0.
Sage can compute the toric ideal of the twisted cubic in projective 3 space:
sage: R.<a,b,c,d> = PolynomialRing(QQ, 4)
sage: I = ideal(b^2-a*c, c^2-b*d, a*d-b*c)
sage: F = I.groebner_fan(); F
Groebner fan of the ideal:
Ideal (b^2 - a*c, c^2 - b*d, -b*c + a*d) of Multivariate Polynomial Ring
in a, b, c, d over Rational Field
sage: F.reduced_groebner_bases ()
[[-c^2 + b*d, -b*c + a*d, -b^2 + a*c],
[-b*c + a*d, -c^2 + b*d, b^2 - a*c],
[-c^3 + a*d^2, -c^2 + b*d, b*c - a*d, b^2 - a*c],
[-c^2 + b*d, b^2 - a*c, b*c - a*d, c^3 - a*d^2],
[-b*c + a*d, -b^2 + a*c, c^2 - b*d],
[-b^3 + a^2*d, -b^2 + a*c, c^2 - b*d, b*c - a*d],
[-b^2 + a*c, c^2 - b*d, b*c - a*d, b^3 - a^2*d],
[c^2 - b*d, b*c - a*d, b^2 - a*c]]
(continues on next page)
𝑦 2 + 𝑎1 𝑥𝑦 + 𝑎3 𝑦 = 𝑥3 + 𝑎2 𝑥2 + 𝑎4 𝑥 + 𝑎6 ,
where the 𝑎𝑖 ’s are coerced into the parent of 𝑎1 . If all the 𝑎𝑖 have parent , they are coerced into .
• EllipticCurve([𝑎4 , 𝑎6 ]): Same as above, but 𝑎1 = 𝑎2 = 𝑎3 = 0.
• EllipticCurve(label): Returns the elliptic curve over from the Cremona database with the given (new!) Cremona
label. The label is a string, such as "11a" or "37b2". The letter must be lower case (to distinguish it from the old
labeling).
• EllipticCurve(j): Returns an elliptic curve with 𝑗-invariant 𝑗.
• EllipticCurve(R, [𝑎1 , 𝑎2 , 𝑎3 , 𝑎4 , 𝑎6 ]): Create the elliptic curve over a ring 𝑅 with given 𝑎𝑖 ’s as above.
We illustrate each of these constructors:
sage: EllipticCurve([0,0,1,-1,0])
Elliptic Curve defined by y^2 + y = x^3 - x over Rational Field
sage: EllipticCurve([GF(5)(0),0,1,-1,0])
Elliptic Curve defined by y^2 + y = x^3 + 4*x over Finite Field of size 5
(continues on next page)
sage: EllipticCurve([1,2])
Elliptic Curve defined by y^2 = x^3 + x + 2 over Rational Field
sage: EllipticCurve_from_j(1)
Elliptic Curve defined by y^2 + x*y = x^3 + 36*x + 3455 over Rational Field
>>> EllipticCurve([GF(Integer(5))(Integer(0)),Integer(0),Integer(1),-Integer(1),
˓→Integer(0)])
Elliptic Curve defined by y^2 + y = x^3 + 4*x over Finite Field of size 5
>>> EllipticCurve([Integer(1),Integer(2)])
Elliptic Curve defined by y^2 = x^3 + x + 2 over Rational Field
>>> EllipticCurve_from_j(Integer(1))
Elliptic Curve defined by y^2 + x*y = x^3 + 36*x + 3455 over Rational Field
Elliptic Curve defined by y^2 + y = x^3 + 4*x over Finite Field of size 5
The pair (0, 0) is a point on the elliptic curve 𝐸 defined by 𝑦 2 + 𝑦 = 𝑥3 − 𝑥. To create this point in Sage type E([0,0]).
Sage can add points on such an elliptic curve (recall elliptic curves support an additive group structure where the point at
infinity is the zero element and three co-linear points on the curve add to zero):
sage: E = EllipticCurve([0,0,1,-1,0])
sage: E
Elliptic Curve defined by y^2 + y = x^3 - x over Rational Field
sage: P = E([0,0])
sage: P + P
(1 : 0 : 1)
sage: 10*P
(161/16 : -2065/64 : 1)
sage: 20*P
(683916417/264517696 : -18784454671297/4302115807744 : 1)
sage: E.conductor()
37
The elliptic curves over the complex numbers are parameterized by the 𝑗-invariant. Sage computes 𝑗-invariant as follows:
sage: E = EllipticCurve([0,0,0,-4,2]); E
Elliptic Curve defined by y^2 = x^3 - 4*x + 2 over Rational Field
sage: E.conductor()
2368
sage: E.j_invariant()
110592/37
If we make a curve with the same 𝑗-invariant as that of 𝐸, it need not be isomorphic to 𝐸. In the following example, the
curves are not isomorphic because their conductors are different.
sage: F = EllipticCurve_from_j(110592/37)
sage: F.conductor()
37
sage: G = F.quadratic_twist(2); G
Elliptic Curve defined by y^2 = x^3 - 4*x + 2 over Rational Field
sage: G.conductor()
2368
sage: G.j_invariant()
110592/37
Elliptic curves can be constructed using their Cremona labels. This pre-loads the elliptic curve with information about its
rank, Tamagawa numbers, regulator, etc.
sage: E = EllipticCurve("37b2")
sage: E
Elliptic Curve defined by y^2 + y = x^3 + x^2 - 1873*x - 31833 over Rational
Field
sage: E = EllipticCurve("389a")
sage: E
Elliptic Curve defined by y^2 + y = x^3 + x^2 - 2*x over Rational Field
sage: E.rank()
2
sage: E = EllipticCurve("5077a")
sage: E.rank()
3
sage: db = sage.databases.cremona.CremonaDatabase()
sage: db.curves(37)
{ a1 : [[0, 0, 1, -1, 0], 1, 1], b1 : [[0, 1, 1, -23, -50], 0, 3]}
sage: db.allcurves(37)
{ a1 : [[0, 0, 1, -1, 0], 1, 1],
b1 : [[0, 1, 1, -23, -50], 0, 3],
b2 : [[0, 1, 1, -1873, -31833], 0, 1],
b3 : [[0, 1, 1, -3, 1], 0, 3]}
The objects returned from the database are not of type EllipticCurve. They are elements of a database and have a
couple of fields, and that’s it. There is a small version of Cremona’s database, which is distributed by default with Sage,
and contains limited information about elliptic curves of conductor ≤ 10000. There is also a large optional version, which
contains extensive data about all curves of conductor up to 120000 (as of October 2005). There is also a huge (2GB)
optional database package for Sage that contains the hundreds of millions of elliptic curves in the Stein-Watkins database.
sage: G = DirichletGroup(12)
sage: G.list()
[Dirichlet character modulo 12 of conductor 1 mapping 7 |--> 1, 5 |--> 1,
Dirichlet character modulo 12 of conductor 4 mapping 7 |--> -1, 5 |--> 1,
Dirichlet character modulo 12 of conductor 3 mapping 7 |--> 1, 5 |--> -1,
Dirichlet character modulo 12 of conductor 12 mapping 7 |--> -1, 5 |--> -1]
sage: G.gens()
(Dirichlet character modulo 12 of conductor 4 mapping 7 |--> -1, 5 |--> 1,
(continues on next page)
Having created the group, we next create an element and compute with it.
sage: G = DirichletGroup(21)
sage: chi = G.1; chi
Dirichlet character modulo 21 of conductor 7 mapping 8 |--> 1, 10 |--> zeta6
sage: chi.values()
[0, 1, zeta6 - 1, 0, -zeta6, -zeta6 + 1, 0, 0, 1, 0, zeta6, -zeta6, 0, -1,
0, 0, zeta6 - 1, zeta6, 0, -zeta6 + 1, -1]
sage: chi.conductor()
7
sage: chi.modulus()
21
sage: chi.order()
6
sage: chi(19)
-zeta6 + 1
sage: chi(40)
-zeta6 + 1
It is also possible to compute the action of the Galois group Gal( (𝜁𝑁 )/ ) on these characters, as well as the direct
product decomposition corresponding to the factorization of the modulus.
sage: chi.galois_orbit()
[Dirichlet character modulo 21 of conductor 7 mapping 8 |--> 1, 10 |--> -zeta6 + 1,
Dirichlet character modulo 21 of conductor 7 mapping 8 |--> 1, 10 |--> zeta6]
sage: go = G.galois_orbits()
sage: [len(orbit) for orbit in go]
[1, 2, 2, 1, 1, 2, 2, 1]
sage: G.decomposition()
[Group of Dirichlet characters modulo 3 with values in Cyclotomic Field of order 6␣
˓→and degree 2,
>>> go = G.galois_orbits()
>>> [len(orbit) for orbit in go]
[1, 2, 2, 1, 1, 2, 2, 1]
>>> G.decomposition()
[Group of Dirichlet characters modulo 3 with values in Cyclotomic Field of order 6␣
˓→and degree 2,
Next, we construct the group of Dirichlet characters mod 20, but with values in (𝑖):
sage: G.gens()
(Dirichlet character modulo 20 of conductor 4 mapping 11 |--> -1, 17 |--> 1,
Dirichlet character modulo 20 of conductor 5 mapping 11 |--> 1, 17 |--> i)
sage: G.unit_gens()
(11, 17)
sage: G.zeta()
i
sage: G.zeta_order()
4
>>> G.unit_gens()
(11, 17)
>>> G.zeta()
i
>>> G.zeta_order()
4
In this example we create a Dirichlet character with values in a number field. We explicitly specify the choice of root of
unity by the third argument to DirichletGroup below.
sage: x = polygen(QQ, x )
sage: K = NumberField(x^4 + 1, a ); a = K.0
sage: b = K.gen(); a == b
True
sage: K
Number Field in a with defining polynomial x^4 + 1
sage: G = DirichletGroup(5, K, a); G
Group of Dirichlet characters modulo 5 with values in the group of order 8 generated␣
˓→by a in Number Field in a with defining polynomial x^4 + 1
Here NumberField(x^4 + 1, a ) tells Sage to use the symbol “a” in printing what K is (a Number Field in a with
defining polynomial 𝑥4 + 1). The name “a” is undeclared at this point. Once a = K.0 (or equivalently a = K.gen())
is evaluated, the symbol “a” represents a root of the generating polynomial 𝑥4 + 1.
Next we illustrate computation of Hecke operators on a space of modular symbols of level 1 and weight 12.
sage: M = ModularSymbols(1,12)
sage: M.basis()
([X^8*Y^2,(0,0)], [X^9*Y,(0,0)], [X^10,(0,0)])
sage: t2 = M.T(2)
sage: t2
Hecke operator T_2 on Modular Symbols space of dimension 3 for Gamma_0(1)
of weight 12 with sign 0 over Rational Field
sage: t2.matrix()
[ -24 0 0]
[ 0 -24 0]
[4860 0 2049]
sage: f = t2.charpoly( x ); f
x^3 - 2001*x^2 - 97776*x - 1180224
sage: factor(f)
(x - 2049) * (x + 24)^2
sage: M.T(11).charpoly( x ).factor()
(x - 285311670612) * (x - 534612)^2
sage: ModularSymbols(11,2)
Modular Symbols space of dimension 3 for Gamma_0(11) of weight 2 with sign
0 over Rational Field
sage: ModularSymbols(Gamma1(11),2)
Modular Symbols space of dimension 11 for Gamma_1(11) of weight 2 with
sign 0 over Rational Field
sage: M = ModularSymbols(Gamma1(11),2)
sage: M.T(2).charpoly( x )
x^11 - 8*x^10 + 20*x^9 + 10*x^8 - 145*x^7 + 229*x^6 + 58*x^5 - 360*x^4
+ 70*x^3 - 515*x^2 + 1804*x - 1452
sage: M.T(2).charpoly( x ).factor()
(x - 3) * (x + 2)^2 * (x^4 - 7*x^3 + 19*x^2 - 23*x + 11)
* (x^4 - 2*x^3 + 4*x^2 + 2*x + 11)
sage: S = M.cuspidal_submodule()
sage: S.T(2).matrix()
[-2 0]
[ 0 -2]
sage: S.q_expansion_basis(10)
[q - 2*q^2 - q^3 + 2*q^4 + q^5 + 2*q^6 - 2*q^7 - 2*q^9 + O(q^10)]
sage: G = DirichletGroup(13)
sage: e = G.0^2
sage: M = ModularSymbols(e,2); M
Modular Symbols space of dimension 4 and level 13, weight 2, character
[zeta6], sign 0, over Cyclotomic Field of order 6 and degree 2
sage: M.T(2).charpoly( x ).factor()
(x - zeta6 - 2) * (x - 2*zeta6 - 1) * (x + zeta6 + 1)^2
sage: S = M.cuspidal_submodule(); S
Modular Symbols subspace of dimension 2 of Modular Symbols space of
dimension 4 and level 13, weight 2, character [zeta6], sign 0, over
Cyclotomic Field of order 6 and degree 2
sage: S.T(2).charpoly( x ).factor()
(x + zeta6 + 1)^2
sage: S.q_expansion_basis(10)
[q + (-zeta6 - 1)*q^2 + (2*zeta6 - 2)*q^3 + zeta6*q^4 + (-2*zeta6 + 1)*q^5 + (-
˓→2*zeta6 + 4)*q^6 + (2*zeta6 - 1)*q^8 - zeta6*q^9 + O(q^10)]
Here is another example of how Sage can compute the action of Hecke operators on a space of modular forms.
sage: T = ModularForms(Gamma0(11),2)
sage: T
Modular Forms space of dimension 2 for Congruence Subgroup Gamma0(11) of
weight 2 over Rational Field
sage: T.degree()
2
sage: T.level()
11
sage: T.group()
Congruence Subgroup Gamma0(11)
sage: T.dimension()
2
sage: T.cuspidal_subspace()
Cuspidal subspace of dimension 1 of Modular Forms space of dimension 2 for
Congruence Subgroup Gamma0(11) of weight 2 over Rational Field
sage: T.eisenstein_subspace()
Eisenstein subspace of dimension 1 of Modular Forms space of dimension 2
for Congruence Subgroup Gamma0(11) of weight 2 over Rational Field
sage: M = ModularSymbols(11); M
Modular Symbols space of dimension 3 for Gamma_0(11) of weight 2 with sign
0 over Rational Field
sage: M.weight()
2
sage: M.basis()
((1,0), (1,8), (1,9))
sage: M.sign()
0
Let 𝑇𝑝 denote the usual Hecke operators (𝑝 prime). How do the Hecke operators 𝑇2 , 𝑇3 , 𝑇5 act on the space of modular
symbols?
sage: M.T(2).matrix()
[ 3 0 -1]
[ 0 -2 0]
[ 0 0 -2]
sage: M.T(3).matrix()
[ 4 0 -1]
[ 0 -1 0]
[ 0 0 -1]
sage: M.T(5).matrix()
[ 6 0 -1]
[ 0 1 0]
[ 0 0 1]
THREE
In most of this tutorial, we assume you start the Sage interpreter using the sage command. This starts a customized
version of the IPython shell, and imports many functions and classes, so they are ready to use from the command prompt.
Further customization is possible by editing the $SAGE_ROOT/ipythonrc file. Upon starting Sage, you get output
similar to the following:
┌────────────────────────────────────────────────────────────────────┐
│ SageMath version 9.7, Release Date: 2022-01-10 │
│ Using Python 3.10.4. Type "help()" for help. │
└────────────────────────────────────────────────────────────────────┘
sage:
sage: quit
Exiting Sage (CPU time 0m0.00s, Wall time 0m0.89s)
The wall time is the time that elapsed on the clock hanging from your wall. This is relevant, since CPU time does not
track time used by subprocesses like GAP or Singular.
(Avoid killing a Sage process with kill -9 from a terminal, since Sage might not kill child processes, e.g., Maple
processes, or cleanup temporary files from $HOME/.sage/tmp.)
89
Tutorial, Release 10.6
Here is an example:
sage: factor(100)
_1 = 2^2 * 5^2
sage: kronecker_symbol(3,5)
_2 = -1
sage: %hist #This only works from the interactive shell, not the notebook.
1: factor(100)
2: kronecker_symbol(3,5)
3: %hist
sage: _oh
_4 = {1: 2^2 * 5^2, 2: -1}
sage: _i1
_5 = factor(ZZ(100))\n
sage: eval(_i1)
_6 = 2^2 * 5^2
sage: %hist
1: factor(100)
2: kronecker_symbol(3,5)
3: %hist
4: _oh
5: _i1
6: eval(_i1)
7: %hist
We omit the output numbering in the rest of this tutorial and the other Sage documentation.
You can also store a list of input from session in a macro for that session.
sage: E = EllipticCurve([1,2,3,4,5])
sage: M = ModularSymbols(37)
sage: %hist
1: E = EllipticCurve([1,2,3,4,5])
2: M = ModularSymbols(37)
3: %hist
sage: %macro em 1-2
Macro em created. To execute, type its name (without quotes).
sage: E
Elliptic Curve defined by y^2 + x*y + 3*y = x^3 + 2*x^2 + 4*x + 5 over
Rational Field
sage: E = 5
sage: M = None
sage: em
Executing Macro...
sage: E
Elliptic Curve defined by y^2 + x*y + 3*y = x^3 + 2*x^2 + 4*x + 5 over
Rational Field
When using the interactive shell, any UNIX shell command can be executed from Sage by prefacing it by an exclamation
point !. For example,
sage: !ls
auto example.sage glossary.tex t tmp tut.log tut.tex
The PATH has the Sage bin directory at the front, so if you run gp, gap, singular, maxima, etc., you get the versions
included with Sage.
sage: !gp
Reading GPRC: /etc/gprc ...Done.
was@form:~$ sage
┌────────────────────────────────────────────────────────────────────┐
│ SageMath version 9.7, Release Date: 2022-01-10 │
│ Using Python 3.10.4. Type "help()" for help. │
└────────────────────────────────────────────────────────────────────┘
sage: load("setup")
Loading log file <setup> one line at a time...
Finished replaying log file <setup>
sage: E
Elliptic Curve defined by y^2 + x*y = x^3 - x^2 + 4*x + 3 over Rational
Field
sage: x*y
x*y
sage: G
[(2 : 3 : 1)]
If you use Sage in the Linux KDE terminal konsole then you can save your session as follows: after starting Sage in
konsole, select “settings”, then “history…”, then “set unlimited”. When you are ready to save your session, select “edit”
then “save history as…” and type in a name to save the text of your session to your computer. After saving this file, you
could then load it into an editor, such as xemacs, and print it.
sage: 2^10
1024
sage: sage: sage: 2^10
1024
sage: >>> 2^10
1024
This means that 0.66 seconds total were taken, and the “Wall time”, i.e., the amount of time that elapsed on your wall
clock, is also 0.66 seconds. If your computer is heavily loaded with other programs, the wall time may be much larger
than the CPU time.
It’s also possible to use the timeit function to try to get timing over a large number of iterations of a command. This
gives slightly different information, and requires the input of a string with the command you want to time.
sage: timeit("int(1938)^int(99484)")
5 loops, best of 3: 44.8 ms per loop
Next we time exponentiation using the native Sage Integer type, which is implemented (in Cython) using the GMP library:
GMP is better, but only slightly (as expected, since the version of PARI built for Sage uses GMP for integer arithmetic).
You can also time a block of commands using the cputime command, as illustrated below:
sage: t = cputime()
sage: a = int(1938)^int(99484)
sage: b = 1938^99484
sage: c = pari(1938)^pari(99484)
sage: cputime(t) # somewhat random output
0.64
sage: cputime?
...
Return the time in CPU second since Sage started, or with optional
argument t, return the time since time t.
INPUT:
t -- (optional) float, time in CPU seconds
OUTPUT:
float -- time in CPU seconds
The walltime command behaves just like the cputime command, except that it measures wall time.
We can also compute the above power in some of the computer algebra systems that Sage includes. In each case we
execute a trivial command in the system, in order to start up the server for that program. The most relevant time is the
wall time. However, if there is a significant difference between the wall time and the CPU time then this may indicate a
performance issue worth looking into.
sage: time 1938^99484;
CPU times: user 0.01 s, sys: 0.00 s, total: 0.01 s
Wall time: 0.01
sage: gp(0)
0
sage: time g = gp( 1938^99484 )
CPU times: user 0.00 s, sys: 0.00 s, total: 0.00 s
Wall time: 0.04
sage: maxima(0)
0
sage: time g = maxima( 1938^99484 )
CPU times: user 0.00 s, sys: 0.00 s, total: 0.00 s
(continues on next page)
Note that GAP and Maxima are the slowest in this test (this was run on the machine sage.math.washington.edu).
Because of the pexpect interface overhead, it is perhaps unfair to compare these to Sage, which is the fastest.
def some_function(n):
return n**2 + 3*n + 2
Save and quit from the editor. For the rest of your Sage session, you can then use some_function. If you want
to modify it, type %edit some_function from the Sage prompt.
• If you have a computation and you want to modify its output for another use, perform the computation and type
%rep: this will place the output from the previous command at the Sage prompt, ready for you to edit it.
At this point, if you type %rep at the Sage prompt, you will get a new Sage prompt, followed by -sin(x), with
the cursor at the end of the line.
For more, type %quickref to get a quick reference guide to IPython. As of this writing (April 2011), Sage uses version
0.9.1 of IPython, and the documentation for its magic commands is available online. Various slightly advanced aspects
of magic command system are documented here in IPython.
sage: 3_2
------------------------------------------------------------
File "<console>", line 1
ZZ(3)_2
^
SyntaxError: invalid ...
sage: EllipticCurve([0,infinity])
------------------------------------------------------------
Traceback (most recent call last):
...
TypeError: Unable to coerce Infinity (<class sage...Infinity >) to Rational
>>> EllipticCurve([Integer(0),infinity])
------------------------------------------------------------
Traceback (most recent call last):
...
TypeError: Unable to coerce Infinity (<class sage...Infinity >) to Rational
The interactive debugger is sometimes useful for understanding what went wrong. You can toggle it on or off using %pdb
(the default is off). The prompt ipdb> appears if an exception is raised and the debugger is on. From within the debugger,
you can print the state of any local variable, and move up and down the execution stack. For example,
sage: %pdb
Automatic pdb calling has been turned ON
sage: EllipticCurve([1,infinity])
---------------------------------------------------------------------------
<class exceptions.TypeError > Traceback (most recent call last)
...
ipdb>
ipdb>
ipdb> ?
Undocumented commands:
======================
retval rv
sage: V = VectorSpace(QQ,3)
sage: V
Vector space of dimension 3 over Rational Field
sage: V = QQ^3
Then it is easy to list all member functions for 𝑉 using tab completion. Just type V., then type the Tab key on your
keyboard:
If you type the first few letters of a function, then the Tab key, you get only functions that begin as indicated.
If you wonder what a particular function does, e.g., the coordinates function, type V.coordinates? for help or V.
coordinates?? for the source code, as explained in the next section.
sage: V = QQ^3
sage: V.coordinates?
Type: instancemethod
Base Class: <class instancemethod >
String Form: <bound method FreeModule_ambient_field.coordinates of Vector
space of dimension 3 over Rational Field>
Namespace: Interactive
File: /home/was/s/local/lib/python2.4/site-packages/sage/modules/f
ree_module.py
Definition: V.coordinates(self, v)
Docstring:
Write v in terms of the basis for self.
EXAMPLES:
sage: M = FreeModule(IntegerRing(), 2); M0,M1=M.gens()
sage: W = M.submodule([M0 + M1, M0 - 2*M1])
sage: W.coordinates(2*M0-M1)
[2, -1]
EXAMPLES:
>>> M = FreeModule(IntegerRing(), Integer(2)); M0,M1=M.gens()
>>> W = M.submodule([M0 + M1, M0 - Integer(2)*M1])
>>> W.coordinates(Integer(2)*M0-M1)
[2, -1]
As shown above, the output tells you the type of the object, the file in which it is defined, and a useful description of
the function with examples that you can paste into your current session. Almost all of these examples are regularly
automatically tested to make sure they work and behave exactly as claimed.
Another feature that is very much in the spirit of the open source nature of Sage is that if f is a Python function, then
typing f?? displays the source code that defines f. For example,
sage: V = QQ^3
sage: V.coordinates??
Type: instancemethod
...
Source:
def coordinates(self, v):
"""
Write $v$ in terms of the basis for self.
...
(continues on next page)
This tells us that all the coordinates function does is call the coordinate_vector function and change the result
into a list. What does the coordinate_vector function do?
sage: V = QQ^3
sage: V.coordinate_vector??
...
def coordinate_vector(self, v):
...
return self.ambient_vector_space()(v)
The coordinate_vector function coerces its input into the ambient space, which has the effect of computing the vector
of coefficients of 𝑣 in terms of 𝑉 . The space 𝑉 is already ambient since it’s just 3 . There is also a coordinate_vector
function for subspaces, and it’s different. We create a subspace and see:
(If you think the implementation is inefficient, please sign up to help optimize linear algebra.)
You may also type help(command_name) or help(class) for a manpage-like help file about a given class.
sage: help(VectorSpace)
Help on function VectorSpace in module sage.modules.free_module:
::
::
(continues on next page)
When you type q to exit the help system, your session appears just as it was. The help listing does not clutter up your ses-
sion, unlike the output of function_name? sometimes does. It’s particularly helpful to type help(module_name). For
example, vector spaces are defined in sage.modules.free_module, so type help(sage.modules.free_module)
for documentation about that whole module. When viewing documentation using help, you can search by typing / and in
reverse by typing ?.
sage: A = MatrixSpace(QQ,3)(range(9))^2
sage: A
[ 15 18 21]
[ 42 54 66]
[ 69 90 111]
sage: save(A, A )
You should now quit Sage and restart. Then you can get A back:
sage: A = load( A )
sage: A
[ 15 18 21]
[ 42 54 66]
[ 69 90 111]
You can do the same with more complicated objects, e.g., elliptic curves. All data about the object that is cached is stored
with the object. For example,
The saved version of E takes 153 kilobytes, since it stores the first 100000 𝑎𝑛 with it.
~/tmp$ ls -l E.sobj
-rw-r--r-- 1 was was 153500 2006-01-28 19:23 E.sobj
~/tmp$ sage [...]
sage: E = load( E )
sage: v = E.anlist(100000) # instant!
(In Python, saving and loading is accomplished using the cPickle module. In particular, a Sage object x can be saved
via cPickle.dumps(x, 2). Note the 2!)
Sage cannot save and load individual objects created in some other computer algebra systems, e.g., GAP, Singular, Max-
ima, etc. They reload in a state marked “invalid”. In GAP, though many objects print in a form from which they can be
reconstructed, many don’t, so reconstructing from their print representation is purposely not allowed.
sage: a = libgap(2)
sage: a.save( a )
sage: load( a )
Traceback (most recent call last):
...
ValueError: The session in which this object was defined is no longer
running.
GP/PARI objects can be saved and loaded since their print representation is enough to reconstruct them.
sage: a = gp(2)
sage: a.save( a )
sage: load( a )
2
Saved objects can be re-loaded later on computers with different architectures or operating systems, e.g., you could save a
huge matrix on 32-bit OS X and reload it on 64-bit Linux, find the echelon form, then move it back. Also, in many cases
you can even load objects into versions of Sage that are different than the versions they were saved in, as long as the code
for that object isn’t too different. All the attributes of the objects are saved, along with the class (but not source code) that
defines the object. If that class no longer exists in a new version of Sage, then the object can’t be reloaded in that newer
version. But you could load it in an old version, get the objects dictionary (with x.__dict__), and save the dictionary,
and load that into the newer version.
dictionary.) The resulting file is an .sobj file and can be loaded just like any other object that was saved. When you load
the objects saved in a session, you get a dictionary whose keys are the variables names and whose values are the objects.
You can use the load_session(sessionname) command to load the variables defined in sessionname into the
current session. Note that this does not wipe out variables you’ve already defined in your current session; instead, the two
sessions are merged.
First we start Sage and define some variables.
Next we save our session, which saves each of the above variables into a file. Then we view the file, which is about 3K in
size.
Finally we restart Sage, define an extra variable, and load our saved session.
sage: b = 19
sage: load_session( misc )
Loading a
Loading M
Loading E
Loading t
Each saved variable is again available. Moreover, the variable b was not overwritten.
sage: M
Full Modular Symbols space for Gamma_0(37) of weight 2 with sign 0
and dimension 5 over Rational Field
sage: E
Elliptic Curve defined by y^2 + y = x^3 - x^2 - 10*x - 20 over Rational
Field
sage: b
19
sage: a
389
FOUR
INTERFACES
A central facet of Sage is that it supports computation with objects in many different computer algebra systems “under
one roof” using a common interface and clean programming language.
The console and interact methods of an interface do very different things. For example, using GAP as an example:
1. gap.console(): This opens the GAP console - it transfers control to GAP. Here Sage is serving as nothing more
than a convenient program launcher, similar to the Linux bash shell.
2. gap.interact(): This is a convenient way to interact with a running GAP instance that may be “full of” Sage
objects. You can import Sage objects into this GAP session (even from the interactive interface), etc.
4.1 GP/PARI
PARI is a compact, very mature, highly optimized C program whose primary focus is number theory. There are two very
distinct interfaces that you can use in Sage:
• gp – the PARI interpreter, and
• pari – the PARI C library.
For example, the following are two ways of doing the same thing. They look identical, but the output is actually different,
and what happens behind the scenes is drastically different.
In the first case, a separate copy of the GP interpreter is started as a server, and the string znprimroot(10007) is
sent to it, evaluated by GP, and the result is assigned to a variable in GP (which takes up space in the child GP processes
memory that won’t be freed). Then the value of that variable is displayed. In the second case, no separate program is
started, and the string znprimroot(10007) is evaluated by a certain PARI C library function. The result is stored
in a piece of memory on the Python heap, which is freed when the variable is no longer referenced. The objects have
different types:
109
Tutorial, Release 10.6
So which should you use? It depends on what you’re doing. The GP interface can do absolutely anything you could do
in the usual GP/PARI command line program, since it is running that program. In particular, you can load complicated
PARI programs and run them. In contrast, the PARI interface (via the C library) is much more restrictive. First, not all
member functions have been implemented. Second, a lot of code, e.g., involving numerical integration, won’t work via
the PARI interface. That said, the PARI interface can be significantly faster and more robust than the GP one.
(If the GP interface runs out of memory evaluating a given input line, it will silently and automatically double the stack
size and retry that input line. Thus your computation won’t crash if you didn’t correctly anticipate the amount of memory
that would be needed. This is a nice trick the usual GP interpreter doesn’t seem to provide. Regarding the PARI C library
interface, it immediately copies each created object off of the PARI stack, hence the stack never grows. However, each
object must not exceed 100MB in size, or the stack will overflow when the object is being created. This extra copying
does impose a slight performance penalty.)
In summary, Sage uses the PARI C library to provide functionality similar to that provided by the GP/PARI interpreter,
except with different sophisticated memory management and the Python programming language.
First we create a PARI list from a Python list.
sage: v = pari([1,2,3,4,5])
sage: v
[1, 2, 3, 4, 5]
sage: type(v)
<class cypari2.gen.Gen >
Every PARI object is of type Gen. The PARI type of the underlying object can be obtained using the type member
function.
sage: v.type()
t_VEC
In PARI, to create an elliptic curve we enter ellinit([1,2,3,4,5]). Sage is similar, except that ellinit is a
method that can be called on any PARI object, e.g., our t_VEC 𝑣.
sage: e = v.ellinit()
sage: e.type()
t_VEC
sage: pari(e)[:13]
[1, 2, 3, 4, 5, 9, 11, 29, 35, -183, -3429, -10351, 6128487/10351]
Now that we have an elliptic curve object, we can compute some things about it.
sage: e.elltors()
[1, [], []]
sage: e.ellglobalred()
[10351, [1, -1, 0, -1], 1, [11, 1; 941, 1], [[1, 5, 0, 1], [1, 5, 0, 1]]]
sage: f = e.ellchangecurve([1,-1,0,-1])
sage: f[:5]
[1, -1, 0, 4, 3]
4.2 GAP
Sage comes with GAP for computational discrete mathematics, especially group theory.
Here’s an example of GAP’s IdGroup function.
We can do the same computation in Sage without explicitly invoking the GAP interface as follows:
sage: G = PermutationGroup([[(1,2,3),(4,5)],[(3,4)]])
sage: G.center()
Subgroup generated by [()] of (Permutation Group with generators [(3,4), (1,2,3)(4,
˓→5)])
sage: G.group_id()
[120, 34]
sage: n = G.order(); n
120
>>> G.center()
Subgroup generated by [()] of (Permutation Group with generators [(3,4), (1,2,3)(4,
˓→5)])
>>> G.group_id()
[120, 34]
>>> n = G.order(); n
120
For some GAP functionality, you should install an optional Sage packages. This can be done with the command:
sage -i gap_packages
4.3 Singular
Singular provides a massive and mature library for Gröbner bases, multivariate polynomial gcds, bases of Riemann-Roch
spaces of a plane curve, and factorizations, among other things. We illustrate multivariate polynomial factorization using
the Sage interface to Singular (do not type the ....:):
sage: f
9*x^16-18*x^13*y^2-9*x^12*y^3+9*x^10*y^4-18*x^11*y^2+36*x^8*y^4+18*x^7*y^5-18*x^5*y^
˓→6+9*x^6*y^4-18*x^3*y^6-9*x^2*y^7+9*y^8
sage: f.parent()
Singular
sage: F = f.factorize(); F
[1]:
_[1]=9
_[2]=x^6-2*x^3*y^2-x^2*y^3+y^4
_[3]=-x^5+y^2
[2]:
1,1,2
sage: F[1][2]
x^6-2*x^3*y^2-x^2*y^3+y^4
>>> f.parent()
Singular
>>> F = f.factorize(); F
[1]:
_[1]=9
_[2]=x^6-2*x^3*y^2-x^2*y^3+y^4
_[3]=-x^5+y^2
[2]:
1,1,2
>>> F[Integer(1)][Integer(2)]
x^6-2*x^3*y^2-x^2*y^3+y^4
As with the GAP example in GAP, we can compute the above factorization without explicitly using the Singular interface
(however, behind the scenes Sage uses the Singular interface for the actual computation). Do not type the ....::
sage: x, y = QQ[ x, y ].gens()
sage: f = (9*y^8 - 9*x^2*y^7 - 18*x^3*y^6 - 18*x^5*y^6 + 9*x^6*y^4
....: + 18*x^7*y^5 + 36*x^8*y^4 + 9*x^10*y^4 - 18*x^11*y^2 - 9*x^12*y^3
....: - 18*x^13*y^2 + 9*x^16)
(continues on next page)
˓→Integer(9)*x**Integer(6)*y**Integer(4)
... + Integer(18)*x**Integer(7)*y**Integer(5) +␣
˓→Integer(36)*x**Integer(8)*y**Integer(4) + Integer(9)*x**Integer(10)*y**Integer(4) -␣
˓→Integer(18)*x**Integer(11)*y**Integer(2) - Integer(9)*x**Integer(12)*y**Integer(3)
4.4 Maxima
Maxima is included with Sage, as well as a Lisp implementation. The gnuplot package (which Maxima uses by default for
plotting) is distributed as a Sage optional package. Among other things, Maxima does symbolic manipulation. Maxima
can integrate and differentiate functions symbolically, solve 1st order ODEs, most linear 2nd order ODEs, and has imple-
mented the Laplace transform method for linear ODEs of any degree. Maxima also knows about a wide range of special
functions, has plotting capabilities via gnuplot, and has methods to solve and manipulate matrices (such as row reduction,
eigenvalues and eigenvectors), and polynomial equations.
We illustrate the Sage/Maxima interface by constructing the matrix whose 𝑖, 𝑗 entry is 𝑖/𝑗, for 𝑖, 𝑗 = 1, . . . , 4.
sage: M = MatrixSpace(QQ,3,3)
sage: AA = M([[1,0,0],[1, - 1,0],[1,3, - 2]])
sage: b1 = v1.base_ring()
sage: AA*v1 == b1(lambda1)*v1
True
sage: b2 = v2.base_ring()
sage: AA*v2 == b2(lambda2)*v2
True
sage: b3 = v3.base_ring()
sage: AA*v3 == b3(lambda3)*v3
True
>>> M = MatrixSpace(QQ,Integer(3),Integer(3))
>>> AA = M([[Integer(1),Integer(0),Integer(0)],[Integer(1), - Integer(1),Integer(0)],
˓→[Integer(1),Integer(3), - Integer(2)]])
>>> b1 = v1.base_ring()
>>> AA*v1 == b1(lambda1)*v1
True
>>> b2 = v2.base_ring()
>>> AA*v2 == b2(lambda2)*v2
True
>>> b3 = v3.base_ring()
>>> AA*v3 == b3(lambda3)*v3
True
Finally, we give an example of using Sage to plot using openmath. Many of these were modified from the Maxima
reference manual.
A 2D plot of several functions (do not type the ....:):
A “live” 3D plot which you can move with your mouse (do not type the ....:):
sage: maxima.plot3d ("2^(-u^2 + v^2)", "[u, -3, 3]", "[v, -2, 2]", # not tested
....: [plot_format, openmath] )
sage: maxima.plot3d("atan(-x^2 + y^3/4)", "[x, -4, 4]", "[y, -4, 4]", # not tested
....: "[grid, 50, 50]", [plot_format, openmath] )
The next plot is the famous Möbius strip (do not type the ....:):
The next plot is the famous Klein bottle (do not type the ....:):
FIVE
Sage and the LaTeX dialect of TeX have an intensely synergistic relationship. This section aims to introduce the variety
of interactions, beginning with the most basic and proceeding to the more unusual.
sage: var( z )
z
sage: latex(z^12)
z^{12}
sage: latex(sqrt(z^2 + 1/2))
\sqrt{z^{2} + \frac{1}{2}}
sage: latex( a string )
\text{\texttt{a{ }string}}
sage: latex(QQ)
\Bold{Q}
sage: latex(ZZ[ x ])
\Bold{Z}[x]
sage: latex(matrix(QQ, 2, 3, [[2,4,6],[-1,-1,-1]]))
\left(\begin{array}{rrr}
2 & 4 & 6 \\
-1 & -1 & -1
\end{array}\right)
117
Tutorial, Release 10.6
\left(\begin{array}{rrr}
2 & 4 & 6 \\
-1 & -1 & -1
\end{array}\right)
In this way, Sage can be used effectively for constructing portions of a LaTeX document: create or compute an object in
Sage, do latex(foo) of the object foo and cut/paste the LaTeX string into your document.
The command view(foo) will show the rendered LaTeX representation of foo. In the background, the command
runs latex(foo) and incorporates the LaTeX string into a simple LaTeX document, processes that document with the
system-wide TeX installation, and finally an appropriate viewer will be called to display the output.
In the Jupyter notebook, you can see the rendered LaTeX representation of the output of the entered commands auto-
matically. You can start this automatic rendering by executing %display latex (and stop by executing %display
plain).
The Jupyter notebook uses MathJax to render mathematics cleanly in a web browser. MathJax is an open source JavaScript
display engine for mathematics that works in all modern browsers. It is able to render a large, but not totally complete,
subset of LaTeX. It has no support for things like complicated tables, sectioning or document management, as it is oriented
towards accurately rendering math snippets of LaTeX.
The automatic LaTeX rendering in the Jupyter notebook (with %display latex on) is internally done via the sage.
misc.html.MathJax class. The object of this class converts a Sage object through latex() to a form of HTML
palatable to MathJax and then wraps it in HTML.
<html>\[\left(\begin{array}{rrr}
2 & 4 & 6 \\
-1 & -1 & -1
\end{array}\right)\]</html>
This is useful to know if you need to understand the LaTeX rendering of a Sage object.
It is possible to take advantage of the extensible nature of LaTeX by adding in new macros. Individual macros can be
added so that they are used when MathJax interprets a LaTeX snippet.
sage: latex.add_macro(r"\newcommand{\sqrt}[1]{(#1)^\frac{1}{2}}")
sage: latex.extra_macros()
\\newcommand{\\sqrt}[1]{(#1)^\\frac{1}{2}}
(continues on next page)
sage: latex.extra_macros( )
sage: latex.extra_preamble( )
sage: from sage.misc.latex import latex_extra_preamble
sage: print(latex_extra_preamble())
\newcommand{\ZZ}{\Bold{Z}}
...
\newcommand{\Bold}[1]{\mathbf{#1}}
sage: latex.add_macro("\\newcommand{\\foo}{bar}")
sage: print(latex_extra_preamble())
\newcommand{\ZZ}{\Bold{Z}}
...
\newcommand{\Bold}[1]{\mathbf{#1}}
\newcommand{\foo}{bar}
Again, for larger or more complicated LaTeX expressions, it is possible to add packages (or anything else) to the preamble
of the LaTeX file. Anything may be incorporated into the preamble with the latex.add_to_preamble command, and
the specialized command latex.add_package_to_preamble_if_available will first check if a certain package
is actually available before trying to add it to the preamble.
Here we add the geometry package to the preamble and use it to set the size of the region on the page that TeX will use
(effectively setting the margins). As usual, note the need for the double-backslashes in the Python strings.
sage: from sage.misc.latex import latex_extra_preamble
sage: latex.extra_macros( )
sage: latex.extra_preamble( )
sage: latex.add_to_preamble( \\usepackage{geometry} )
sage: latex.add_to_preamble( \\geometry{letterpaper,total={8in,10in}} )
sage: latex.extra_preamble()
\\usepackage{geometry}\\geometry{letterpaper,total={8in,10in}}
sage: print(latex_extra_preamble())
\usepackage{geometry}\geometry{letterpaper,total={8in,10in}}
\newcommand{\ZZ}{\Bold{Z}}
...
\newcommand{\Bold}[1]{\mathbf{#1}}
A particular package may be added along with a check on its existence, as follows. As an example, we just illustrate an
attempt to add to the preamble a package that presumably does not exist.
sage: latex.extra_preamble( )
sage: latex.extra_preamble()
Which dialect of TeX is used, and therefore the nature of the output and associated viewer, can also be customized.
INFO-CIRCLE Note
Sage includes almost everything you need to build and use Sage, but a significant exception is TeX itself. So in the
following situations you need to have a full TeX system installed, along with some associated conversion utilities.
Many versions of Linux have packages based on TeXLive, for macOS there is MacTeX and for Windows there is
MiKTeX.
The latex.engine() command can be used to control if the system-wide executables latex, pdflatex or xelatex
are employed. When view() is called and the engine is set to latex, a dvi file is produced and Sage will use a dvi viewer
(like xdvi) to display the result. In contrast, using view() when the engine is set to pdflatex will produce a PDF as
the result and Sage will call your system’s utility for displaying PDF files (acrobat, okular, evince, etc.).
For your exercises with these facilities, there are some pre-packaged examples. To use these, it is necessary to import
the sage.misc.latex.latex_examples object, which is an instance of the sage.misc.latex.LatexExamples
class, as illustrated below. This class currently has examples of commutative diagrams, combinatorial graphs, knot theory
and pstricks, which respectively exercise the following packages: xy, tkz-graph, xypic, pstricks. After the import, use
tab-completion on latex_examples to see the pre-packaged examples. Calling each example will give you back some
explanation about what is required to make the example render properly. To actually see the examples, it is necessary to
use view(foo) (once the preamble, engine, etc are all set properly).
To use, try to view this object -- it will not work. Now try
latex.add_to_preamble("\\usepackage[matrix,arrow,curve,cmtip]{xy}") ,
and try viewing again. You should get a picture (a part of the diagram arising
from a filtered chain complex).
For an example of how complicated LaTeX expressions can be processed, let us see the example of combinatorial graphs,
that use tkz-graph LaTeX package.
INFO-CIRCLE Note
tkz-graph LaTeX package is built on top of the tikz front-end to the pgf library. Rendering combinatorial graphs
requires the pgf library, and the files tkz-graph.sty and tkz-berge.sty. It is highly likely that they are already
part of your system-wide TeX installation. Even if not, it should be easy to find instructions to install them.
First, we ensure that the relevant packages are included by adding them to the preamble of the LaTeX document.
The images of graphs do not form properly when a dvi file is used as an intermediate format, so it is best to set the latex
engine to the pdflatex executable:
At this point a command like view(graphs.CompleteGraph(4)) should produce a PDF with an appropriate image
of the complete graph 𝐾4 .
Actually the preliminary steps could be omitted as the preamble is automatically set up properly for graphs and pdflatex
is the default LaTeX engine in Sage. Try the command again after restarting Sage.
Note that there is a variety of options to affect how a graph is rendered in LaTeX via tkz-graph, which is outside the
scope of this section. See the section LaTeX options for graphs of the Reference Manual for instructions and details.
5.4 SageTeX
SageTeX is a program available to further integrate TeX and Sage. It is a collection of TeX macros that allow a LaTeX
document to include instructions to have Sage compute various objects and format objects using the latex(). See Using
SageTeX for more information.
SIX
PROGRAMMING
print("Hello World")
print(2^3)
You can read in and execute example.sage file using the load command.
sage: load("example.sage")
Hello World
8
You can also attach a Sage file to a running session using the attach command:
sage: attach("example.sage")
Hello World
8
Now if you change example.sage and enter one blank line into Sage (i.e., hit return), then the contents of example.
sage will be automatically reloaded into Sage.
In particular, attach automatically reloads a file whenever it changes, which is handy when debugging code, whereas
load only loads a file once.
When Sage loads example.sage it converts it to Python, which is then executed by the Python interpreter. This con-
version is minimal; it mainly involves wrapping integer literals in Integer() floating point literals in RealNumber(),
replacing ^’s by **’s, and replacing e.g., R.2 by R.gen(2). The converted version of example.sage is contained in
the same directory as example.sage and is called example.sage.py. This file contains the following code:
125
Tutorial, Release 10.6
print("Hello World")
print(Integer(2)**Integer(3))
Integer literals are wrapped and the ^ is replaced by a **. (In Python ^ means “exclusive or” and ** means “exponenti-
ation”.)
(This preparsing is implemented in sage/misc/interpreter.py.)
You can paste multi-line indented code into Sage as long as there are newlines to make new blocks (this is not necessary
in files). However, the best way to enter such code into Sage is to save it to a file and use attach, as described above.
NO Sage preparsing is applied to spyx files, e.g., 1/3 will result in 0 in a spyx file instead of the rational number 1/3. If
foo is a function in the Sage library, to use it from a spyx file import sage.all and use sage.all.foo.
import sage.all
def foo(n):
return sage.all.factorial(n)
int add_one(int n) {
return n + 1;
}
def test(n):
return add_one(n)
sage: attach("test.spyx")
Compiling (...)/test.spyx...
sage: test(10)
11
If an additional library foo is needed to compile the C code generated from a Cython file, add the line clib foo to the
Cython source. Similarly, an additional C file bar can be included in the compilation with the declaration cfile bar.
#!/usr/bin/env sage
import sys
if len(sys.argv) != 2:
print("Usage: %s <n>" % sys.argv[0])
print("Outputs the prime factorization of n.")
sys.exit(1)
print(factor(sage_eval(sys.argv[1])))
In order to use this script, your SAGE_ROOT must be in your PATH. If the above script is called factor, here is an
example usage:
$ ./factor 2006
2 * 17 * 59
Only certain functions can be called on V. In other math software systems, these would be called using the “func-
tional” notation foo(V,...). In Sage, certain functions are attached to the type (or class) of V, and are called using
an object-oriented syntax like in Java or C++, e.g., V.foo(...). This helps keep the global namespace from being pol-
luted with tens of thousands of functions, and means that many different functions with different behavior can be named
foo, without having to use type-checking of arguments (or case statements) to decide which to call. Also, if you reuse
the name of a function, that function is still available (e.g., if you call something zeta, then want to compute the value
of the Riemann-Zeta function at 0.5, you can still type s=.5; s.zeta()).
sage: zeta = -1
sage: s=.5; s.zeta()
-1.46035450880959
In some very common cases, the usual functional notation is also supported for convenience and because mathematical
expressions might look confusing using object-oriented notation. Here are some examples.
sage: n = 2; n.sqrt()
sqrt(2)
(continues on next page)
To list all member functions for 𝐴, use tab completion. Just type A., then type the [tab] key on your keyboard, as
explained in Reverse Search and Tab Completion.
(When indexing into a list, it is OK if the index is not a Python int!) A Sage Integer (or Rational, or anything with an
__index__ method) will work just fine.
sage: v = [1,2,3]
sage: v[2]
3
sage: n = 2 # Sage Integer
sage: v[n] # Perfectly OK!
3
sage: v[int(n)] # Also OK.
3
The range function creates a list of Python int’s (not Sage Integers):
For more about how to create lists using list comprehensions, see [PyT].
List slicing is a wonderful feature. If L is a list, then L[m:n] returns the sublist of L obtained by starting at the 𝑚𝑡ℎ
element and stopping at the (𝑛 − 1)𝑠𝑡 element, as illustrated below.
Tuples are similar to lists, except they are immutable, meaning once they are created they can’t be changed.
sage: v = (1,2,3,4); v
(1, 2, 3, 4)
sage: type(v)
<... tuple >
sage: v[1] = 5
Traceback (most recent call last):
...
TypeError: tuple object does not support item assignment
Sequences are a third list-oriented Sage type. Unlike lists and tuples, Sequence is not a built-in Python type. By default,
a sequence is mutable, but using the Sequence class method set_immutable, it can be set to be immutable, as the
following example illustrates. All elements of a sequence have a common parent, called the sequences universe.
sage: v = Sequence([1,2,3,4/5])
sage: v
[1, 2, 3, 4/5]
sage: type(v)
<class sage.structure.sequence.Sequence_generic >
sage: type(v[1])
<class sage.rings.rational.Rational >
sage: v.universe()
Rational Field
sage: v.is_immutable()
False
sage: v.set_immutable()
sage: v[0] = 3
Traceback (most recent call last):
...
ValueError: object is immutable; please change a copy instead.
Sequences derive from lists and can be used anywhere a list can be used:
sage: v = Sequence([1,2,3,4/5])
sage: isinstance(v, list)
(continues on next page)
As another example, basis for vector spaces are immutable sequences, since it’s important that you don’t change them.
6.6 Dictionaries
A dictionary (also sometimes called an associative array) is a mapping from ‘hashable’ objects (e.g., strings, numbers,
and tuples of such; see the Python documentation http://docs.python.org/tut/node7.html and http://docs.python.org/lib/
typesmapping.html for details) to arbitrary objects.
sage: d = {1:5, sage :17, ZZ:GF(7)}
sage: type(d)
<... dict >
sage: list(d.keys())
[1, sage , Integer Ring]
(continues on next page)
The third key illustrates that the indexes of a dictionary can be complicated, e.g., the ring of integers.
You can turn the above dictionary into a list with the same data:
sage: list(d.items())
[(1, 5), ( sage , 17), (Integer Ring, Finite Field of size 7)]
6.7 Sets
Python has a built-in set type. The main feature it offers is very fast lookup of whether an element is in the set or not,
along with standard set-theoretic operations.
Sage also has its own set type that is (in some cases) implemented using the built-in Python set type, but has a little bit of
extra Sage-related functionality. Create a Sage set using Set(...). For example,
sage: X = Set([1,19, a ]); Y = Set([1,1,1, 2/3])
sage: X # random sort order
{ a , 1, 19}
sage: X == Set([ a , 1, 1, 19])
True
sage: Y
{1, 2/3}
sage: X.intersection(Y)
{1}
sage: print(latex(Y))
\left\{1, \frac{2}{3}\right\}
sage: Set(ZZ)
Set of elements of Integer Ring
6.8 Iterators
Iterators are a recent addition to Python that are particularly useful in mathematics applications. Here are several examples;
see [PyT] for more details. We make an iterator over the squares of the nonnegative integers up to 10000000.
sage: v = (n^2 for n in range(10000000))
sage: next(v)
0
sage: next(v)
1
sage: next(v)
4
We create an iterate over the primes of the form 4𝑝 + 1 with 𝑝 also prime, and look at the first few values.
sage: w = (4*p + 1 for p in Primes() if is_prime(4*p+1))
sage: w # in the next line, 0xb0853d6c is a random 0x number
<generator object at 0xb0853d6c>
sage: next(w)
13
sage: next(w)
29
sage: next(w)
53
Certain rings, e.g., finite fields and the integers have iterators associated to them:
Note the colon at the end of the for statement (there is no “do” or “od” as in GAP or Maple), and the indentation before
the “body” of the loop, namely print(i). This indentation is important. In Sage, the indentation is automatically put in
for you when you hit enter after a “:”, as illustrated below.
The symbol = is used for assignment. The symbol == is used to check for equality:
Keep in mind how indentation determines the block structure for if, for, and while statements:
sage: legendre(2,7)
(continues on next page)
>>> legendre(Integer(2),Integer(7))
1
>>> legendre(Integer(3),Integer(7))
-1
Of course this is not an efficient implementation of the Legendre symbol! It is meant to illustrate various aspects of
Python/Sage programming. The function {kronecker}, which comes with Sage, computes the Legendre symbol efficiently
via a C-library call to PARI.
Finally, we note that comparisons, such as ==, !=, <=, >=, >, <, between numbers will automatically convert both numbers
into the same type if possible:
True
True
sage: x < x + 1
x < x + 1
sage: bool(x < x + 1)
True
When comparing objects of different types in Sage, in most cases Sage tries to find a canonical coercion of both objects
to a common parent (see Parents, Conversion and Coercion for more details). If successful, the comparison is performed
between the coerced objects; if not successful, the objects are considered not equal. For testing whether two variables
reference the same object use is. As we see in this example, the Python int 1 is unique, but the Sage Integer 1 is not:
sage: 1 is 2/2
False
sage: 1 is 1
False
sage: 1 == 2/2
True
In the following two lines, the first equality is False because there is no canonical morphism → F5 , hence no canonical
way to compare the 1 in F5 to the 1 ∈ . In contrast, there is a canonical map → F5 , hence the second comparison is
True. Note also that the order doesn’t matter.
False
False
>>> GF(Integer(5))(Integer(1)) == ZZ(Integer(1)); ZZ(Integer(1)) ==␣
˓→GF(Integer(5))(Integer(1))
True
True
>>> ZZ(Integer(1)) == QQ(Integer(1))
True
WARNING: Comparison in Sage is more restrictive than in Magma, which declares the 1 ∈ F5 equal to 1 ∈ .
6.10 Profiling
“Premature optimization is the root of all evil.” - Donald Knuth
Section author: Martin Albrecht <[email protected]>
Sometimes it is useful to check for bottlenecks in code to understand which parts take the most computational time; this
can give a good idea of which parts to optimize. Python and therefore Sage offers several profiling–as this process is
called–options.
The simplest to use is the prun command in the interactive shell. It returns a summary describing which functions took
how much computational time. To profile (the currently slow! - as of version 1.0) matrix multiplication over finite fields,
for example, do:
Here ncalls is the number of calls, tottime is the total time spent in the given function (and excluding time made
in calls to sub-functions), percall is the quotient of tottime divided by ncalls. cumtime is the total time spent
in this and all sub-functions (i.e., from invocation until exit), percall is the quotient of cumtime divided by primitive
calls, and filename:lineno(function) provides the respective data of each function. The rule of thumb here is:
The higher the function in that listing, the more expensive it is. Thus it is more interesting for optimization.
As usual, prun? provides details on how to use the profiler and understand the output.
The profiling data may be written to an object as well to allow closer examination:
Note: entering stats = prun -r A\*A displays a syntax error message because prun is an IPython shell command,
not a regular function.
For a nice graphical representation of profiling data, you can use the hotshot profiler, a small script called hotshot2ca-
chetree and the program kcachegrind (Unix only). The same example with the hotshot profiler:
sage: prof.run("A*A")
<hotshot.Profile instance at 0x414c11ec>
sage: prof.close()
This results in a file pythongrind.prof in the current working directory. It can now be converted to the cachegrind
format for visualization.
On a system shell, type
The output file cachegrind.out.42 can now be examined with kcachegrind. Please note that the naming convention
cachegrind.out.XX needs to be obeyed.
SEVEN
USING SAGETEX
The SageTeX package allows you to embed the results of Sage computations into a LaTeX document. To use it, you will
need to “install” it first (see Make SageTeX known to TeX).
7.1 An example
Here is a very brief example of using SageTeX. The full documentation can be found in SAGE_ROOT/venv/share/
doc/sagetex, where SAGE_ROOT is the directory where your Sage installation is located. That directory contains the
documentation and an example file. See SAGE_ROOT/venv/share/texmf/tex/latex/sagetex for some possibly
useful Python scripts.
To see how SageTeX works, follow the directions for installing SageTeX (in Make SageTeX known to TeX) and copy the
following text into a file named, say, st_example.tex:
Exclamation-Triangle Warning
The text below will have several errors about unknown control sequences if you are viewing this in the “live” help.
Use the static version to see the correct text.
\documentclass{article}
\usepackage{sagetex}
\begin{document}
Using Sage\TeX, one can use Sage to compute things and put them into
your \LaTeX{} document. For example, there are
$\sage{number_of_partitions(1269)}$ integer partitions of $1269$.
You don t need to compute the number yourself, or even cut and paste
it from somewhere.
\begin{sageblock}
f(x) = exp(x) * sin(2*x)
\end{sageblock}
\[
\frac{\mathrm{d}^{2}}{\mathrm{d}x^{2}} \sage{f(x)} =
(continues on next page)
145
Tutorial, Release 10.6
\end{document}
Run LaTeX on st_example.tex as usual. Note that LaTeX will have some complaints, which will include:
Notice that, in addition to the usual collection of files produced by LaTeX, there is a file called st_example.sagetex.
sage. That is a Sage script produced when you run LaTeX on st_example.tex. The warning message told you to run
Sage on st_example.sagetex.sage, so take its advice and do that. It will tell you to run LaTeX on st_example.
tex again, but before you do that, notice that a new file has been created: st_example.sagetex.sout. That file
contains the results of Sage’s computations, in a format that LaTeX can use to insert into your text. A new directory
containing an EPS file of your plot has also been created. Run LaTeX again and you’ll see that everything that Sage
computed and plotted is now included in your document.
The different macros used above should be pretty easy to understand. A sageblock environment typesets your code
verbatim and also executes the code when you run Sage. When you do \sage{foo}, the result put into your document
is whatever you get from running latex(foo) inside Sage. Plot commands are a bit more complicated, but in their
simplest form, \sageplot{foo} inserts the image you get from doing foo.save( filename.eps ).
In general, the mantra is:
• run LaTeX on your .tex file;
• run Sage on the generated .sage file;
• run LaTeX again.
You can omit running Sage if you haven’t changed around any Sage commands in your document.
There’s a lot more to SageTeX, and since both Sage and LaTeX are complex, powerful tools, it’s a good idea to read the
documentation for SageTeX, which is in SAGE_ROOT/venv/share/doc/sagetex.
• The first and simplest way is simply to copy sagetex.sty into the same directory as your LaTeX document.
Since the current directory is always searched when typesetting a document, this will always work.
There are a couple small problems with this, however: the first is that you will end up with many unnecessary copies
of sagetex.sty scattered around your computer. The second and more serious problem is that if you upgrade
Sage and get a new version of SageTeX, the Python code and LaTeX code for SageTeX may no longer match,
causing errors.
• The second way is to use the TEXMFLOCAL environment variable. If you are using the bash shell, you can do
$ export TEXMFLOCAL=SAGE_ROOT/venv/share/texmf
$ mktexlsr # update kpathsea ls-R databases
where SAGE_ROOT is the location of your Sage installation. Thereafter, TeX and friends will find the SageTeX
style file. If you want to make this change persistent, you can add the 1st of the above lines to your .bashrc file.
If you are using a different shell, you may have to modify the above command to make the environment variable
known; see your shell’s documentation for how to do that.
If you ever move your Sage installation, or install a new version into a new directory, you’ll need to update the
above command to reflect the new value of SAGE_ROOT.
• The third (and best) way to make TeX aware of sagetex.sty is to copy that file into a convenient place in your
home directory. In most TeX distributions, the texmf directory in your home directory is automatically searched
for packages. To find out exactly what this directory is, do the following on the command line:
$ kpsewhich -var-value=TEXMFHOME
which will print out a directory, such as /home/drake/texmf or /Users/drake/Library/texmf. Copy the
tex/ directory from SAGE_ROOT/venv/share/texmf/ into your home texmf directory with a command like
$ cp -R SAGE_ROOT/venv/share/texmf/tex TEXMFHOME
where SAGE_ROOT is, as usual, replaced with the location of your Sage installation and TEXMFHOME is the result of
the kpsewhich command above.
If you upgrade Sage and discover that SageTeX no longer works, you can simply repeat these steps and the Sage
and TeX parts of SageTeX will again be synchronized.
• For installation on a multiuser system, you just modify the above instructions appropriately to copy sagetex.sty
into a systemwide TeX directory. Instead of the directory TEXMFHOME, probably the best choice is to use the result
of
$ kpsewhich -var-value=TEXMFLOCAL
which will likely produce something like /usr/local/share/texmf. Copy the tex directory as above into the
TEXMFLOCAL directory. Now you need to update TeX’s database of packages, which you can do simply by running
$ texhash TEXMFLOCAL
as root, replacing TEXMFLOCAL appropriately. Now all users of your system will have access to the LaTeX package,
and if they can also run Sage, they will be able to use SageTeX.
Exclamation-Triangle Warning
it’s very important that the file sagetex.sty that LaTeX uses when typesetting your document match the version
of SageTeX that Sage is using. If you upgrade your Sage installation, you really should delete all the old versions of
sagetex.sty floating around.
Because of this problem, we recommend copying the SageTeX files into your home directory’s texmf directory (the
third method above). Then there is only one thing you need to do (copy a directory) when you upgrade Sage to insure
that SageTeX will work properly.
EIGHT
AFTERWORD
>>> 2^8
10
(continues on next page)
149
Tutorial, Release 10.6
This use of ^ may appear odd, and it is inefficient for pure math research, since the “exclusive or” function is rarely
used. For convenience, Sage pre-parses all command lines before passing them to Python, replacing instances of
^ that are not in strings with **:
sage: 2^8
256
sage: 3^2
9
sage: "3^2"
3^2
The bitwise xor operator in Sage is ^^. This also works for the inplace operator ^^=:
sage: 3^^2
1
sage: a = 2
sage: a ^^= 8
sage: a
10
• Integer division: The Python expression 2/3 does not behave the way mathematicians might expect: 2/3 returns
the floating point number 0.6666.... Note that // is the Euclidean division and 2//3 returns 0.
We deal with this in the Sage interpreter, by wrapping integer literals in Integer( ) and making division a
constructor for rational numbers. For example:
sage: 2/3
2/3
sage: (2/3).parent()
Rational Field
sage: 2//3
0
• Long integers: Python has native support for arbitrary precision integers, in addition to C-int’s. These are signif-
icantly slower than what GMP provides. Sage implements arbitrary precision integers using the GMP C-library.
Rather than modifying the Python interpreter (as some people have done for internal projects), we use the Python language
exactly as is, and write a pre-parser for IPython so that the command line behavior of IPython is what a mathematician
expects. This means any existing Python code can be used in Sage. However, one must still obey the standard Python
rules when writing packages that will be imported into Sage.
(To install a Python library, for example that you have found on the Internet, follow the directions, but run sage -python
instead of python. Very often this means typing sage -python setup.py install.)
in your bibliography (replacing 8.7 with the version of Sage you used). Moreover, please attempt to track down what
components of Sage are used for your computation, e.g., PARI?, GAP?, Singular? Maxima? and also cite those systems.
If you are in doubt about what software your computation uses, feel free to ask on the sage-devel Google group. See
Univariate Polynomials for further discussion of this point.
If you happen to have just read straight through this tutorial, and have some sense of how long it took you, please let us
know on the sage-devel Google group.
Have fun with Sage!
NINE
APPENDIX
Operators Description
or boolean or
and boolean and
not boolean not
in, not in membership
is, is not identity test
>, <=, >, >=, ==, != comparison
+, - addition, subtraction
*, /, % multiplication, division, remainder
**, ^ exponentiation
Therefore, to compute 3^2*4 + 2%5, Sage brackets the computation this way: ((3^2)*4) + (2%5). Thus, first
compute 3^2, which is 9, then compute both (3^2)*4 and 2%5, and finally add these.
153
Tutorial, Release 10.6
TEN
BIBLIOGRAPHY
155
Tutorial, Release 10.6
ELEVEN
• genindex
• search
157
Tutorial, Release 10.6
159
Tutorial, Release 10.6
160 Bibliography
INDEX
E
EDITOR, 97
environment variable
EDITOR, 97
161