On Sunday, July 21, 2013 5:14:21 PM UTC-7, Volker Braun wrote: > > There is already an affine space class (as affine scheme). Whats wrong > with using that as ambient space? > > Thanks for pointing that out. I had chosen AffSpace for the name of the class I need initially because the name AffineSpace is already used, but someone changed it on trac, and I forgot about the conflict. The current affine space is designed for completely different purposes. It has very few of the methods I need and lots that I don't. So I will need to think of a better name. Any ideas?
> sage: AffineSpace(2,QQ) > Affine Space of dimension 2 over Rational Field > > Whats your plan with parent/element relations? It seems Hyperplane should > be an element with HyperplaneArrangement the parent. > > At the moment, I just have Hyperplane as a class deriving from AffineSpace (my version of AffineSpace, that is, which I will change, as noted above), and HyperplaneArrangement deriving from object. Can you spell out your idea a bit more? > Do you have a repository / trac ticket with the current code? > > Yes, it is trac #14789. Warning: in the next few days I will post a substantial change to that posting. To get an idea, though, you might download hyperplane.sage, posted there. > On Sunday, July 21, 2013 5:54:25 PM UTC-4, davidp wrote: >> >> I have created three classes: AffineSpace, Hyperplane (inheriting from >> AffineSpace), and HyperplaneArrangement. The methods in >> HyperplaneArrangement that I have defined so far are (where 'a', below, is >> a hyperplane arrangement): >> >> a.ambient_space a.num_bounded_regions >> a.base_field a.num_hyperplanes >> a.bounded_regions a.num_regions >> a.change_base_field a.plot >> a.characteristic_polynomial a.poincare_polynomial >> a.cone a.polyhedron >> a.deletion a.rank >> a.dim a.region_containing_point >> a.doubly_indexed_whitney_number a.regions >> a.essentialization a.repr_point >> a.face_vector a.restriction >> a.has_good_reduction a.show >> a.hyperplanes a.sign_vector >> a.intersection_poset a.unbounded_regions >> a.is_central a.union >> a.is_essential a.whitney_data >> a.is_linear a.whitney_number >> a.is_separating_hyperplane >> >> Please let me know if there are other things you would like to see >> included. >> >> Thanks, >> Dave >> >> On Sunday, July 21, 2013 2:34:16 PM UTC-7, Volker Braun wrote: >>> >>> "center" is not a function but a method of Polyhedron_base. I suggest >>> you read up on object-oriented programming and Python if that that doesn't >>> answer your question. >>> >>> I'm definitely interested in hyperplane arrangements, though. Do you >>> have a particular data structure in mind or is your plan to just keep a >>> collection of hyperplanes? >>> >>> >>> >>> On Sunday, July 21, 2013 3:58:24 PM UTC-4, davidp wrote: >>>> >>>> I am working on a Sage package for hyperplane arrangements. In my >>>> file hyperplane_arrangement.py, >>>> I would like to use the function 'center' >>>> from sage/geometry/polyhedron/basepy. (It finds the center of a >>>> polyhedron.) >>>> I have tried to import it with >>>> >>>> import from sage.geometry.polyhedron.base import center >>>> >>>> but that crashes Sage. I have tried several variations on this theme. >>>> Could someone please tell me the magic words? >>>> >>>> Thanks, >>>> Dave >>>> >>> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
