Formal description of a generic graph model with 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
Formal specification of abstract data types (ADTs) is important in modeling system architectures and their implementations. One of the most widely used ADTs is graph, since many problems in sciences and engineering can be formulated and solved by a graph model. In this paper, we present a formal approach to the specification of graphs as an ADT using real-time process algebra (RTPA). RTPA is a formal method that describes a software system, especially a real-time system, as a set of processes. We use RTPA to describe a generic graph model in three parts encompassing the architecture, static and dynamic behaviors. In the RTPA specification, the graph behaviors can be classified into four categories, namely: (a) basic operations (InsertNode, DeleteNode, InsertEdge, DeleteEdge, GetSize, GetNumberOfEdges, Retrieve, Update, and Search); (b) node/edge-specific operations (FindNode, FindEdge, Fanin, Fanout, FindNeighbours, and Degree); (c) pointer operations (CurrentNode and CurrentEdge); and (d) utility operations (Create, Clear, and Release). Each of the 20 operations is formally described by an RTPA processes in a unified encapsulation of graph behaviors. On the basis of the RTPA graph model, a wide range of graph-based applications can be implemented by sharing the common architecture and behaviors of the graph as a system type or class.
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