Skip to content

Only five smooth projective toric Fano surfaces

The past few weeks I’ve been dabbling in some toric geometry, and the following result in toric geometry puzzled me when I first read it:

The only smooth projective toric Fano surfaces are \mathbb{P}^2,\mathbb{P}^1\times\mathbb{P}^1,\mathrm{Bl}_1\mathbb{P}^2,\mathrm{Bl}_2\mathbb{P}^2,\mathrm{Bl}_3\mathbb{P}^2.

If you are as ignorant about toric geometry as I am (i.e. you’ve looked at Cox–Little–Schenck’s marvellous book but not much more than that) this statement might be a bit puzzling. Because as you might know: the del Pezzo surfaces (a shorthand term for smooth projective Fano varieties of dimension 2) are classified, and these are exactly the surfaces \mathbb{P}^2,\mathbb{P}^1\times\mathbb{P}^1,\mathrm{Bl}_1\mathbb{P}^2,\ldots,\mathrm{Bl}_9\mathbb{P}^2, where the points are chosen sufficiently general.

So why did this fact puzzle me? Well: there is a perfectly good notion of blowing up a toric variety. Hence why do we not get \mathrm{Bl}_4\mathbb{P}^2 as a toric del Pezzo surface? Surely it is del Pezzo, and via a blow-up we can realise it as a toric surface, right?!

No! Think about this for a while. If you don’t know this: a toric blow-up is not an arbitrary blow-up, it is a blow-up in a torus-invariant point. This is really the crucial point.

In the case of \mathbb{P}^2 there are 3 torus-invariant divisors, and they form a triangle of \mathbb{P}^1‘s in \mathbb{P}^2. If you do a toric blow-up you blow up in one of the intersections. You get a square of \mathbb{P}^1‘s in \mathrm{Bl}_1\mathbb{P}^2, hence there are now 4 intersections to choose from for your toric blow-up, but only two of them come from \mathbb{P}^2. If you blow-up one of those two original points it was as if you performed a simultaneous blow-up, to get \mathrm{Bl}_2\mathbb{P}^2, but if you pick one of the other 2 points, which lie on the exceptional divisor, you are getting something different.

Hence, this is why you cannot get \mathrm{Bl}_4\mathbb{P}^2 as a toric del Pezzo surface: it is not toric! It is all completely trivial, but it was a nice thing to realise for me, and what is better than sharing your ignorance with the world?

What are Chern classes?

This year we are continuing ANAGRAMS, the local student seminar (previously announced on my weblog). The first series of lectures we are starting with will be about Chern classes, and I will try to blog more regularly about the things we discuss. Hence in this post I will outline the motivation and interpretation of Chern classes (the gory details will not be discussed here).

Characteristic classes

People like vector bundles. They are easy-to-understand coherent sheaves, we have some obvious candidates (tangent and cotangent bundles, line bundles) and there are many interesting constructions for them (duals, direct sums, tensor products, symmetric products, exterior products, …), but nevertheless they carry significant amounts of geometric information. Even if you don’t like vector bundles as such, some seemingly totally non-vector bundleish questions such as “how many lines lie on a cubic surface” can be rephrased in terms of vector bundles and then we can actually solve them!

So what is there to know about vector bundles? We know that locally they are just copies of the structure sheaf, so the main question to ask about your vector bundle is whether it is globally (non)trivial. Continuing this train of thought one should ask, whenever a vector bundle is non-trivial, whether we can say in which sense it is non-trivial. This admittedly vague statement will be made more precise (but not too precise) in the next section.

So how can we quantify information about vector bundles? Using characteristic classes! So what are they? Depending on which context you are working in (differential geometry, complex geometry, algebraic geometry) you have different cohomology theories associated to the space on which you are considering vector bundles. There is Betti cohomology, the Chow ring, de Rham cohomology, … The characteristic class of your vector bundle is then an element in this cohomology theory, which then measures something about the vector bundle: how non-trivial it is, and in which sense it is non-trivial. If you are lucky then you can interpret the characteristic class of your bundle, and draw an interesting conclusion.

To summarise: pick your favourite cohomology ring associated to your variety, this is a graded ring. Then the characteristic classes of your vector bundle (there are possibly multiple non-zero classes) all lie in one particular piece of this graded ring.

Chern classes

Let X be a smooth projective variety over some algebraically closed field (one can get by with much less). If one takes the Chow ring \mathrm{CH}^\bullet(X) for the receptacle of this characteristic classes mumbo-jumbo one obtains Chern classes. The Chow ring is defined in terms of cycles on X, and hence our Chern classes describe something in terms of the subvarieties: \mathrm{c}_i(\mathcal{F}) is an element of \mathrm{CH}^i(X), hence defines some cycle of codimension i.

One can interpret these Chern classes in terms of degeneracy loci. Recall that we were trying to measure in which sense a vector bundle is non-trivial, and for ease of statement we will assume that our vector bundle is globally generated. If we denote r=\mathrm{rk}(\mathcal{F}), then for any k=1,\dotsc,r we can consider global sections s_1,\dotsc,s_{r-k+1}. If we evaluate these in a point we get r-k+1 vectors of length r, hence we can ask whether these are linearly (in)dependent. The degeneracy locus of our set of global sections is then exactly the set of points in which the evaluations become linearly dependent, hence they degenerate.

Of course one has to choose these sections sufficiently generally in order to make the codimension of the degeneracy locus correct, but one can prove that if the codimension is correct and the vector bundle is globally generated, then the degeneracy locus is independent of the choice! This can then be one way of defining the Chern classes of a vector bundle.

Example

During the series of lectures I intend to have people discuss some “numbers you should recognise”. Hence you have to explain why e.g. the number 2875 is interesting from the viewpoint of an enumerative geometer. As the toy example to introduce vector bundles in enumerative geometry I will do the number 27, which is as everyone should know, the number of lines on a smooth cubic surface.

How can we phrase the question

How many lines lie on a cubic surface?

in terms of vector bundles, and therefore apply Chern class machinery to try and solve it? The Grassmannian G=\mathrm{Grass}(2,4) parametrising lines in \mathbb{P}^3 or planes in \mathbb{A}^4 is a smooth projective variety (more specifically: it is a quadric hypersurface in \mathbb{P}^5) that comes equipped with a tautological bundle \mathcal{F} (not to be confused with the canonical bundle, which is the highest exterior power of the cotangent bundle).

This tautological bundle has rank 2, and is a subbundle of the trivial vector bundle \mathcal{O}_G^{\oplus 4}, obtained by taking as the fiber in each point the 2-dimensional subspace (of the 4-dimensional vector space) that corresponds to the point of the Grassmannian. The inclusion \mathcal{F}\hookrightarrow\mathcal{O}_G^{\oplus 4} dualises to a surjection \mathcal{O}_G^{\oplus 4,\vee}\twoheadrightarrow\mathcal{F}^\vee, which corresponds to restricting a linear function on \mathbb{P}^3 to the line. Taking dth symmetric powers of this surjection corresponds to restricting a homogeneous degree d polynomial on \mathbb{P}^3 to the line.

Now let X be the hypersurface defined by a cubic, to this corresponds a f, a section of \mathrm{Sym}^3(\mathcal{O}_G^{\oplus 4}) which is mapped to \mathrm{Sym}^3(\mathcal{F}^\vee) by the symmetric cube of the map from the previous paragraph. Hence we get a global section of the symmetric cube of our tautological bundle, which describes exactly the set of lines in \mathbb{P}^3 on which f vanishes!

Now, assuming this set is finite, we can apply some intersection theory machinery (see section 14.1 of Fulton’s bible) which says that inside the correct Chow group the zero locus of our global section is described by the top Chern class of our vector bundle! Hence it is completely determined in terms of Chern classes, and if we can compute this particular Chern class (and its degree) we know exactly how big this set is. To see why this is the case: observe that

\mathrm{rk}(\mathrm{Sym}^3(\mathcal{F}^\vee))={2+3-1 \choose 3}=4=\mathrm{dim}(G),

hence the top Chern class of this vector bundle lands precisely where it should land.

To determine this top Chern class \mathrm{c}_4(\mathrm{Sym}^3\mathcal{F}^\vee) one has to study how Chern classes behave with respect to symmetric powers and express it in terms of \mathcal{F}^\vee only, which gives

\mathrm{c}_4(\mathrm{Sym}^3\mathcal{F}^\vee)=9\mathrm{c}_2(\mathcal{F}^\vee)^2+18\mathrm{c}_1(\mathcal{F}^\vee)^2\mathrm{c}_2(\mathcal{F}^\vee).

Now we have to interpret the values in the right-hand side, which can either be done using general Schubert calculus on a Grassmannian variety (the moduli interpretation of these varieties gives strong tools to compute things on these varieties), or in this small case one can resort to explicit interpretations. Either way, the products turn out to be 1 in both cases, hence there are 27 lines on a cubic surface.

This is certainly not the only thing Chern classes are good for, but I think it’s a nice example of showing how constructions with vector bundles are reflected by operations on Chern classes, and how enumerative geometry can be rephrased in terms of intersection theory.

Why homotopy colimits in triangulated categories are defined the way they are

This post is one big triviality. But I only realised now why homotopy colimits in triangulated categories are defined the way they are defined.

Just think of triangulated categories as a bit wonky abelian categories, and in (non-wonky) abelian categories a colimit can be constructed from having coproducts and coequalisers. In a triangulated category you don’t have coequalisers / cokernels, but cones play this role. Hence one takes a particular cone of a direct sum that simulates a coequaliser, and one is done.

Of course, everything dualises to homotopy limits.

Why did no-one tell me this?!

Each statement is to be interpreted under suitable conditions on the objects in sight, e.g. existence of direct sums etc. etc.

Comparison of topologies

Last year I made a graph comparing a bunch of Grothendieck topologies, and I had been toying with the idea of making an interactive web version of it. Two weeks ago Shane Kelly published a preprint Points in algebraic geometry, while Stefan Schroër tackled in a preprint that appeared on the same day the intriguingly hard case of Points in the fppf topology.

The article by Kelly contains a comparison graph, just like the one I made last year (mine emphasised the “usual” topologies more, and had less topologies), but also describes what type of rings act as stalks for this topology, and gave short definitions of each of the topologies in use. Hence I had all the data to make a complete comparison!

There is a very preliminary draft available. I’ll be away from the internet for 2 weeks, hence if you are looking for a summer programming project and feel like contributing, there is the GitHub repository. I want to:

  1. Improve the layout (I’m a horrible designer, as you can tell, and my SVG skills are rather sketchy).
  2. Add explanations on how to use the comparison graph.
  3. Fix all the TODOs, the code is riddled with them…
  4. Add more data (you don’t have to be a programmer for this): I am especially looking for improved comparison results, more topologies, … I know there is a fpuo and a l' topology out there. Are there more topologies in use?
  5. Add the canonical and extensive topology to the graph, and indicate these properties in the “passport” as well.
  6. I want a tighter integration with the Stacks project, preferably all the result that are used should turn up there, this requires both writing for the Stacks project and providing the functionality in the comparison graph.
  7. Right now everything is for \mathrm{Sch}/S, the category of separated schemes of finite type over S a separated noetherian scheme: I don’t know what goes wrong if we take a different category, hence
    • I would like to be able to switch between categories, and suitably update the comparison graph.
    • I have no clue regarding the actual results that should be there…

New feature for the Stacks project: slogans

Update from the Stacks project: there is a new feature, namely slogans. Johan de Jong has discussed this idea before, and right now they are implemented on the website *and* there is a nice web page (compatible with your smartphone, I hope) to suggest slogans. Moreover, there are numerous small bug fixes (and hopefully not too many new bugs).

Hence: first suggest slogans and then see them appear on the Stacks project website.

I would like to thank Johan and Grietje Commelin for providing an excellent place to stay during the programmingathon Johan (Commelin, having multiple Johans makes for confusing mail conversations) and I did. And special thanks to their 2.5 year old daughter Hannah for the great conversations one can have with toddlers during breaks :).

Notes on stratification of triangulated categories

The last week of June I attended a summer school on derived categories in Nantes. Really interesting summer school, and a truly brilliant city. During the long and boring train ride home I decided to TeX up my notes for Henning Krause‘s lecture series on stratification of triangulated categories. The result of that is now proofread and corrected (thanks Henning!), and can be found on my personal webpage (or his, or hopefully the summer school’s page soon).

New version of Hodge diamonds and Serre duality tables for complete intersections

Recall that a few months ago I wrote a tool to visualise / compute Serre duality and Hodge diamonds for complete intersections.

Using it yesterday I realised that I should beef it up a little, so I have:

  • added more numerical invariants in the case of surfaces, they are defined in terms of the Hodge diamond anyway but it saves me from miscomputing things (I should do it for more general varieties too, but at the moment I care only about surfaces)
  • improved the layout, no more incessant scrolling if you care about Hodge diamonds

The result still won’t win a medal for its visuals. If you have suggestions regarding layout or functionality, just contact me.

Follow

Get every new post delivered to your Inbox.

Join 26 other followers