[ 
https://issues.apache.org/jira/browse/TIKA-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975147#comment-15975147
 ] 

ASF GitHub Bot commented on TIKA-2306:
--------------------------------------

thammegowda commented on issue #163: TIKA-2306: Update Inception v3 to 
Inception v4 in Object recognition parser 
URL: https://github.com/apache/tika/pull/163#issuecomment-295358397
 
 
   > Wait, does this prevent jpeg metadata from being extracted?
   
   Oh yes! That is the case with existing ObjectRecognition Parser.
   
   How do we run two different parsers for the same file and merge the metadata?
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Update Inception v3 to Inception v4 in Object recognition parser 
> -----------------------------------------------------------------
>
>                 Key: TIKA-2306
>                 URL: https://issues.apache.org/jira/browse/TIKA-2306
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 1.14
>            Reporter: Kranthi Kiran GV
>            Priority: Minor
>              Labels: inception, object_recognition
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Object Recognition Parser currently uses Inception V3 model for the object 
> classification task. Google released a newer Inception V4 model [1][2].
> It has an improved Top -1 accuracy of 80.2 and Top-5 accuracy of 95.2 [3].
> I believe that Tika community would benefit from it. I would be working on 
> this issue in the next few days.
> [1] https://research.googleblog.com/2016/08/improving-inception-and-image.html
> [2] https://arxiv.org/abs/1602.07261
> [3] https://github.com/tensorflow/models/tree/master/slim



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to