A Unified Fracture Model for X65 Pipeline Material Under Various Constraints Using the Extended Finite Element Method (XFEM)
Bibliographic record
Abstract
Abstract It is generally accepted that the fracture strain is dependent on geometry/constraints in metals. However, the currently available implementation of extended finite element method (XFEM) assumes a fixed fracture strain criterion independent of the constraints. The objective of this paper is to develop and implement a variable fracture strain criterion in XFEM that is capable of predicting a wide range of fracture conditions in X65 pipeline steels with various crack tip constraints. Various small-scale tests with different out-of-plane constraints obtained from the literature were simulated using the XFEM in abaqus software. These tests included smooth bar, notched bar, single edge notch tension (SENT), and single edge notch bending (SENB) tests. For each test, the value of the maximum principal strain (Maxpe) as a fracture initiation criterion in the cohesive zone model (CZM) in XFEM framework was varied while keeping the fracture energy constant until the model was able to accurately replicate the reported experimental results. For each test, the crack tip constraints were characterized and the stress triaxialities and Lode angle parameters at the onset of fracture initiation were calculated from the models. The results allowed expressing of the fracture strain as an explicit function of stress triaxiality which was then implemented in abaqus XFEM using UDMGINI subroutine. For the sake of comparison, the tests were simulated in finite element method (FEM) using a similar damage initiation model, namely, the Johnson–Cook (J–C) model. A single model in XFEM was able to accurately replicate the experimental observations for all specimens and compared well to experiments in the way simulated by FEM damage model. However, it was observed that XFEM was more suitable to simulate specimens with pre-existing cracks such as in SENT and SENB tests since the crack grew through elements when mesh refinement was not required around the crack tips. Lastly, the simulated results were found to be less mesh sensitive in XFEM than in FEM damage models.
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.000 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 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".