tensorflow / tensorflow/tflite-support
Replace custom JSON expected result with the protobuf JSON format
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 441
- Forks
- 146
- PR merge metrics
- No merged PRs in 30d
Description
Investigate if we write expected_detections using the proto json format directly, something like this, which should be equivalent to what generated from here (expected_result_dict).
@kinaryml Could you take a look?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare expected_detections in tensorflow_lite_support/cc/test/task/vision/object_detector_test.cc with expected_result_dict in tensorflow_lite_support/python/test/task/vision/object_detector_test.py. Start by reading the referenced test sections and run the object detector tests. Done means the C++ test uses protobuf JSON directly while retaining equivalent expected results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100