Age | Commit message (Collapse) | Author |
|
I had forgotten that as a workaround for the testing using a different
number of test cases for different hardware backends, we repeat
the expected test results an arbitrary number of times
Change-Id: I4d1ea8daa1cbfd63ebcd7ac93ac30acb5806fafe
|
|
Change-Id: Iaf03755b0d30598f5d09ca36af8eeeb369191950
|
|
Change-Id: Ib7ea0a0b809bdfe1d705b31a08f42e1b7815b0d2
|
|
When looking for the top probability, use the 'first' result not the 'second'.
This avoids an issue where for batched tests the classification index was reported wrongly.
Still doesn't correctly handle multiple results with the exact probabibility, or batched testing,
but it's slightly more correct than before.
Change-Id: I57d33552754667613e222d9d2037e12c87a96854
|
|
implement test for TfLite VGG16 quantized
Change-Id: I2061f62f62684b963fa0f090718f1dcffe5c93ce
|