MétaCan
Menu
Back to cohort
Record W2169183020 · doi:10.1109/inm.2001.918011

Dynamic evolution of network management software by software hot-swapping

2002· article· en· W2169183020 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.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicMobile Agent-Based Network Management
Canadian institutionsCarleton UniversityNortel (Canada)
Fundersnot available
KeywordsComputer scienceSoftwareSoftware engineeringJavaModular designProcess (computing)Network managementSoftware developmentSoftware systemOperating systemDistributed computing

Abstract

fetched live from OpenAlex

The computer communications world is very dynamic, requiring continual software updating for correction, perfection, and increased functionality. The problem addressed here is that of providing an evolutionary path for software that permits updating without disrupting the operation and management of the network. This problem is relevant to network management software which is also dynamic. For example SNMPv3 is not yet a standard and is not yet widely deployed. Its initial installations will need to be perfected as more experience is acquired. This paper examines a software hot-swapping solution to the problem, whereby management system software modules can be replaced dynamically without disrupting the management process. The paper also discusses application of the technique to a modular SNMPv3 system implemented in Java.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.859
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.001
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.193
Teacher spread0.185 · 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

Quick stats

Citations22
Published2002
Admission routes1
Has abstractyes

Explore more

Same topicMobile Agent-Based Network ManagementFrench-language works237,207