Bibliographic record
Abstract
Winpak Limited is an international company which manufactures and distributes high quality packaging material and related packaging machines. Food, beverage, and health care packaging are some of many products Winpak has to offer. The design for the packaging is created through a flexographic printing process. The machines used in the flexographic printing process are capable of producing packaging up to a rate of 500 metres per minute. The machines are currently running at 100 metres per minute or less due to a phenomenon called "bounce." Bounce is recognized by print variability, specifically in the formation of horizontal bands where the ink transfer is noticeably diminished or increased. The phenomenon does not appear at low printing speeds, but begins to occur when print speeds approach 100 metres per minute. Bounce is currently limiting the amount of packaging Winpak can produce. The team was tasked with the goal of finding what could be causing bounce in the printing process and to recommend possible solutions to the problem. Resonance and rotational imbalance of the rollers, the doctor blade used to remove excess ink from the printing material, and the sticky back tape used to hold the print template to the roller were all are as the team investigated. A modal analysis of one of the print cylinders was created in ANSYS. The first vibration mode occurs within the operating speed of the printing press. This means bounce could occur at a print speed of 270 meters per minute. However, the finite element model does not take into account environmental effects, or vibrations occurring in other components of the printing press, which can change the speed which bounce would occur at. This mode shape would cause the material at either end of the print cylinder to print more faint than the material in the middle. The recommended course of action is to install a new doctor blade and try a different brand of sticky back to increase the amount of damping on the print rollers. Increasing the amount of damping should reduce the amount of vibration, and bounce as well. A doctor blade […]
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.001 | 0.004 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.003 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.079 | 0.029 |
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".