Specialization to ordinary table#298
Specialization to ordinary table#298SoongNoonien wants to merge 2 commits intooscar-system:masterfrom
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #298 +/- ##
==========================================
- Coverage 95.10% 89.87% -5.24%
==========================================
Files 14 15 +1
Lines 961 1017 +56
==========================================
Hits 914 914
- Misses 47 103 +56 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
You can also check the table by asking... OSCAR ;-) Also note that the first column should have only positive integer entries (those should be the degrees of the corresponding representations). So indeed something is wrong |
Of course I should have thought of that...
Yes, but that's just a convention on the order of the conjugacy classes. My first goal is to obtain a table which is correct up to permutation of columns and rows. I'm not even sure if we can say beforehand which combination of class parameters corresponds to the trivial class. |
|
Ok, I found the problem. Now the table looks like this: |
|
Yes, this way it works "in principle", provided the character parameters and class parameters are correctly described. But it quickly becomes non-practical because for larger tables and/or parameters you produce far too many rows and columns which are then collapsed afterwords. With newly created tables I will later provide additional information on the parameter sets, such that each class and each irreducible character is described by a unique parameter specialization. |
This is a first and very crude hack to get an ordinary character table from a generic one. Apparently I'm doing something wrong or the parameter specifications of$\mathrm{GL}(2,3)$ :
GL2are incorrect. This is what I get forThere are two additional rows and columns as can be verified here.