MétaCan
Menu
Back to cohort

High‐Level Methodologies to Evaluate Naval Task Groups

2011· article· en· W2120158572 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

VenueNaval Engineers Journal · 2011
Typearticle
Languageen
FieldEngineering
TopicTechnology Assessment and Management
Canadian institutionsUniversity of SaskatchewanUniversity of Manitoba
Fundersnot available
KeywordsMetric (unit)Task (project management)Context (archaeology)Computer scienceAsset (computer security)Set (abstract data type)Process (computing)Task groupSystems engineeringOperations researchEngineeringReliability engineeringEngineering managementOperations managementComputer security

Abstract

fetched live from OpenAlex

Abstract Defense organizations within many nations (e.g., United States and Canada), use capability‐based planning (CBP) to guide their force development processes. A key element of the CBP process is testing current and proposed capabilities against force planning scenarios, particularly for asset evaluation. This analysis involves a wide range of capabilities, and thus is a multicriteria problem. Comparison of alternatives using multiple criteria is challenging, and often is assisted by aggregation techniques. Set in a naval context, this paper presents three high‐level capability aggregation techniques: the vector method, star plot method, and wedge method. Each method aggregates naval task group capabilities, with respect to a scenario, into three quantifiable measures: effectiveness, unmatched, and unused. As with numerous techniques, the effectiveness gauges the ability of a task group to meet a set of scenario requirements. The unmatched and unused measures yield insight into capability gaps, which is an important aspect of CBP. The unmatched metric measures scenario requirements that are not provided by a task group and the unused metric measures task group capabilities that are not required by a scenario. An application of the methods is presented, including a discussion of their strengths and weaknesses. Based on this work, it is concluded that the vector method is the best of the three presented.

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 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: none
Teacher disagreement score0.578
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.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
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.088
GPT teacher head0.295
Teacher spread0.207 · 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