Review: Fundamentals, limitations and pitfalls on the development and application of precision nutrition techniques for precision livestock farming
Bibliographic record
Abstract
Precision livestock farming (PLF) concerns the management of livestock using the principles and technologies of process engineering. Precision nutrition (PN) is part of the PLF approach and involves the use of feeding techniques that allow the proper amount of feed with the suitable composition to be supplied in a timely manner to individual animals or groups of animals. Automatic data collection, data processing, and control actions are required activities for PN applications. Despite the benefits that PN offers to producers, few systems have been successfully implemented so far. Besides the economical and logistical challenges, there are conceptual limitations and pitfalls that threaten the widespread adoption of PN. Developers have to avoid the temptation of looking for the application of available sensors and instead concentrate on identifying the most appropriate and relevant information needed for the optimal functioning of PN applications. Efficient PN applications are obtained by controlling the nutrient requirement variations occurring between animals and over time. The utilization of feedback control algorithms for the automatic determination of optimal nutrient supply is not recommended. Mathematical models are the preferred data processing method for PN, but these models have to be designed to operate in real time using up-to-date information. These models are therefore structurally different than traditional nutrition or growth models. Combining knowledge- and data-driven models using machine learning and deep learning algorithms will enhance our ability to use real-time farm data, thus opening up new opportunities for PN. To facilitate the implementation of PN in farms, different experts and stakeholders should be involved in the development of the fully integrated and automatic PLF system. Precision livestock farming and PN should not be seen as just being a question of technology, but a successful marriage between knowledge and technology.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.008 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.003 | 0.002 |
| Bibliometrics | 0.004 | 0.005 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.004 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.003 | 0.003 |
| Insufficient payload (model declined to judge) | 0.006 | 0.003 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".