Relationship of Typical Core Temperatures After Hydrocooling on Retention of Different Quality Components in Sweet Cherry
Bibliographic record
Abstract
The research was conducted to first determine the commercial reality in regards to effectiveness of hydrocooling of sweet cherries ( Prunus avium ) at commercial packing houses. Temperature data obtained from the commercial studies were then used as a guide to evaluate the effect of small differences (0.5, 3, and 5 °C) in sweet cherry core temperature on the quality retention of ‘Sweetheart’ sweet cherries over 6 weeks of storage to simulate container shipment. Sweet cherry core temperatures after in-line hydrocooling and at the time of packing were generally around 3 or 5 °C. Once palletized and placed in commercial cold rooms, the internal boxes of a pallet did not cool any further. Only when a pallet was exposed to direct airflow from cooling coils did the exterior boxes in an assembled pallet show any further reduction in core temperature of packed sweet cherries. Experiments to evaluate the differences in quality retention at close to ideal core temperature (0.5 °C) vs. at more typical 3 or 5 °C core temperatures demonstrated significant decline when the two higher temperatures were maintained over 6 weeks of storage. Sweet cherry firmness, titratable acidity, and stem removal force value declines in storage were significantly affected by these small differences in core temperature, showing the best retention at 0.5 °C. Stem browning increased significantly with 3 or 5 °C storage by 6 weeks of storage. Decay was also significantly increased with warmer temperatures, but the results were variable likely due to differences in fruit infection at the time of harvest. Soluble solids were unaffected by storage temperature, and weight loss and pitting severity were somewhat affected. These results support the need for post packing cooling of sweet cherries as the core temperatures achieved by in-line hydrocoolers during packing do not reduce temperatures sufficiently to ensure good quality retention over longer periods of time that are required for container shipping to export markets. Therefore, forced-air cooling is recommended to further reduce sweet cherry temperatures in the box, before shipping.
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.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
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".