You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies, this isn't really a bug, it's more of a question. But it might be useful for someone else down the road...
I was thrilled to discover this project, as we've been using a very old version of pHash (https://github.com/hszcg/pHash-0.9.6, it has some patches applied to it for things I'm assuming you've since addressed here). We have over 2 million existing pHash values for photos in our database calculated by the older version.
It seems that, for a given photo, the pHash values from our old version differ from the value that the latest version produces. It's different enough that we're not able to detect the images as being similar... Is this expected?
And more importantly, is it is possible that this could happen when the pHash library is updated in the future? That a pHash calculated from today's code could be different from one calculated in some future version of the lib?
The text was updated successfully, but these errors were encountered:
Apologies, this isn't really a bug, it's more of a question. But it might be useful for someone else down the road...
I was thrilled to discover this project, as we've been using a very old version of pHash (https://github.com/hszcg/pHash-0.9.6, it has some patches applied to it for things I'm assuming you've since addressed here). We have over 2 million existing pHash values for photos in our database calculated by the older version.
We're also using a Ruby wrapper for the pHash lib to compare photos: https://github.com/toy/pHash
It seems that, for a given photo, the pHash values from our old version differ from the value that the latest version produces. It's different enough that we're not able to detect the images as being similar... Is this expected?
And more importantly, is it is possible that this could happen when the pHash library is updated in the future? That a pHash calculated from today's code could be different from one calculated in some future version of the lib?
The text was updated successfully, but these errors were encountered: