Bibliographic record
Abstract
Abstract The wordabstractionis used as a noun, “to build an abstraction.” Its root form,abstract, is used as a verb, “to abstract the requirements to perform a domain analysis” or as an adjective, “a linked list is an abstract concept.” From the software engineering perspective, all of these uses refer to the concept of identifying essential properties while simultaneously eliminating nonessential properties. An abstraction intentionally ignores some qualities, attributes, or functions to focus attention on others. It is a summary; it covers the high points and leaves out the details. An abstraction omits all the pieces of the system that are not necessary for understanding the system at a given level of detail. The abstraction includes only the relevant aspects of the object. The selection of what to include and what to exclude in a good abstraction is based on knowledge of the problem, the needs of the moment, and experience. A proper combination of these considerations leads to a good abstraction. The purpose of creating abstractions is to concentrate on one aspect of the problem and to preclude distraction by other parts of the problem. Level of abstraction is a quality that deals with the amount of detail in this view of a system. The process of abstraction has also been referred to as chunking. In this context, one abstraction represents one chunk of information. Encapsulation is the process of separating and hiding the external (user's) view of an abstraction from the internal (implementer's) view of the abstraction. There are three fundamental abstractions in terms of which all software can be described. A complete design must include all three. They are data, function, and process. These are discussed.
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.003 | 0.012 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.003 | 0.002 |
| Scholarly communication | 0.009 | 0.010 |
| Open science | 0.003 | 0.009 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.184 | 0.106 |
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".