MétaCan
Menu
Back to cohort
Record W2014020629 · doi:10.1017/s0890060400145068

SEED-Config: A case-based reasoning system for conceptual building design

2000· article· en· W2014020629 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

VenueArtificial intelligence for engineering design analysis and manufacturing · 2000
Typearticle
Languageen
FieldComputer Science
TopicAI-based Problem Solving and Planning
Canadian institutionsConcordia University
Fundersnot available
KeywordsComputer scienceConceptual designAdaptation (eye)Generative DesignProcess (computing)Representation (politics)Task (project management)Case-based reasoningObject (grammar)Knowledge representation and reasoningHuman–computer interactionDecompositionSoftware engineeringArtificial intelligenceInformation retrievalSystems engineeringProgramming languageEngineering

Abstract

fetched live from OpenAlex

A case-based design functionality is a natural and intuitive addition to a design tool that can augment human capabilities and help designers remember and retrieve appropriate cases. SEED-Config, a design environment for conceptual building design, was developed to incorporate a case-based reasoning functionality to provide designers with initial potential solutions. The case representation in SEED-Config is the BENT information model, which records design knowledge, supports the hierarchical decomposition of design cases, offers multiple views, and encapsulates the outcome of the design in addition to the problem specification and the design solution. The case library was implemented in an object-oriented database management system to accumulate cases automatically and to provide efficient query facilities. The case retrieval aspect of SEED-Config offers three different methods to find the most useful cases stored in the case library: task-based, lineage-based, and customized. Case retrieval responds to the exploratory nature of the design process and supports versatile case retrieval by providing multiple paths to each case. The case adaptation aspect, which adjusts the selected case to the new problem to provide a complete solution, uses an adaptation method called derivational replay. The case-based design capabilities are completely integrated within the design environment from which the cases originate.

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: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.583
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.0010.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.037
GPT teacher head0.251
Teacher spread0.213 · 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