Skip to content
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

problem with generic code for elements in pc groups #5638

Open
ThomasBreuer opened this issue Feb 14, 2024 · 0 comments
Open

problem with generic code for elements in pc groups #5638

ThomasBreuer opened this issue Feb 14, 2024 · 0 comments
Labels
kind: bug: unexpected error Issues describing bugs in which computation unexpectedly encounters an error, and PRs fixing them

Comments

@ThomasBreuer
Copy link
Contributor

The following happens in GAP 4.12.2 as well as in the current master branch.

gap> p:= NextPrimeInt( 134217688 );
134217689
gap> G:= CyclicGroup( p );
<pc group of size 134217689 with 1 generator>
gap> ConjugacyClassesSubgroups( G );;   # works
gap> p:= NextPrimeInt( p );
134217757
gap> G:= CyclicGroup( p );
<pc group of size 134217757 with 1 generator>
gap> ConjugacyClassesSubgroups( G );;   # does not work
Error, PosObj Element: <PosObj>![9] must have an assigned value in
  return Type![9]( Type![5], vec )
[...]

The problem is that different collectors are used for the two groups in question.
The smaller one still uses a 32BitsSingleCollector whereas the bigger one uses the generic PolycyclicCollector.
The element types for the collectors are created in MultiplicativeElementsWithInversesFamilyByRws methods.
The methods for the 8, 16, and 32 bits collectors set the entries at the relevant positions in these types, but this is not the case for the generic collector.

@james-d-mitchell james-d-mitchell added kind: bug Issues describing general bugs, and PRs fixing them kind: bug: unexpected error Issues describing bugs in which computation unexpectedly encounters an error, and PRs fixing them and removed kind: bug Issues describing general bugs, and PRs fixing them labels Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: bug: unexpected error Issues describing bugs in which computation unexpectedly encounters an error, and PRs fixing them
Projects
None yet
Development

No branches or pull requests

2 participants