Hi Andrey,
I agree that the reflexive case is the most interesting, I just don't
understand where you need that in the FanoToricVariety code right now.
If we can relax restrictions without any cost then we should allow the
more general, right? On the other hand, if it would make the code more
complicated then screw it...
On May 19, 4:03 am, Andrey Novoseltsev <novos...@gmail.com> wrote:
> [...] we can add "PCR" in
> the beginning or the end (corresponding to PartialCrepantResolution).
Batyrev already defined the abbreviation
MPCP resolution =
(maximal projective crepant partial) resolution =
maximal subdivision of polyhedron
I think you want to do everything except the "maximal" (and perhaps
except the "projective", I don't see why you need to enforce that in
the Sage class), so how about PCPR or CPR? CPRFanoToricVariety_field?
> [...] How
> about also latexing them with subscripts? Like "(1,2)_{N}"?
Nice!
> One way or another they will have to define variables containing the
> lattices, but that's pretty much unavoidable, I don't think it is a
> good idea to put names like "N" and "M" into the global name space.
In fact, "N" is already in the global workspace :-)
sage: N(1/2)
0.500000000000000
Are you implementing the ToricLattice soon? Clearly this should be
done first...
Best wishes,
Volker
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
