Demo Data from EDBT 2026 / reviewers in the wild / expert
Genevieve Marquis
dblp:50/826
· DBLP profile ↗
2ranked-venue papers
0as first author
0since 2021 · last 1987
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1Applied, interdisciplinary, general and emerging computing · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Computer architecture, parallel and distributed computing, and storage systems
2 papers |
Embedded and real-time systems · 95% Distributed systems · 5% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Embedded and real-time systems › distributed real-time systems
distributed real-time programming |
0.0 | 2 | 1987 | RNet: A Hard Real-Time Distributed Programming System · IEEE Trans. Computers 1987 RNet: A Hard Real-Time Distributed Programming System · RTSS 1986 |
Embedded and real-time systems
real-time scheduling |
0.0 | 2 | 1987 | RNet: A Hard Real-Time Distributed Programming System · IEEE Trans. Computers 1987 RNet: A Hard Real-Time Distributed Programming System · RTSS 1986 |
Embedded and real-time systems › timing constraints
timing constraint specification |
0.0 | 1 | 1987 | RNet: A Hard Real-Time Distributed Programming System · IEEE Trans. Computers 1987 |
Distributed systems › middleware
distributed programming systems |
0.0 | 1 | 1986 | RNet: A Hard Real-Time Distributed Programming System · RTSS 1986 |
Methods — techniques the papers use, named apart from their topics
simulation · 0.0message passing · 0.0distributed programming · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1987 | RNet: A Hard Real-Time Distributed Programming SystemabstractRNet is a high-level programming system for building and executing distributed hard real-time programs. The main objective in developing RNet is to investigate how high-level programming concepts and tools can be used to simplify the real-time programming task. A distributed real-time program in RNet consists of a configuration specification that outlines the structure and real-time properties of the program, and a set of program modules written in a high-level programming language. The RNet configuration system performs a static feasibility analysis of the specifications and handles the construction, distribution, and execution of the program. A debugging and timing analysis system, currently under development and not described here, will be used to measure the real-time characteristics of network resources and the application program, and to perform a validation of the specifications via simulation. The distributed RNet kernel provides run-time support for message-passing and real-time scheduling. The RNet programming model, based on message ports having associated deadlines, provides the programmer with a direct means of expressing a variety of real-time behavioral effects in a way that can be validated. In particular, timing constraints can be used to obtain reliable event synchronization. Some properties that are considered desirable in a high-level distributed real-time programming system are identified. These address issues such as program moduilarity and reconfigurability, timing constraint specification, validation and enforcement, real-time event handling, I/O and exception handling, logical and physical structure specification, and program analysis. The degree to which RNet succeeds in possessing these properties is discussed. Michael F. Coulas, Glenn H. MacEwen, Genevieve Marquis |
IEEE Trans. Computers | 3 |
| 1986 | RNet: A Hard Real-Time Distributed Programming System
Chantal Belzile, Michael F. Coulas, Glenn H. MacEwen, Genevieve Marquis |
RTSS | 4 |