#15536: Implement symplectic and orthogonal bases of Sym
-------------------------------------+-------------------------------------
       Reporter:  tscrim             |        Owner:  sage-combinat
           Type:  enhancement        |       Status:  needs_info
       Priority:  major              |    Milestone:  sage-6.10
      Component:  combinatorics      |   Resolution:
       Keywords:  days54, sym        |    Merged in:
        Authors:  Travis Scrimshaw   |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  public/combinat/sf/sp_orth         |  8e690e2a13b8c266f0d6a46c7c9b01a01aa48933
   Dependencies:  #17096             |     Stopgaps:
-------------------------------------+-------------------------------------
Changes (by tscrim):

 * commit:  cac1d88d687705fa90de0edac1b472f6e2d623b4 =>
     8e690e2a13b8c266f0d6a46c7c9b01a01aa48933
 * branch:  u/tscrim/sp_orth_broken => public/combinat/sf/sp_orth


Comment:

 However, I don't think that is the right solution. `:/` The check is
 reasonable and necessary.

 Granted, my current proposal is a major hack, but I don't think too many
 people will be creating many instances of Sym over various large finite
 fields (and there are more computationally intensive parts necessary for
 working with Sym). I'm tired of trying to deal with this here, so I just
 checked if the base ring was a field before any categories get created.

 There is also another issue with C3 in that I get a `KeyError` if I make
 this change:
 {{{#!diff
          cat = HopfAlgebras(self.base().base_ring())
          return [self.base().Realizations(),
                  cat.Commutative().WithBasis(),
 -                cat.Graded().Realizations()]
 +                cat.Commutative().Graded().Realizations()]
 }}}
 This is what it should be, but because everything commutative will come
 from the `cat.Commutative().WithBasis()`, I think we are okay for now.

 I really would like to push this ticket in and later reach in and fix the
 category-refinement/MRO/C3 issues on a separate ticket.
 ----
 New commits:
 
||[http://git.sagemath.org/sage.git/commit/?id=8263b10f2c00d58f2a8e09777c394ea51906b366
 8263b10]||{{{Merge branch 'develop' into public/combinat/sf/sp_orth}}}||
 
||[http://git.sagemath.org/sage.git/commit/?id=b151195bd18ba3c5526b36d6298f39ede0189fd4
 b151195]||{{{Merge branch 'develop' into public/combinat/sf/sp_orth}}}||
 
||[http://git.sagemath.org/sage.git/commit/?id=8e690e2a13b8c266f0d6a46c7c9b01a01aa48933
 8e690e2]||{{{Some hacks and FIXMEs.}}}||

--
Ticket URL: <http://trac.sagemath.org/ticket/15536#comment:45>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to