MétaCan
Menu
Back to cohort
Record W2242881448 · doi:10.1016/j.ifacol.2015.06.362

Tool Wear Improvement in Face-Hobbing of Bevel Gears by Re-designing the Cutting Blades

2015· article· en· W2242881448 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueIFAC-PapersOnLine · 2015
Typearticle
Languageen
FieldEngineering
TopicGear and Bearing Dynamics Analysis
Canadian institutionsConcordia University
Fundersnot available
KeywordsHobbingRakeBevelEnhanced Data Rates for GSM EvolutionTool wearMachiningBevel gearMechanical engineeringCutting toolRake angleBlade (archaeology)EngineeringEngineering drawingStructural engineering

Abstract

fetched live from OpenAlex

Bevel and hypoid gears are manufactured by two main processes, face-milling and face-hobbing. In both processes, blade sticks on the cutter head are prone to be worn out at the corner of the cutting edges. Tool wear can cause unpredictable shut down in production line. By controlling and improving the tool wear, the manufacturing efficiency can be increased. A few researches on the tool wear in bevel gear manufacturing processes were done and the only suggested way to improve the tool wear characteristic was to change the gear design which applies limitations in the gear design stage. Large changes in gradients of the working rake and relief angles along the cutting edge are the important geometrical related factor in the tool wear. In this paper, first, full mathematical representation of the blade including the cutting edge and rake and relief surfaces are presented which it cannot be found in literature. Then, a new method is presented to improve the tool wear characteristics by decreasing the gradients of the working rake and relief angles. In order to validate the better tool wear characteristic of the new blade, FEA machining simulations are conducted on both the proposed and conventional blades. The simulations show great improvements in the tool wear characteristics of the new designed blade in comparison with conventional one.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.623
Threshold uncertainty score0.588

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.014
GPT teacher head0.219
Teacher spread0.205 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it