This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[Feature Request] Assertion operators #12484
Labels
Comments
@jasonyu1996 thank you for the feature request . @mxnet-label-bot [Feature request] |
It seems that I am not the only person who thinks this type of operators beneficial. Is anyone interested in implementing this? @haojin2 @apeforest @samskalicky |
@eric-haibin-lin Hi! Do you think it is necessary to provide an interface for explicitly defining dependencies like this https://www.tensorflow.org/api_docs/python/tf/control_dependencies ? |
@jasonyu1996 Same question... |
It seems that this is indeed a feature in need. Could you please provide some instructions on how this should be implemented? @haojin2 @apeforest @samskalicky |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi! I personally would be happy to see assertion operators in MXNet. While they might seem useless for imperative computations (the NDArray API), I believe they are absolutely helpful for symbolic computation (the Symbol API), especially when implementing libraries (e.g., implementing a library function that takes as input some symbols and returns the result after performing several symbols), where the validity of the input should be checked. Tensorflow has these https://tensorflow.google.cn/api_guides/python/check_ops . It should be noted that in order to ensure that these assertions are executed, how to add them to the computational graph in order to make the output dependent on these assertions should be considered.
The text was updated successfully, but these errors were encountered: