MétaCan
Menu
Back to cohort
Record W4387480319 · doi:10.1016/j.cma.2023.116509

Fictitious domain method: A stabilized post-processing technique for boundary-flux calculation using cut elements

2023· article· en· W4387480319 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

VenueComputer Methods in Applied Mechanics and Engineering · 2023
Typearticle
Languageen
FieldEngineering
TopicNumerical methods in engineering
Canadian institutionsUniversité Laval
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsBoundary (topology)MathematicsBoundary knot methodFinite element methodBoundary value problemMathematical analysisSingular boundary methodPenalty methodPiecewisePosition (finance)Context (archaeology)Domain (mathematical analysis)Mixed boundary conditionPiecewise linear functionApplied mathematicsBoundary element methodGeometryMathematical optimizationPhysics

Abstract

fetched live from OpenAlex

This paper presents a technique for calculating boundary fluxes in the context of fictitious domain methods. We focus on a simple boundary-value problem and use Nitsche’s method stabilized with ghost penalty for the finite element formulation. To recover the flux, we derive a formulation directly from the boundary-value problem’s finite element formulation. Since the boundary may not align with the mesh, we compute the approximate flux using piecewise linear polynomials on cut elements. We then deduce the desired flux as the trace of the solution on the boundary. To ensure that the condition number of the resulting system matrix is independent of the boundary’s position on the mesh, we add a ghost penalty term. This term acts on the jumps of the gradients over interior facets belonging to elements intersected by the boundary. Two and three-dimensional numerical examples are provided, and show that the method is accurate and has optimal convergence regardless of the immersed boundary position.

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.003
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.498
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.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.025
GPT teacher head0.333
Teacher spread0.308 · 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