MétaCan
Menu
Back to cohort
Record W2010944089 · doi:10.1142/s0219876213500266

COMPUTATIONAL ASPECTS OF MONTE-CARLO SIMULATIONS OF THE FIRST PASSAGE TIME FOR MULTIVARIATE TRANSFORMED BROWNIAN MOTIONS WITH JUMPS

2013· article· en· W2010944089 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

VenueInternational Journal of Computational Methods · 2013
Typearticle
Languageen
FieldEconomics, Econometrics and Finance
TopicCredit Risk and Financial Regulations
Canadian institutionsWilfrid Laurier University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsJump diffusionMonte Carlo methodContext (archaeology)Computer scienceMultivariate statisticsJumpStochastic processProcess (computing)First-hitting-time modelApplied mathematicsMathematical optimizationStatistical physicsEconometricsMathematicsStatisticsMachine learningPhysics

Abstract

fetched live from OpenAlex

Many problems in science, engineering, and finance require the information on the first passage time (FPT) of a stochastic process. Mathematically, such problems are often reduced to the evaluation of the probability density of the time for such a process to cross a certain level, a boundary, or to enter a certain region. While in other areas of applications the FPT problem can often be solved analytically, in finance we usually have to resort to the application of numerical procedures, in particular when we deal with jump-diffusion stochastic processes (JDP). In this paper, we propose a Monte-Carlo-based methodology for the solution of the FPT problem in the context of multivariate (and correlated) JDPs. The developed technique provides an efficient tool for a number of applications, including credit risk and option pricing. We demonstrate its applicability to the analysis of default rates and default correlations of several different, but correlated firms via a set of empirical data.

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: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.611
Threshold uncertainty score0.487

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.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.030
GPT teacher head0.303
Teacher spread0.273 · 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