MétaCan
Menu
Back to cohort
Record W2330726326 · doi:10.1515/secm-2013-0257

Impact of layup rate on the quality of fiber steering/cut-restart in automated fiber placement processes

2014· article· en· W2330726326 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

VenueScience and Engineering of Composite Materials · 2014
Typearticle
Languageen
FieldEngineering
TopicEpoxy Resin Curing Processes
Canadian institutionsNational Research Council Canada
Fundersnot available
KeywordsFiberMaterials scienceProcess (computing)CurvatureCompactionComputer scienceComposite materialMathematicsGeometry

Abstract

fetched live from OpenAlex

Abstract Developing reliable processes is one of the key elements in producing high-quality composite components using an automated fiber placement (AFP) process. In this study, both simulation and experimental studies were carried out to investigate fiber steering and cut/restart under different processing parameters, such as layup rate and compaction pressure, during the AFP process. First, fiber paths were designed using curved fiber axes with different radii. Fiber placement trials were then conducted to investigate the quality of the steered fiber paths. Furthermore, a series of sinusoidal fiber paths were fiber placed and investigated. Moreover, a six-ply laminate with cut-outs in it was manufactured in the cut/restart trials. The accuracy of the fiber cut/restart was compared at different layup rates for both one- and bi-directional layups. Experimental results show that it was possible to layup steered fiber paths with small radii of curvature (minimum 114 mm) designed for this study when the proper process condition was used. It was observed from the cut/restart trials that the quality of tow cut was independent of layup speed; however, the accuracy of tow restart was related to the layup speed. The faster the layup speed, the less accurate was the tow restart.

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: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.265
Threshold uncertainty score0.502

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.001
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.017
GPT teacher head0.284
Teacher spread0.267 · 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