-
Notifications
You must be signed in to change notification settings - Fork 2
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
New linear representation type #6
Comments
Can we maybe do discussions about groups only in LIeGroups.jl? Also not my most recent question, whether the GroupAction we currently have should stay abstract – this indicates it maybe should? But again, since I am just starting redesigning that on the other repository, maybe changing the code here is a bit counterproductive – Let's do it over on LieGroups – otherwise I will just completely loose track. |
I can even finish the Interface PR without actions and you do a PR on actions over on Lie groups? |
The It is not adding a new feature. It is more a simplification, since all the As to your question: should group action be abstract: yes (even without this proposal). |
All work on the repo is in the first PR (#2). Later today I will remove my first steps towards GroupActions because they seem to be total bogus again probably, and merge that first PR. |
It's merged, I will probably do a PR on exp or a first group next – so you could start a PR on Actions? Again, Ia ma not sure whether we need one or two directions (one in the action one as argument in apply). translate is now combined with compose already. So we just need apply |
Sure, we can do that. Maybe |
We can easily keep track of it here in LieGroups.jl then :) |
Many group actions are actually linear representations, which allows to define
apply_diff
automatically. I would suggest the following:AbstractLinearRepresentation
:apply_diff
for this class of group actions:AbstractLinearRepresentation
For instance:
Most of the existing implementations of
apply_diff
follow this pattern (because they are linear representation), for instance:apply_diff(::TranslationAction,...)
apply_diff(::RotationActionOnVector,...)
apply_diff(::RotationTranslationOnVector
,...)`The text was updated successfully, but these errors were encountered: