germanattanasio / visual-recognition-nodejs

DEPRECATED: this repo is no longer actively maintained
Apache License 2.0
361 stars 351 forks source link

Custom Classifier not getting picked up #183

Closed swamichandra closed 8 years ago

swamichandra commented 8 years ago

After training a custom classifier successfully, it is not getting picked up. Getting "No matching classifiers found." message.

kognate commented 8 years ago

Can you paste the response you got on the creation step?

swamichandra commented 8 years ago

Not sure which response you are looking for. But here is the info about the custom classifier model.

swamchan$ curl -X GET "https://gateway-a.watsonplatform.net/visual-recognition/api/v3/classifiers/PackageIdentifier_1887047378?api_key=xxxxxx&version=2016-05-20"

{
    "classifier_id": "PackageIdentifier_1887047378",
    "name": "PackageIdentifier",
    "owner": "xx-xx-xx-xx-xxx",
    "status": "ready",
    "created": "2016-07-01T02:27:25.809Z",
    "classes": [{"class": "PackageFound"}]
}
germanattanasio commented 8 years ago

@swamichandra is this a demo issue or a question about the API?

swamichandra commented 8 years ago

The issue is about the demo. I trained a new classifier and pointed the demo app to use the API key. But the new classifier is not getting used and the app seems to be reverting back to the default VR models.

On Friday, July 1, 2016, German Attanasio Ruiz notifications@github.com wrote:

@swamichandra https://github.com/swamichandra is this a demo issue or a question about the API?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/watson-developer-cloud/visual-recognition-nodejs/issues/183#issuecomment-229990286, or mute the thread https://github.com/notifications/unsubscribe/AExXwxT_6qnJkvCW_gdzDCdlUZoPjTC4ks5qRUAjgaJpZM4JCypo .

kognate commented 8 years ago

There is no way to use a classifier in the demo app unless it was trained in the demo app. You would have to modify the demo app quite a bit because the demo app expects the trained classifiers to be deleted soon.

swamichandra commented 8 years ago

That's a bummer. What would it take to specify a particular classifier ID to be used by the app? I'm not able to locate where in the app the classifier ID is specified even for the default model.

germanattanasio commented 8 years ago

The classifier id is being saved in a cookie call classifier

germanattanasio commented 8 years ago

I've created and issue to prevent people from opening issues and asking for where things are in the code #185