Segre class formula needs projectiveBundle', not projectiveBundle -- undocumented
@mikestillman is already working on this.
Since Aug 13, 2015.
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
The following example/bug report was reported by Paolo Aluffi. I need to decide still what the problem is. I'm making it an issue so I don't forget to look into it.
If F is a vector bundle over a base X, Y = P(F) its projectivization, and K is the first
Chern class of the tautological O_Y(1), then the push-forward of (1 + K + K^2 + ... )
should equal the Segre class of F. (This is the formula at the bottom of p.47 in
Fulton's book.)
I see that `segre' in Schubert2 differs from Fulton's convention, but this formula should
still hold up to signs. For example:
i1 : load("Schubert2.m2")
i2 : X = projectiveBundle 4;
i3 : F = OO_X(2) ++ OO_X(3);
i4 : segre F
o4 = 1 + 5H + 19H + 65H + 211H
2,1 2,2 2,3 2,4
i5 : Y = projectiveBundle F;
i6 : p = Y.StructureMap;
i7 : K = chern(1,OO_Y(1));
i8 : p_*(1+K+K^2+K^3+K^4+K^5+K^6)
o8 = 1 + 5H + 19H + 65H + 211H
2,1 2,2 2,3 2,4
o4 and o8 agree, as expected. I am actually a little confused by the signs, since the
different convention should lead to discrepancies, but never mind. What worries me more
is the same computation, but performed on a rank-3 bundle (I am using this example
because it matches the example given on
http://www.math.uiuc.edu/Macaulay2/doc/Macaulay2-1.6/share/doc/Macaulay2/Schubert2/html/_projective__Bundle.html):
i1 : load("Schubert2.m2")
i2 : X = projectiveBundle 4;
i3 : F = OO_X(2) ++ OO_X(3) ++ OO_X(4);
i4 : segre F
o4 = 1 + 9H + 55H + 285H + 1351H
2,1 2,2 2,3 2,4
i5 : Y = projectiveBundle F;
i6 : p = Y.StructureMap;
i7 : K = chern(1,OO_Y(1));
i8 : p_*(1+K+K^2+K^3+K^4+K^5+K^6)
o8 = 1 + 18H + 217H + 2190H + 19981H
2,1 2,2 2,3 2,4
I really am not sure what is going on here. Shouldn't o4 and o8 agree (maybe up to signs),
by Fulton's formula, just as they do in the rank-2 case? (I haven't tried this on the older
Schubert maple package, I don't have easy access to it.)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.