Skip to content
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

Uncaught (in promise) Error: Tensorflow Op is not supported: _FusedConv2D #233

Open
brrbaral opened this issue Jan 30, 2024 · 5 comments
Open

Comments

@brrbaral
Copy link

Hi, I tried to build the web demo using:
bazel run wit_dashboard/demo:imagedemoserver

I got the error:

Uncaught (in promise) Error: Tensorflow Op is not supported: _FusedConv2D
    at t.mapNode (image.html:76874:708586)
    at image.html:76874:707992
    at Array.reduce (<anonymous>)
    at t.transformGraph (image.html:76874:707952)
    at t.<anonymous> (image.html:76874:743398)
    at image.html:76874:673788
    at Object.next (image.html:76874:673893)
    at a (image.html:76874:672663)

The same error is in web demo as well: https://pair-code.github.io/what-if-tool/demos/image.html

@jameswex
Copy link
Collaborator

The issue most likely has to do with version numbers of dependencies. The What-If Tool is an old project at this point and was last built against old versions of downstream dependencies. In general, it has been obsoleted by our follow-up tool, LIT (https://pair-code.github.io/lit/, https://github.com/PAIR-code/lit/).

If you wish to try to get the build to work, you may need to work off of an older version of TensorFlow JS than what you currently have installed.

In general, I recommend you look towards more up-to-date tools such as LIT, depending on your task.

@taposh
Copy link

taposh commented Jan 31, 2024

Same error on the Pair-code website as well.

image

@jameswex
Copy link
Collaborator

jameswex commented Feb 1, 2024

Thanks, I see the issue and am looking into a solution. It seems that the model files for the image classifier that we used from tensorflow.js got moved and now when our demo is redirected to its new location, it is getting a new version of the model files that doesn't match our tensorflow.js version we use in the demos.

@jameswex
Copy link
Collaborator

jameswex commented Feb 1, 2024

I have fixed the deployed version by making the following change to the compiled image demo html file: a410765

I have not made any change to the source code that would fix this issue in anyone building the demo locally. That would require updating our tf.js version and mobilenet version in our bazel workspace most likely, and then perhaps some code updates for the newer versions of those libraries.

@taposh
Copy link

taposh commented Feb 2, 2024

Works now ! thank you @jameswex

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants