Demo Data from VLDB 2026 / reviewers in the wild / expert
William S. Beebee
dblp:46/5700
· DBLP profile ↗
3ranked-venue papers
0as first author
0since 2021 · last 2004
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 2Applied, 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.
| Software engineering, system software, and programming languages
1 paper |
Programming languages and type systems · 40% Runtime systems and virtual machines · 40% Operating systems · 20% | |
| Computer architecture, parallel and distributed computing, and storage systems
2 papers |
Embedded and real-time systems · 37% Memory systems · 37% Distributed systems · 13% | |
| Interdisciplinary, comprehensive, and emerging computing
1 paper |
Bioinformatics and computational biology · 100% | |
| Network and information security
1 paper |
Systems and software security · 100% |
Topics — the 11 heaviest of 12, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Runtime systems and virtual machines
garbage collection |
0.0 | 1 | 2003 | Ownership types for safe region-based memory management in real-time Java · PLDI 2003 |
Programming languages and type systems › type systems
ownership types |
0.0 | 1 | 2003 | Ownership types for safe region-based memory management in real-time Java · PLDI 2003 |
Runtime systems and virtual machines › garbage collection
real-time garbage collection |
0.0 | 1 | 2003 | Ownership types for safe region-based memory management in real-time Java · PLDI 2003 |
Operating systems › resource management › memory management
region-based memory management |
0.0 | 1 | 2003 | Ownership types for safe region-based memory management in real-time Java · PLDI 2003 |
Programming languages and type systems
type systems |
0.0 | 1 | 2003 | Ownership types for safe region-based memory management in real-time Java · PLDI 2003 |
Embedded and real-time systems › real-time programming languages
real-time java |
0.0 | 1 | 2003 | Ownership types for safe region-based memory management in real-time Java · PLDI 2003 |
Memory systems › memory management
region-based memory management |
0.0 | 1 | 2003 | Ownership types for safe region-based memory management in real-time Java · PLDI 2003 |
Bioinformatics and computational biology › genome annotation › gene prediction
exon prediction |
0.0 | 1 | 1999 | A dictionary based approach for gene annotation · RECOMB 1999 |
Bioinformatics and computational biology › genome annotation
gene annotation |
0.0 | 1 | 1999 | A dictionary based approach for gene annotation · RECOMB 1999 |
Distributed systems
fault tolerance |
0.0 | 1 | 2004 | Enhancing Server Availability and Security Through Failure-Oblivious Computing · OSDI 2004 |
Hardware reliability and fault tolerance
memory fault tolerance |
0.0 | 1 | 2004 | Enhancing Server Availability and Security Through Failure-Oblivious Computing · OSDI 2004 |
Methods — techniques the papers use, named apart from their topics
static type system · 0.1homology determination · 0.0dictionary lookup · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2004 | Enhancing Server Availability and Security Through Failure-Oblivious Computing
Martin C. Rinard, Cristian Cadar, Daniel Dumitran, Daniel M. Roy 0001, Tudor Leu, William S. Beebee |
OSDI | 6 |
| 2003 | Ownership types for safe region-based memory management in real-time JavaabstractThe Real Time Specification for Java (RTSJ) allows a program to create real-time threads with hard real-time constraints. Real-time threads use region-based memory management to avoid unbounded pauses caused by interference from the garbage collector. The RTSJ uses runtime checks to ensure that deleting a region does not create dangling references and that real-time threads do not access references to objects allocated in the garbage-collected heap. This paper presents a static type system that guarantees that these runtime checks will never fail for well-typed programs. Our type system therefore 1) provides an important safety guarantee for real-time programs and 2) makes it possible to eliminate the runtime checks and their associated overhead.Our system also makes several contributions over previous work on region types. For object-oriented programs, it combines the benefits of region types and ownership types in a unified type system framework. For multithreaded programs, it allows long-lived threads to share objects without using the heap and without memory leaks. For real-time programs, it ensures that real-time threads do not interfere with the garbage collector. Our experience indicates that our type system is sufficiently expressive and requires little programming overhead, and that eliminating the RTSJ runtime checks using a static type system can significantly decrease the execution time of real-time programs. Chandrasekhar Boyapati, Alexandru Salcianu, William S. Beebee, Martin C. Rinard |
PLDI | 3 |
| 1999 | A dictionary based approach for gene annotationabstractThis paper describes a fast and fully automated dictionary based approach to gene annotation and exon prediction. Two dictionaries are constructed, one from the nonredundant protein OWL database and the other from the dbEST database. These dictionaries are used to obtain O(1) time lookups of tuples in the dictionaries (4 tuples for the OWL database and 11 tuples for the \ndbEST database). These tuples can be used to rapidly find the longest matches at every position in an input sequence to the database sequences. Such matches provide very useful information pertaining to locating common segments between exons, alternative splice sites, and frequency data of long tuples for statistical purposes. These dictionaries also provide the basis for both homology determination, and statistical approaches to exon prediction. For instance, using the OWL protein database on a benchmark test set of 130 genes, and after removing sequences from the database with exact amino acid homology to genes in our test set, we find 88% of coding nucleotides, and 99% of our predictions of coding nucleotides are correct. Also, 81% of coding exons are predicted exactly, while 82% of our predictions of exons agree exactly with the published annotation of their genes. Lior Pachter, Serafim Batzoglou, Valentin I. Spitkovsky, William S. Beebee, Eric S. Lander, Bonnie Berger, Daniel J. Kleitman |
RECOMB | 4 |