MétaCan
Menu
Back to cohort
Record W2202708876

5th workshop on cloud computing

2014· article· en· W2202708876 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

VenueComputer Science and Software Engineering · 2014
Typearticle
Languageen
FieldComputer Science
TopicCloud Computing and Resource Management
Canadian institutionsYork University
Fundersnot available
KeywordsCloud computingComputer scienceCloud computing securityCloud testingService providerComputer securityService (business)Utility computingWorld Wide WebSoftware as a serviceSoftwareSoftware developmentBusinessOperating system
DOInot available

Abstract

fetched live from OpenAlex

The shared computing and communication infrastructure, known as cloud computing, is supporting a growing number of companies to drive their core businesses. The Cloud term characterizes the end-users perspective: it offers services the users access as outsiders (which could be in the form of a computing and communication platform or infrastructure or an application) while being agnostic about the technology underlying it. The implementation details are abstracted away, and the service/computing is consumed as a pay-per-use service and not acquired as an asset. From the service-provider's perspective, a number of technologies can be deployed to deliver the end-user experience. When the provider is outside of the end user's organization, it is called the public cloud or just the cloud. The same underlying technology can be used to provide similar infrastructure / platforms / software within the organization, perhaps offered by a separate business unit or to take advantage of the benefits while maintaining control; in this case, the term private cloud is used. Separate clouds (separated by technology or management or geography) unified to appear as one are termed federated clouds. When the federated clouds are running different technologies, and in particular do not natively expose same APIs, a more specialized term is a heterogeneous federated cloud. When the clouds being federated are composed of both private and public clouds, the result is a hybrid cloud. Cloud offerings are often classified into three main -as-a-Service (-aaS) categories: Infrastructure-,Platform-, and Software-. Other categories are sometimes used to describe specific implementations of these categories Storage-aaS, Management-aaS, etc.

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.002
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: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.661
Threshold uncertainty score0.825

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0010.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.010
GPT teacher head0.215
Teacher spread0.205 · 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