MétaCan
Menu
Back to cohort
Record W2045722572 · doi:10.1063/1.4819804

Laser ablation of iron: A comparison between femtosecond and picosecond laser pulses

2013· article· en· W2045722572 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueJournal of Applied Physics · 2013
Typearticle
Languageen
FieldEngineering
TopicLaser-induced spectroscopy and plasma
Canadian institutionsUniversity of Windsor
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsFluenceFemtosecondMaterials sciencePicosecondLaserAblationSapphireOpticsLaser ablationX-ray laserOptoelectronicsLaser power scalingPhysics

Abstract

fetched live from OpenAlex

In this study, a comparison between femtosecond (fs) and picosecond (ps) laser ablation of electrolytic iron was carried out in ambient air. Experiments were conducted using a Ti:sapphire laser that emits radiation at 785 nm and at pulse widths of 110 ps and 130 fs, before and after pulse compression, respectively. Ablation rates were calculated from the depth of craters produced by multiple laser pulses incident normally to the target surface. Optical and scanning electron microscopy showed that picosecond laser pulses create craters that are deeper than those created by the same number of femtosecond laser pulses at the same fluence. Most of the ablated material was ejected from the ablation site in the form of large particles (few microns in size) in the case of picosecond laser ablation, while small particles (few hundred nanometers) were produced in femtosecond laser ablation. Thermal effects were apparent at high fluence in both femtosecond and picosecond laser ablation, but were less prevalent at low fluence, closer to the ablation threshold of the material. The quality of craters produced by femtosecond laser ablation at low fluence is better than those created at high fluence or using picosecond laser pulses.

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.000
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.360
Threshold uncertainty score0.515

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.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.012
GPT teacher head0.225
Teacher spread0.213 · 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