Formal description of the ADT model of files using RTPA
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.
Bibliographic record
Abstract
An abstract data type (ADT) is an abstraction of a data structure that specifies what information can be stored in the ADT and what operations can be done on/by the ADT. The file as a common type plays a primordial role in software system development since it provides a means for manipulating large volumes of information and persistent data. However, the file ADT has not been given a formal semantics. Access to data stored in an ADT is through its interfaces. These interfaces and the operations that they represent should be rigorously defined so as to guarantee that their use will give expected results. This paper illustrates the use of real-time process algebra (RTPA) to formally describe both the data and operations of the file ADT. The difficulties in the file ADT specification are the formal description of its logical and physical models. The logical model of the file ADT is modeled using an indexing mechanism in which each record stored in the file is accessed through its address. The formal model is used in the file management system of RTOS+, a novel real-time operating system developed by the authors. RTPA has been found a very useful notation for describing the behavior of software systems.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it