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
{{ message }}
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.
The error is raised from svd operation in backends/numpy/decompositions.py: num_sing_vals_keep = min(max_singular_values, num_sing_vals_err) as ConcretizationTypeError: Abstract tracer value encountered where concrete value is expected:.
This error is actually as expected even before I tried this, since jax jitted function only accepts and returns tensors with fixed shape, which supports only a subset of functionalities of tf.function. Since split_node with max_truncation_err returns nodes of varying shape (final shape depends on the singular value), it seems to be incompatible with jax jit mechanism.
Any thoughts or workaround on this? As I believe it is very common to apply split_node with max_singular_values in tensornetwork related algorithms and it would be great such algorithms can be jitted.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
SVD and
split_node
are ok on tensorflow backend with tensorflow jit:But it fails on jax backend as:
The error is raised from svd operation in
backends/numpy/decompositions.py
:num_sing_vals_keep = min(max_singular_values, num_sing_vals_err)
asConcretizationTypeError: Abstract tracer value encountered where concrete value is expected:
.This error is actually as expected even before I tried this, since jax jitted function only accepts and returns tensors with fixed shape, which supports only a subset of functionalities of
tf.function
. Sincesplit_node
withmax_truncation_err
returns nodes of varying shape (final shape depends on the singular value), it seems to be incompatible with jax jit mechanism.Any thoughts or workaround on this? As I believe it is very common to apply
split_node
withmax_singular_values
in tensornetwork related algorithms and it would be great such algorithms can be jitted.The text was updated successfully, but these errors were encountered: