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

FIX: Fitting free data use in clashom #3154

Merged
merged 3 commits into from
Jan 9, 2019
Merged

Conversation

hulpke
Copy link
Contributor

@hulpke hulpke commented Dec 30, 2018

If the group has been obtained as subgroup from a fitting free/solvable radical computation,
the data will be inherited and might not guarantee that the factor group
really is fitting free. Test/resolve this.

This fixes #3139

Also recode assertion to avoid #3140

@hulpke hulpke added kind: bug: unexpected error Issues describing bugs in which computation unexpectedly encounters an error, and PRs fixing them backport-to-4.10 labels Dec 30, 2018
@codecov
Copy link

codecov bot commented Dec 30, 2018

Codecov Report

Merging #3154 into master will increase coverage by 8.31%.
The diff coverage is 52.63%.

@@            Coverage Diff             @@
##           master    #3154      +/-   ##
==========================================
+ Coverage   75.36%   83.67%   +8.31%     
==========================================
  Files         682      688       +6     
  Lines      327430   336662    +9232     
==========================================
+ Hits       246757   281694   +34937     
+ Misses      80673    54968   -25705
Impacted Files Coverage Δ
lib/grp.gd 100% <ø> (ø) ⬆️
lib/fitfree.gi 57.67% <100%> (+0.67%) ⬆️
lib/matrix.gi 86.63% <25%> (+10.03%) ⬆️
lib/clashom.gi 78.5% <50%> (+9.21%) ⬆️
src/vector.c 92.73% <0%> (-7.27%) ⬇️
src/hookintrprtr.c 67.34% <0%> (-4.88%) ⬇️
src/iostream.c 62.35% <0%> (-4.31%) ⬇️
src/vecffe.c 71.09% <0%> (-3.42%) ⬇️
src/lists.c 76.55% <0%> (-3.36%) ⬇️
src/c_type1.c 86.47% <0%> (-2.37%) ⬇️
... and 289 more

@coveralls
Copy link

coveralls commented Dec 30, 2018

Coverage Status

Coverage decreased (-0.9%) to 82.832% when pulling 038098e on hulpke:fixes into 48b871b on gap-system:master.

@gap-system gap-system deleted a comment from coveralls Dec 30, 2018
@gap-system gap-system deleted a comment from coveralls Dec 30, 2018
If the group has been obtained as subgroup from a fitting free computation,
the data will be inherited and might not guarantee that the factor group
really is fitting free. Test/resolve this.

This fixes gap-system#3139
I.e. do not store an FF setup if the factor has a radical -- code often
assume that the given radical factor is indeed fitting free.
Subsequent manual changes
@hulpke hulpke merged commit 85bfb25 into gap-system:master Jan 9, 2019
@fingolfin fingolfin added the kind: bug Issues describing general bugs, and PRs fixing them label Mar 21, 2019
@markusbaumeister markusbaumeister added the release notes: to be added PRs introducing changes that should be (but have not yet been) mentioned in the release notes label Apr 16, 2019
@fingolfin
Copy link
Member

Backported to stable-4.10 in commits 4f6aa5c fe8ebae 3f85d62

@olexandr-konovalov
Copy link
Member

@hulpke for the release notes, could you please give a proper description of the fix? Thanks.

@hulpke
Copy link
Contributor Author

hulpke commented Jun 15, 2019

@alex-konovalov I think the secription is as good as I can make it. For the release notes
Resolved an error in computing conjugacy classes of a subgroup
should be fine, but it also just cvould go under a general headline of numerous bugs were fixed, as the error was not dangerous.

@olexandr-konovalov
Copy link
Member

I am particularly concerned about "fitting free computation" - seems this part could have been made clearer.

@hulpke
Copy link
Contributor Author

hulpke commented Jun 15, 2019

@alex-konovalov
Fitting free/solvable radical is a class of algorithms that build the potentially problematic data structure. Are you concerned about the release notes (for which I suggested a line, and which do not need this detail), or the code base (for which I think the description in the PR is plausible?

@olexandr-konovalov
Copy link
Member

About the style of the text used for release notes.

@olexandr-konovalov
Copy link
Member

olexandr-konovalov commented Jun 15, 2019

Let me explain in more details why I am assuming that for a side reader this may be cryptic.

First of all, it's now clear which is the behaviour before and which is after. Is what you're describing a bug, or a behaviour after a bug? Next,

If the group has been obtained as subgroup from a fitting free/solvable radical computation,

what is actually computed? A subgroup or a solvable radical? I would struggle to parse this

the data will be inherited and might not guarantee that the factor group

"will be" (after the fix) or "was" (before it) or actually "is" since this did not change at all?

really is fitting free. Test/resolve this.

and Fitting is a surname to be spelled as Fitting.

Would you be happy with this, or it's incorrect:

  • #3154 If the group has been obtained as subgroup from a Fitting free/solvable radical computation, the data is inherited and might not guarantee that the factor group really is Fitting free. Added a check and an assertion to catch this situation.

@olexandr-konovalov olexandr-konovalov added release notes: added PRs introducing changes that have since been mentioned in the release notes and removed release notes: to be added PRs introducing changes that should be (but have not yet been) mentioned in the release notes labels Jun 15, 2019
@olexandr-konovalov
Copy link
Member

I've put that version in #3503 - if you have any corrections, please leave them as comments there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-to-4.10-DONE kind: bug: unexpected error Issues describing bugs in which computation unexpectedly encounters an error, and PRs fixing them kind: bug Issues describing general bugs, and PRs fixing them release notes: added PRs introducing changes that have since been mentioned in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Break loop using ConjugacyClasses on Centralizer in permutation group
6 participants