Writing and Reviewing FEA Reports Supporting ASME Section VIII, Division 1 and 2 Designs: Practical Considerations and Recommended Good Practice
Bibliographic record
Abstract
Finite element analysis (FEA) is used, with increasing frequency, to supplement or justify the design of an ASME Section VIII, Division 1 or 2 pressure vessel. When this occurs, good engineering practice indicates that a competent engineer should review the finite element analysis report. In some jurisdictions, it is required that a Professional Engineer review and certify the report. This paper discusses some of the practical aspects of both writing and reviewing a good quality FEA report — both in the context of the technical perspective and in the context of Code compliance. This paper will serve as a practical assistant to an engineer reviewing an FEA report, as well as a guide to an engineer preparing an FEA report. Aspects such as properly following Code requirements, following appropriate Design By Analysis methodologies, and applying good design practices will be discussed.
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.075 | 0.318 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.002 | 0.001 |
| Bibliometrics | 0.006 | 0.003 |
| Science and technology studies | 0.004 | 0.004 |
| Scholarly communication | 0.007 | 0.007 |
| Open science | 0.004 | 0.003 |
| Research integrity | 0.005 | 0.005 |
| Insufficient payload (model declined to judge) | 0.026 | 0.048 |
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".