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
Uploading failing_sdfg.json…
I have an SDFG that fails with the following error ValueError: Dimension mismatch in composition: Subset composed must be either completely stripped of all non-data dimensions or be not stripped of latter at all. and gives me the following stack:
I did not use a frontend but build it through the API using my Jax to SDFG translator.
If I disable all optimizations (simplify and auto_ops) then the SDFG passes all tests.
Some context, the original code had a lot of numpy.squeeze() and numpy.expand_dims() class, which are translated into Memlets, for example w[:, 0, :] -> u[:, :].
I then switched to mapped Tasklets of the form __out = __in, which is quite stupid.
However, this switch was able to fix, or rather avoid, the issue.
Since I had no problems using these operations I think that the problem is that there are several such Memlets after each other.
The text was updated successfully, but these errors were encountered:
Uploading failing_sdfg.json…
I have an SDFG that fails with the following error
ValueError: Dimension mismatch in composition: Subset composed must be either completely stripped of all non-data dimensions or be not stripped of latter at all.
and gives me the following stack:I did not use a frontend but build it through the API using my Jax to SDFG translator.
If I disable all optimizations (simplify and auto_ops) then the SDFG passes all tests.
Some context, the original code had a lot of
numpy.squeeze()
andnumpy.expand_dims()
class, which are translated into Memlets, for examplew[:, 0, :] -> u[:, :]
.I then switched to mapped Tasklets of the form
__out = __in
, which is quite stupid.However, this switch was able to fix, or rather avoid, the issue.
Since I had no problems using these operations I think that the problem is that there are several such Memlets after each other.
The text was updated successfully, but these errors were encountered: