MétaCan
Menu
Back to cohort
Record W2100475936 · doi:10.1109/pacrim.1989.48354

DPD: a distributed program debugger for the REM environment

2003· article· en· W2100475936 on OpenAlexaff
R. S. Side, Gholamali C. Shoja

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicDistributed systems and fault tolerance
Canadian institutionsUniversity of Victoria
Fundersnot available
KeywordsDebuggerComputer scienceSynchronization (alternating current)AbstractionProcess (computing)Graphical user interfaceDebuggingProgramming languageController (irrigation)Real-time computingOperating systemDistributed computingComputer network

Abstract

fetched live from OpenAlex

The development of a distributed program debugger (DPD) for the remote execution manager (REM) environment is discussed. The model for DPD and REM consists of multiple processors, each with its own private memory and each capable of running several processes. DPD debugs at a higher level of abstraction than sequential debuggers, specifically at the process communication and control level. Synchronization and communication faults are more easily detected when events are the sending and receiving of messages or the creation and termination of processes. When a fault is detected in a distributed program, DPD has the ability to stop the program, roll back, and replay. During the replay, the user can control and change the behavior of the program in order to detect the synchronization faults. A graphical interface is used to show the ordering of events and the communication between processes.>

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 imitation

Not 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.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.006
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Software · Consensus signal: none
Teacher disagreement score0.015
Threshold uncertainty score0.050

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.006
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.001
Science and technology studies0.0000.001
Scholarly communication0.0010.003
Open science0.0030.003
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0150.007

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.016
GPT teacher head0.244
Teacher spread0.228 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreSoftware

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".

Quick stats

Citations0
Published2003
Admission routes1
Has abstractyes

Explore more

Same topicDistributed systems and fault toleranceFrench-language works237,207