-
Notifications
You must be signed in to change notification settings - Fork 182
a little bit better documentation for nice monomorphisms #6211
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -344,11 +344,32 @@ nice monomorphism of a given group <C>G</C>, | |
| for example if <C>G</C> is a matrix group and <C>map</C> describes the | ||
| faithful action of <C>G</C> on a small set of vectors. | ||
| In such a case, one can prescribe this monomorphism via | ||
| <C>SetNiceMonomorphism( G, map )</C>, | ||
| provided that <C>map</C> stores that it is injective. | ||
| The latter can be achieved by calling <C>IsInjective( map )</C> or, | ||
| if one is sure that <C>map</C> is injective and one wants to avoid the | ||
| overhead of the test, by calling <C>SetIsInjective( map, true )</C>. | ||
| <C>SetNiceMonomorphism( G, map )</C> if certain technical requirements | ||
| are satisfied. | ||
| <P/> | ||
| <List> | ||
| <Item> | ||
| <C>G</C> does not store a nice monomorphism yet. | ||
| </Item> | ||
| <Item> | ||
| <C>map</C> stores that it is injective. | ||
| This can be achieved by calling <C>IsInjective( map )</C> or, | ||
| if one is sure that <C>map</C> is injective and one wants to avoid the | ||
| overhead of the test, by calling <C>SetIsInjective( map, true )</C>. | ||
| Note that the <C>IsInjective</C> call for <C>map</C> may compute and store | ||
| some different nice monomorphism in the source of <C>map</C>, | ||
| which is probably <C>G</C>. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So calling
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You can call An example where |
||
| </Item> | ||
| <Item> | ||
| <C>map</C> knows that it is a group homomorphism, | ||
| calling <Ref Oper="ImagesSet"/> with <C>map</C> and a subgroup of <C>G</C> | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there a way to check if this condition holds?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I do not know an easy way, so I wanted to be careful with promises. Initially I had thought that we can write that at least Usually something that makes sense as a nice monomorphism will be in |
||
| returns a group object, and analogously <Ref Oper="PreImagesSet"/> for an | ||
| image group returns a group object. | ||
| For example, | ||
| mappings constructed with <Ref Func="GeneralMappingByElements"/> will | ||
| <E>not</E> be <Q>nice enough</Q> to serve as nice monomorphisms. | ||
| </Item> | ||
| </List> | ||
|
|
||
| <#Include Label="IsHandledByNiceMonomorphism"> | ||
| <#Include Label="NiceMonomorphism"> | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
O.k.