Bibliographic record
Abstract
The engineering design process is traditionally modelled as proceeding from the functional domain to the physical domain. Function thus represents more abstract concepts and the form or structure resulting from the design process as the more concrete. A comparison of mechanical design with process planning, however, reveals that this model does not apply to all areas of engineering design. In mechanical design, engineers select those forms they believe will perform the desired function; in process planning, engineers select those functions (i.e., machining operations) they believe will create the desired form. This reversal of form and function raises important issues concerning how engineering design should be modelled as form and function may not be as distinct as the traditional model of engineering design might suggest. This paper is an initial exploration to better understand the nature and the implications of this "reversibility". Potential benefactors of this research are computerized design tools which use form and function to aid designers. By building upon a framework which supports both the mechanical design and the process planning perspectives, the design tool promises to better serve the needs of its users.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.005 | 0.011 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.003 | 0.043 |
| Scholarly communication | 0.014 | 0.017 |
| Open science | 0.002 | 0.004 |
| Research integrity | 0.003 | 0.004 |
| Insufficient payload (model declined to judge) | 0.010 | 0.002 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".