MétaCan
Menu
Back to cohort
Record W2016265567 · doi:10.1002/cpe.1154

Towards building a conflict‐free mobile distributed file system

2007· article· en· W2016265567 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

VenueConcurrency and Computation Practice and Experience · 2007
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Data Storage Technologies
Canadian institutionsUniversity of Ottawa
Fundersnot available
KeywordsComputer scienceOperating systemCacheSelf-certifying File SystemFile system fragmentationComputer networkFile systemMobile databaseVirtual file systemFile serverMobile computingDistributed File SystemNetwork File SystemDistributed computingDevice fileComputer fileMobile stationSSH File Transfer ProtocolBase station

Abstract

fetched live from OpenAlex

Abstract The rising demand for mobile computing has created a need for an improved file system that supports mobile clients. Current file systems with support for mobility provide availability through file replicas that are cached at the client side. However, mobile clients may experience different obstacles with regards to the local cache, such as the limited network bandwidth, the intermittent connection, and serious conflicts when synchronizing back to the server. In this paper, we propose a novel mobile distributed file system design, which provides high availability and reliable storage for files and guarantees that file operations are executed regardless of concurrency and failure issues. The design is intended to fit mobile clients (e.g. PDAs and cell phones) that have limited storage space and cannot store all of the data they need, and yet require access to these data at all times. We adopt a server‐side caching in order to guarantee sufficient caching space to all mobile clients, and to ensure the availability of files in the case of clients' failures. We present our algorithm, describe its implementation, simulate its high availability functions, and report on its performance evaluation using a cluster of workstations. Our simulation results indicate clearly that our algorithm exhibits a significant degree of automation and conflict‐free mobile file system. Copyright © 2007 John Wiley & Sons, Ltd.

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.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.883
Threshold uncertainty score0.627

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.002
Open science0.0000.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.023
GPT teacher head0.330
Teacher spread0.307 · 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