MétaCan
Menu
Back to cohort
Record W2012369294 · doi:10.1093/imaman/dpi029

Calculation of reliability function and remaining useful life for a Markov failure time process

2005· article· en· W2012369294 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

VenueIMA Journal of Management Mathematics · 2005
Typearticle
Languageen
FieldEngineering
TopicStructural Integrity and Reliability Analysis
Canadian institutionsUniversity of TorontoUniversity of New Brunswick
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsReliability (semiconductor)CovariateComputer scienceFunction (biology)Markov processMarkov chainProcess (computing)Reliability engineeringFailure rateMathematical optimizationApplied mathematicsMathematicsEconometricsStatisticsEngineering

Abstract

fetched live from OpenAlex

Reliability analysts are interested in calculating a reliability function (RF), e.g. in order to establish an optimal replacement policy. To implement this policy, it is often important to include measured condition information, such as those from oil or vibration analysis. Information from condition monitoring can be included in reliability analysis by considering the hazard rate function as a function of a stochastic covariate process. In this paper, the failure process along with the covariate process is represented by a discrete Markov process. Methods are designed for calculating the conditional and unconditional RFs and for computing the remaining useful life (RUL) as a function of the current conditions. It is shown that a function that appears in the computation can be obtained as a solution to a Kolmogorov-type system of differential equations. The product-integration method is suggested as the main general method for numerical calculation. The same method is also used to calculate the RUL. Illustration of the main concepts is given using field data from a transmission's oil analysis histories.

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: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.085
Threshold uncertainty score0.343

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.008
GPT teacher head0.230
Teacher spread0.222 · 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