-
Notifications
You must be signed in to change notification settings - Fork 361
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
knot_weights
function expects only a int
(but not a tensor
) as a parameter
#707
Comments
TMS-Namespace
changed the title
knot_weights function requires a numpy int (but not a tensor) as a parameter
Dec 2, 2022
knot_weights
function requires a numpy
int
(but not a tensor
) as a parameter
TMS-Namespace
changed the title
Dec 2, 2022
knot_weights
function requires a numpy
int
(but not a tensor
) as a parameterknot_weights
function expects only a numpy
int
(but not a tensor
) as a parameter
TMS-Namespace
changed the title
Dec 2, 2022
knot_weights
function expects only a numpy
int
(but not a tensor
) as a parameterknot_weights
function expects only a int
(but not a tensor
) as a parameter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
knot_weights
function, from:tensorflow_graphics.math.interpolation.bspline
requires an
int
for thenumber of knots
and thedegree
parameters (it is mentioned in the documentation), and if atf.constant
is passed, theunhashable tensor
exception will occur.Although it is not really a bug, this seems to be a design flaw, and not expected at all (especially that other parameters are expecting tensors), since it breaks graph generation with
@tf.function
, unless I will convert it explicitly to int, as pointed here: tensorflow/tensorflow#27491 (comment)The text was updated successfully, but these errors were encountered: