MétaCan
Menu
Back to cohort
Record W4382866947 · doi:10.1609/icaps.v33i1.27203

On Using Action Inheritance and Modularity in PDDL Domain Modelling

2023· article· en· W4382866947 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.

fundA Canadian funder is recorded on the work.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueProceedings of the International Conference on Automated Planning and Scheduling · 2023
Typearticle
Languageen
FieldComputer Science
TopicModel-Driven Software Engineering Techniques
Canadian institutionsnot available
FundersSocial Sciences and Humanities Research Council of CanadaUK Research and Innovation
KeywordsComputer scienceModularity (biology)Inheritance (genetic algorithm)Programming languageSoftware engineeringCode reuseDomain (mathematical analysis)Artificial intelligenceSoftware

Abstract

fetched live from OpenAlex

The PDDL modelling problem is known to be challenging, time consuming and error prone. This has led researchers to investigate methods of supporting the modelling process. One particular avenue is to adapt tools and techniques that have proven useful in software engineering to support the modelling process. We observe that concepts, such as inheritance and modularity have not been fully explored in the context of modelling PDDL planning models. Within software engineering these concepts help to organise and provide structure to code, which can make it easier to read, debug, and reuse code. In this work we consider inheritance and modularity and their use in PDDL action descriptions, and how these can have a similar impact on the PDDL modelling process. We define an extension to PDDL and develop appropriate tools to compile models using these extensions, both directly from the command line and through the Visual Studio Code PDDL extension. We report on our use of inheritance and modularity when modelling a planning model for a companion robot scenario. We also discuss the benefits of exploiting the inheritance hierarchy in other modules within our robot system.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.545
Threshold uncertainty score0.442

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.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.090
GPT teacher head0.317
Teacher spread0.227 · 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