Effects of subsystem mission time on reliability allocation
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.
Bibliographic record
Abstract
During the early stages of system development, various factors are considered when determining an allocation weight to apportion a system’s reliability requirement to each subsystem. Previous methods have included subsystem mission time as a factor in obtaining the allocation weight in order to allocate a higher failure rate to a subsystem with a shorter mission time than the system’s mission time. This article, first shows that the results obtained from previous methods are misleading, mainly because the allocated failure rate of the subsystem is expressed in the system’s mission time rather than the subsystem’s mission time. It is further shown that if a designer intends to allocate a lower failure rate to a subsystem that has to operate longer in the system, subsystem mission time must not be included as a factor when determining the allocation weight. If a designer wants to allocate the system failure rate equally to each subsystem regardless of a subsystem’s mission time, subsystem mission time must be included as a factor.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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 it