Meat Freshness Prediction

Bhargav Sagiraju, Nathan Casanova, Lam Ivan Chuen Chun, Manan Lohia, Toshinori Yoshiyasu
5/1/2023
cs.CVeess.IV

No official code found. Best implementation: TheLohia/Phteven (3 stars, MIT, last commit 2023-04-23).

Abstract

In most retail stores, the number of days since initial processing is used as a proxy for estimating the freshness of perishable foods or freshness is assessed manually by an employee. While the former method can lead to wastage, as some fresh foods might get disposed after a fixed number of days, the latter can be time-consuming, expensive and impractical at scale. This project aims to propose a Machine Learning (ML) based approach that evaluates freshness of food based on live data. For the current scope, it only considers meat as a the subject of analysis and attempts to classify pieces of meat as fresh, half-fresh or spoiled. Finally the model achieved an accuracy of above 90% and relatively high performance in terms of the cost of misclassification. It is expected that the technology will contribute to the optimization of the client's business operation, reducing the risk of selling defective or rotten products that can entail serious monetary, non-monetary and health-based consequences while also achieving higher corporate value as a sustainable company by reducing food wastage through timely sales and disposal.

View on arXivView PDF

Code Implementations(1)

TheLohia/PhtevenCommunity100%
MIT
33CSS, HTMLApr 17, 20233 years agoMIT

Similar Papers

Cite this paper

@article{sagiraju2023meat,
  title  = {Meat Freshness Prediction},
  author = {Bhargav Sagiraju and Nathan Casanova and Lam Ivan Chuen Chun and Manan Lohia and Toshinori Yoshiyasu},
  year   = {2023},
  eprint = {2305.00986},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2305.00986v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2305.00986.svg)](https://codeofpaper.com/paper/2305.00986)

Discussion