Defining Number Fields -- part 2
William Stein
Jan 11, 2016
Part 2: Relative number fields
Frequently number fields are naturally defined as a tower (or as a compositum of other number fields). First let's consider an extension of number fields. Things work just like before, but you define a second polynomial ring over the first number field.
Let's first define , then .
Elements of will automatically convert into elements of . (This is actually really general and complicated, under the hood, and took years of work to do in the right generality. Sage is the biggest and most sophisticated implementation of this sort of "coercion model" functionality.)
Exercise right now: Construct as an extension of .
Inspiration: Magma
The user interface for making number fields in Sage is motivated by how things work in Magma.
See, e.g., https://magma.maths.usyd.edu.au/magma/handbook/number_fields
and here is an example:
Compositums
You can also make number fields as compositums of existing number fields:
Composite fields outputs a list because there can be more than one composite of fields, in case there are multiple embeddings of the field into .
Exercise right now: explicitly compute an example in which K.composite_fields(M)
is a list of length bigger than 1?
You can also just give several polynomials to construct a choice of compositum:
Other things to think about next time:
Speed of arithmetic in absolute fields
Finding an optimized representation for a number field
Speed of arithmetic in relative fields
Going from a relative extention to an absolute extension.