MétaCan
Menu
Back to cohort
Record W1966316775 · doi:10.1177/154193120304700367

Ecological Interface Design for Network Management

2003· article· en· W1966316775 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueProceedings of the Human Factors and Ergonomics Society Annual Meeting · 2003
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicProduct Development and Customization
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsInterface (matter)Fault managementComputer scienceAbstractionHierarchyNetwork interfaceNetwork managementFault (geology)Network monitoringMedical diagnosisUser interfaceDistributed computingComputer networkEngineeringOperating systemMedicineElectrical engineering

Abstract

fetched live from OpenAlex

This paper describes an experimental investigation of Ecological Interface Design (EID) in computer network management. The constant potential for the addition and removal of devices, as well as change of configurations, makes this work domain more fluid than those previously studied under EID. Two interfaces were created for the University of Toronto campus network consisting of 220 nodes: a P interface based on existing design practices which presented primarily physical information and a P+F interface based on EID which presented both physical and functional information identified by an abstraction hierarchy analysis. Participants were required to use one of the two interfaces to detect and diagnose faults or disturbances in the network in real-time. Network size and fault load were both manipulated as within-participants variables. The P+F interface led to faster detection times, improved rates of detection under higher fault loads, and more accurate diagnoses under higher fault loads. These results suggest that the EID framework may lead to more robust monitoring in computer network management compared to existing interfaces.

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: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.275
Threshold uncertainty score0.513

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.0010.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.021
GPT teacher head0.216
Teacher spread0.195 · 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