MétaCan
Menu
Back to cohort
Record W1980348251 · doi:10.1017/s0269888912000434

itSIMPLE: towards an integrated design system for real planning applications

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

VenueThe Knowledge Engineering Review · 2013
Typearticle
Languageen
FieldComputer Science
TopicAI-based Problem Solving and Planning
Canadian institutionsCanada Research ChairsUniversity of TorontoUniversity of New Brunswick
FundersConselho Nacional de Desenvolvimento Científico e TecnológicoCoordenação de Aperfeiçoamento de Pessoal de Nível Superior
KeywordsComputer scienceUnified Modeling LanguageProcess (computing)Software engineeringDomain (mathematical analysis)Systems engineeringEngineering design processPetri netEngineeringProgramming language

Abstract

fetched live from OpenAlex

Abstract Since the end of the 1990s, there has been an increasing interest in the application of artificial intelligence (AI) planning techniques to solve real-life problems. In addition to characteristics of academic problems, such as the need to reason about actions, real-life problems require detailed knowledge elicitation, engineering, and management. A systematic design process in which Knowledge and Requirements Engineering tools play a fundamental role is necessary in such applications. One of the main challenges in such design process, and consequently in the study of Knowledge Engineering in AI planning, has been the analysis of requirements and their subsequent transformation into an input-ready model for planners. itSIMPLE is a research project dedicated to the study of a project process to support the design phases of real-life planning models. In this paper, we give an overview of itSIMPLE focusing on the main translation processes among a minimal set of representations: from requirements represented in Unified Modeling Language (UML) to Petri Nets and from UML models to planning domain definition language for problem solving.

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

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.0010.000
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.042
GPT teacher head0.290
Teacher spread0.248 · 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