MétaCan
Menu
Back to cohort
Record W3177819721 · doi:10.5957/smc-2013-t14

Topics in Development of Naval Architecture Software Applications

2013· article· en· W3177819721 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

VenueSNAME Maritime Convention · 2013
Typearticle
Languageen
FieldEngineering
TopicMaritime Navigation and Safety
Canadian institutionsDefence Research and Development Canada
Fundersnot available
KeywordsComputer scienceSoftware developmentSoftware engineeringSoftware architectureResource-oriented architectureSystems engineeringDocumentationSoftwareNaval architectureReference architectureSoftware constructionContext (archaeology)EngineeringMarine engineeringProgramming language

Abstract

fetched live from OpenAlex

Software applications are used extensively in the practice of contemporary naval architecture. This paper describes several naval architecture applications, including ship motion prediction, simulation of replenishment at sea, simulation of launch and recovery, ship operator guidance, and measurement of directional wave spectra using wave radar. Within this context, this paper describes relevant technologies and programming languages that are effective for development of naval architecture software applications. Due to the complexity of naval architecture software, discussion is given on matching of human resources to software development tasks. Software documentation, which can take several forms, is addressed. Verification and validation of software is the final major topic.

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 categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.948
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.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.006
GPT teacher head0.204
Teacher spread0.198 · 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