You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The optimizations in GeneralizedMorphismsForCAP which I have removed in #1653 probably do not fulfill the specification "equal input gives equal output". Test:
One can check that both alternatives of mor_gen are equal but the composition gives a different result in the alternative case due to the optimizations. The caches might still make this work somehow, but I'm not sure they actually guarantee the correctness and since we do not want to rely on caching for correctness anyway this is bad in any case.
Background: Without the optimizations, some tests in CategoricalTowers are significantly slower (e.g. SnakeInFreeAbelian.g in FiniteCocompletions and all tests in Algebroids using GeneralizedMorphisms). To avoid long running tests and timeouts in the CI, I will reintroduce the optimizations. However, they should be removed at some point and possibly replaced by compiled code with good performance.
The text was updated successfully, but these errors were encountered:
zickgraf
added a commit
to zickgraf/CAP_project
that referenced
this issue
Sep 11, 2024
to avoid timeouts in tests in CategoricalTowers
The optimizations probably do not fulfill the specification
"equal input gives equal output",
see homalg-project#1669
to avoid timeouts in tests in CategoricalTowers
The optimizations probably do not fulfill the specification
"equal input gives equal output",
see homalg-project#1669
The optimizations in GeneralizedMorphismsForCAP which I have removed in #1653 probably do not fulfill the specification "equal input gives equal output". Test:
One can check that both alternatives of
mor_gen
are equal but the composition gives a different result in the alternative case due to the optimizations. The caches might still make this work somehow, but I'm not sure they actually guarantee the correctness and since we do not want to rely on caching for correctness anyway this is bad in any case.Background: Without the optimizations, some tests in CategoricalTowers are significantly slower (e.g.
SnakeInFreeAbelian.g
in FiniteCocompletions and all tests in Algebroids using GeneralizedMorphisms). To avoid long running tests and timeouts in the CI, I will reintroduce the optimizations. However, they should be removed at some point and possibly replaced by compiled code with good performance.The text was updated successfully, but these errors were encountered: