MétaCan
Menu
Back to cohort
Record W2894981968 · doi:10.1049/iet-wss.2018.5033

Comprehensive survey of the IoT open‐source OSs

2018· article· en· W2894981968 on OpenAlex
Mahmoud H. Qutqut, Aya Al‐Sakran, Fadi Almasalha, Hossam S. Hassanein

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

VenueIET Wireless Sensor Systems · 2018
Typearticle
Languageen
FieldComputer Science
TopicIoT and Edge/Fog Computing
Canadian institutionsQueen's University
FundersApplied Science Private University
KeywordsComputer scienceInteroperabilityInternet of ThingsScalabilityOpen sourceData scienceWorld Wide WebSoftwareDatabaseOperating system

Abstract

fetched live from OpenAlex

The Internet of things (IoT) has attracted a great deal of research and industry attention recently and is envisaged to support diverse emerging domains including smart cities, health informatics, and smart sensory platforms. Operating system (OS) support for IoT plays a pivotal role in developing scalable and interoperable applications that are reliable and efficient. IoT is implemented by both high‐end and low‐end devices that require OSs. Recently, the authors have witnessed a diversity of OSs emerging into the IoT environment to facilitate IoT deployments and developments. In this study, they present a comprehensive overview of the common and existing open‐source OSs for IoT. Each OS is described in detail based on a set of designing and developmental aspects that they established. These aspects include architecture and kernel, programming model, scheduling, memory management, networking protocols support, simulator support, security, power consumption, and support for multimedia. They present a taxonomy of the current IoT open‐source OSs. The objective of this survey is to provide a well‐structured guide to developers and researchers to determine the most appropriate OS for each specific IoT devices/applications based on their functional and non‐functional requirements. They remark that this is the first such tutorial style paper on IoT OSs.

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: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.548
Threshold uncertainty score1.000

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.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0030.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.055
GPT teacher head0.281
Teacher spread0.226 · 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