Small fixes: 'dp' and memory_limit + tensordot axes order #154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR:
memory_limit
meant the'dp'
optimizer would search forever (infinite loop in dynamic-programming with 'max_input' memory limit #153)tensordot
axes in a canonical order (the order they appear on the first operand), so that performance shouldn't change unexpectedly (Performance difference between essentially the same einsum with dummy index interchanging #143)isinstance
call toinfer_backend
(is cleaner? and fixes a rare bug when mixing inputs for e.g. jax compiled contraction)Status