We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am following the steps mentioned here - https://github.com/bhatuzdaname/cryptflow-demo (also mentioned here - https://pratik-bhatu.medium.com/privacy-preserving-machine-learning-for-healthcare-using-cryptflow-cc6c379fbab7)
However, I get Output mismatch instead of Arrays matched upto 1 decimal points.
Output mismatch
Arrays matched upto 1 decimal points
My config.json is the same as given in the cryptflow-demo repository -
{ "model_name": "model.pb", "input_tensors": { "Placeholder" : "1,224,224,3"}, "target": "SCI", "scale": 12, "output_tensors": [ "fc/fc"] }
The output that my client sees is as follows -
I am not sure what is going wrong...
The text was updated successfully, but these errors were encountered:
I am having the same issue unfortunately. For scale 12 I also get:
Output mismatch tensorflow_output.npy : [ 6.90567 -4.355782 -18.939846] output_output.npy : [5.36870909e+08 5.36870898e+08 5.36870903e+08]
And for scale 20 that they use in the Medium article:
Output mismatch tensorflow_output.npy : [ 6.90567 -4.355782 -18.939846] output_output.npy : [0.94352341 0.68226719 0.90837574]
Did you eventually solve this?
Sorry, something went wrong.
No branches or pull requests
I am following the steps mentioned here - https://github.com/bhatuzdaname/cryptflow-demo (also mentioned here - https://pratik-bhatu.medium.com/privacy-preserving-machine-learning-for-healthcare-using-cryptflow-cc6c379fbab7)
However, I get
Output mismatch
instead ofArrays matched upto 1 decimal points
.My config.json is the same as given in the cryptflow-demo repository -
The output that my client sees is as follows -
I am not sure what is going wrong...
The text was updated successfully, but these errors were encountered: