#15560: Add methods to rigged configurations
-------------------------------------+-------------------------------------
Reporter: tscrim | Owner: sage-combinat
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.3
Component: combinatorics | Resolution:
Keywords: rigged | Merged in:
configurations | Reviewers: Anne Schilling
Authors: Travis Scrimshaw | Work issues:
Report Upstream: N/A | Commit:
Branch: | 2874083b12a083c3d644860e09079c1136915622
public/combinat/rigged_configurations/methods-15560| Stopgaps:
Dependencies: #13872 #15882 |
-------------------------------------+-------------------------------------
Comment (by aschilling):
Replying to [comment:24 tscrim]:
> Replying to [comment:22 aschilling]:
> > * The documentation of right_split has a ` missing. Please run the
documentation to see that it actually compiles!
>
> I couldn't find this and the documentation built without an issue and
looks okay to me (although there was a missing 'u').
There is a ` missing in
{{{
+ Let `\ast` denote the :meth:`Lusztig involution<lusztig_involution>`,
+ and `\mathrm{ls}` as the :meth:`left splitting map<left_split>`.
+ The right splitting map is defined as
+ \mathrm{rs} := \ast \circ \mathrm{ls} \circ \ast`.
}}}
> > * Please add the map `\theta` to rigged configuration and compare to
lusztig_involution.
>
> Added under the name `complement`. In general, it will be different than
`lusztig_involution`, which fixes each classical component, whereas
`\theta` fixes the classical structure but permutes the classical
components. Or did you mean you wanted me to add a doctest showing this?
Under `\bar \Phi` the map `\star` (which I guess is what you call
lusztig_involution) intertwines with `\theta`. It would be good to add a
check like that.
> > * Please add tests and more explanations what `build_graph` does.
Explain which graph it is computing. Also the following fails:
>
> This was due to before, the element constructor always preserved the
vacancy numbers and now it recomputes it unless explicitly stated. Fixed
with added tests. I expanded the documentation in
`to_tensor_..._tableaux()` as well.
Even though it is stated in the documentation, that `build_graph` is an
optional
parameter, it does not seem to take this input:
{{{
sage: rc = RC(partition_list=[[1],[1],[1],[1]])
sage:
rc.to_tensor_product_of_kirillov_reshetikhin_crystals(build_graph=True)
---------------------------------------------------------------------------
TypeError Traceback (most recent call
last)
<ipython-input-8-702cb808a701> in <module>()
----> 1
rc.to_tensor_product_of_kirillov_reshetikhin_crystals(build_graph=True)
TypeError: to_tensor_product_of_kirillov_reshetikhin_crystals() got an
unexpected keyword argument 'build_graph'
}}}
What is the difference between `build_graph` and `display_steps`?
Anne
--
Ticket URL: <http://trac.sagemath.org/ticket/15560#comment:25>
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.
