Closed RafaelMiquelino closed 3 years ago
Thanks for reaching out! This sounds like an issue with reading a file from a file system in Python, not a Face Geometry pipeline logic issue. @jiuqiant will be the person to help you navigate through this
Currently, you need to import all the calculator options the graph uses in the python file to make it read the graph correctly. Here is how we do this for face mesh: https://github.com/google/mediapipe/blob/master/mediapipe/python/solutions/face_mesh.py#L23. We will have some improvements soon to do this automatically soon.
Thanks, it did the trick.
Please make sure that this is a build/installation issue and also refer to the troubleshooting documentation before raising any issues.
System information (Please provide as much relevant information as possible)
Describe the problem:
I get the error
Calculator::Open() for node "facegeometryfromdetection__FaceGeometryPipelineCalculator" failed: ; Error while reading file: /Users/***/.virtualenvs/mediapipe/lib/python3.7/site-packages; Failed to read content blob! Resolved path = /Users/***/.virtualenvs/mediapipe/lib/python3.7/site-packages; Failed to read a metadata blob from file!; Failed to read the geometry pipeline metadata from file!
when trying to run my custom graph from Python.I run through #1253 and #1584 and there are valuable information there and I compiled the file and placed that on a specific place, however I don't understanding why my path is resolving to the Python
site-packages
folder and of course there is no geometry pipeline metadata file there.Provide the exact sequence of commands / steps that you executed before running into the problem:
I added the custom graphs to the
mediapipe/BUILD
file as recommended in #1578:The I call my graph and try to process an image from python using the SolutionBase class:
The I get the mentioned error:
The custom graphs are attached (in .txt for compatibility reasons):
The BUILD config for the two graphs are also below:
Complete Logs: Include Complete Log information or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached: