#11400: Add PointCollection
---------------------------+------------------------------------------------
Reporter: novoselt | Owner: novoselt
Type: enhancement | Status: needs_info
Priority: major | Milestone: sage-4.7.1
Component: geometry | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author: Andrey Novoseltsev
Merged: | Dependencies:
---------------------------+------------------------------------------------
Comment(by novoselt):
I am a bit paranoid about adding yet another intermediate level... How
would it perform on really simple examples? One of the most important
cases for us are simplicial cones, so they should build and work as fast
as possible.
I also think that points should not link to collections since the same
point may belong to multiple collections (e.g. points of a face are also
points of the whole thing).
And a natural parent of points seems to be the space in which they live,
not the sequence in which they have happened to appear.
In a way this class already abstracts the way in which points are stored
and say, instead of acting by some transformation matrix on single points
or the matrix representation of a collection we may add direct action on
the collection itself with whatever internal implementation (that's
actually something that I was going to add but forgot). So if we use a
numpy array, then we can live without any kind of stored objects to
represent points and if someone really wants to access a single one -
`__getitem__` will construct a corresponding vector.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11400#comment:6>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
