Opened 10 years ago
Closed 9 years ago
#10696 closed defect (duplicate)
SymmetricGroup function doesn't seem to do arbitrary sets
Reported by: | arattan | Owned by: | sage-combinat |
---|---|---|---|
Priority: | minor | Milestone: | sage-duplicate/invalid/wontfix |
Component: | combinatorics | Keywords: | SymmetricGroup |
Cc: | jdemeyer | Merged in: | |
Authors: | Reviewers: | Mike Hansen | |
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description (last modified by )
The following doesn't seem right to me. I tried this on sage 4.5.3 and 4.6. My impression is that the SymmetricGroup? function can take a list of distinct integers X as an argument and give the symmetric group S_X. However, we can try the following.
sage: f=SymmetricGroup([1,2,4]) sage: for i in f: ....: print i ....: () (2,3) (1,2) (1,2,3) (1,3,2) (1,3) sage: f[3] (1,2,3) sage: f[3](4) 4 sage: f[3](3) 1 sage: f.set() (1, 2, 4)
Thus, it seems that f.set() returns the right support, but in fact the support for the group is 1,2,3. This suggests to me that S_X = S_{1,2,3}.
Change History (8)
comment:1 Changed 10 years ago by
- Description modified (diff)
comment:2 Changed 10 years ago by
comment:3 Changed 9 years ago by
- Description modified (diff)
comment:4 Changed 9 years ago by
- Cc jdemeyer added
This can indeed be closed:
sage: f=SymmetricGroup([1,2,4]) sage: for i in f: ....: print i ....: () (2,4) (1,2) (1,2,4) (1,4,2) (1,4) sage: f[3] (1,2,4) sage: f[3](4) 1 sage: f[3](3) 3 sage: f.set() /opt/sage/local/bin/sage-ipython:1: DeprecationWarning: (Since Sage Version 4.7.1) set is deprecated. Please use domain instead. #!/usr/bin/env python {1, 2, 4}
comment:5 Changed 9 years ago by
- Status changed from new to needs_review
Verified results that this can be closed.
comment:6 Changed 9 years ago by
- Status changed from needs_review to positive_review
comment:7 Changed 9 years ago by
- Milestone set to sage-duplicate/invalid/wontfix
- Reviewers set to Mike Hansen
To mark as ticket as needing to be closed, you should put the milestone to sage-duplicate/invalid/wontfix.
comment:8 Changed 9 years ago by
- Resolution set to duplicate
- Status changed from positive_review to closed
Note: See
TracTickets for help on using
tickets.
This should be fixed by #10335