-
Notifications
You must be signed in to change notification settings - Fork 64
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 in direct sums construction #985
Conversation
Needs rebase |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #985 +/- ##
==========================================
+ Coverage 74.17% 74.22% +0.05%
==========================================
Files 347 347
Lines 110707 110696 -11
==========================================
+ Hits 82117 82169 +52
+ Misses 28590 28527 -63
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Is the |
P.S.: Also documentation build is failing. |
We try here to suggest a consistent patterns for direct sums/direct products/biproducts for some objects which abstractly have biproducts. The general idea is:
Those objects have finite direct sums and finite direct products which agree, and which are called biproducts. We leave as an interface to the user the following choices:
direct_sum
and only get as extra output the injection maps;direct_product
and only get as extra output the projection maps;biproduct
and return the injection maps as well as the projection maps.Moreover, for the objects with "orthogonality relations" i.e.
AbstractLat
,AbstractSpace
andTorQuadModule
, we get rid oforthogonal_sum
since this was misleadingly adirect_sum
in disguise.For consistency, we rename anything in this context named
orthogonal_sum
asdirect_sum
.We also provide for
TorQuadModule
a normal sum+
, similarly to what is possible forZLat
, whenever it makes sense (this could be seen as an "inner sum")