<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<title>Conferencias</title>
<link href="http://dspace.infodocu.lbd.org.es/xmlui/handle/123456789/1369" rel="alternate"/>
<subtitle>Conferencias relacionadas con Estructuras de Datos</subtitle>
<id>http://dspace.infodocu.lbd.org.es/xmlui/handle/123456789/1369</id>
<updated>2026-05-22T19:52:30Z</updated>
<dc:date>2026-05-22T19:52:30Z</dc:date>
<entry>
<title>Bitvectors with runs and the successor/predecessor problem</title>
<link href="http://dspace.infodocu.lbd.org.es/xmlui/handle/123456789/1398" rel="alternate"/>
<author>
<name>Gómez-Brandón, Adrián</name>
</author>
<author>
<name>R. Brisaboa, Nieves</name>
</author>
<id>http://dspace.infodocu.lbd.org.es/xmlui/handle/123456789/1398</id>
<updated>2025-10-20T10:47:52Z</updated>
<published>2020-01-01T00:00:00Z</published>
<summary type="text">Bitvectors with runs and the successor/predecessor problem
Gómez-Brandón, Adrián; R. Brisaboa, Nieves
The successor and predecessor problem consists of obtaining the closest value in a set&#13;
of integers, greater/smaller than a given value. This problem has interesting applications,&#13;
like the intersection of inverted lists. It can be easily modeled by using a bitvector of size n&#13;
and its operations rank and select. However, there is a practical approach [1], which keeps&#13;
the best theoretical bounds, and allows to solve successor and predecessor more efficiently.&#13;
Based on that technique, we designed a novel compact data structure for bitvectors with k&#13;
runs that achieves access, rank, and successor/predecessor in O(1) time by consuming space&#13;
O(&#13;
√&#13;
kn) bits. In practice, it obtains a compression ratio of 0.04% − 26.33% when the runs&#13;
are larger than 100, and becomes the fastest technique, which considers compressibility,&#13;
in successor/predecessor queries. Besides, we present a recursive variant of our structure,&#13;
which tends to O(k) bits and takes O(log n&#13;
k ) time.
</summary>
<dc:date>2020-01-01T00:00:00Z</dc:date>
</entry>
</feed>
