The inclusive/exclusive upper bound is not the reason why we have a mismatch in the selectvity between PartOf and inverted PartOf

Author: thomaskrause

core/src/annostorage/inmemory.rs

@@ -32,12 +32,9 @@ pub struct AnnoStorageImpl<T: Ord + Hash + Default> {
     anno_key_sizes: BTreeMap<AnnoKey, usize>,
     anno_keys: SymbolTable<AnnoKey>,
     anno_values: SymbolTable<String>,
+
     /// Sampled histograms for each annotation key .
     /// Each histogram bound defines a range of values where we estimate that they have the same number of occurences.
-    ///
-    /// If h_i the the histogram bound value at index i, the first range is defined is as [h_0, h_1), the second range from [h_1, h_2) and so on.
-    /// Thus each element marks the inclusive start of a range and an exclusive end.
-    /// **The last range \[h_n-1, h_n\] has an inclusive upper bound instead of an exclusive one!**
     histogram_bounds: BTreeMap<usize, Vec<String>>,
     largest_item: Option<T>,
     total_number_of_annos: usize,

core/src/annostorage/ondisk.rs

@@ -50,10 +50,6 @@ where
 
     /// Sampled histograms for each annotation key .
     /// Each histogram bound defines a range of values where we estimate that they have the same number of occurences.
-    ///
-    /// If h_i the the histogram bound value at index i, the first range is defined is as [h_0, h_1), the second range from [h_1, h_2) and so on.
-    /// Thus each element marks the inclusive start of a range and an exclusive end.
-    /// **The last range \[h_n-1, h_n\] has an inclusive upper bound instead of an exclusive one!**
     histogram_bounds: BTreeMap<AnnoKey, Vec<String>>,
     largest_item: Option<T>,