-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Erroneous characters from orthogonality in C2 x SL(2,3) and SL(2,3) x: C2 #61
Comments
When limiting the search to two missing characters, incorrect results may occur for example in SL(2,3). FastGoat/FastGoat/DetailsGroupsUptoOrder32.txt Lines 4130 to 4147 in 835336c
This is because the equations used are only necessary conditions for determining irreducible characters basis from class functions, as <Xi,Xi> = 1. To ensure accuracy, additional conditions must be applied beforehand or a more robust validation of solutions should be conducted afterward. |
The symmetric and exterior characters appear to function as a validation method when they can undergo an isotypic decomposition. This is applicable for solutions to the orthogonality equations for missing characters of groups such as SL(2,3), C2 x SL(2,3), and SL(2,3) x: C2. Further testing is required for additional groups. |
The previous remark applies solely to SL(2,3) when determining missing characters. For the groups C2 x SL(2,3) and SL(2,3) x: C2, certain class functions that solve the system and yield integer decompositions for symmetric characters may not be valid. These solutions do not necessarily result in integer decompositions for representations in the GroupMatrixFormPart2.cs file. Occasionally, fortuitous ordering can yield satisfactory results for the previous cases. |
FastGoat/FastGoat/Examples/GroupMatrixFormPart2.cs
Lines 669 to 682 in b3bab8f
FastGoat/FastGoat/Examples/GroupMatrixFormPart2.cs
Lines 530 to 531 in b3bab8f
The characters resulting from solving orthogonality are erroneous and lead to an incorrect decomposition of the representation.
The text was updated successfully, but these errors were encountered: