Difference between revisions of "Applications/Sparsehash"

From HPC
Jump to: navigation , search
(Created page with "__TOC__ ==Application Details== * Description: OSMesa is used since Octave 4.0 for offscreen rendering from OpenGL toolkits FLTK and Qt. * Version: 2016-12-21 (compiled with...")
 
m
Line 18: Line 18:
 
* dense_hash_map
 
* dense_hash_map
 
* dense_hash_set
 
* dense_hash_set
 +
  
 
In addition to the hash-map (and hash-set) classes, there's also a lower-level class that implements a "sparse" array.  This class can be useful in its own right; consider using it when you'd normally use a sparse_hash_map, but your keys are all smallish integers.
 
In addition to the hash-map (and hash-set) classes, there's also a lower-level class that implements a "sparse" array.  This class can be useful in its own right; consider using it when you'd normally use a sparse_hash_map, but your keys are all smallish integers.
  
 
===Example===
 
===Example===
 +
  
 
<pre style="background-color: #000000; color: white; border: 2px solid black; font-family: monospace, sans-serif;">
 
<pre style="background-color: #000000; color: white; border: 2px solid black; font-family: monospace, sans-serif;">

Revision as of 15:30, 19 April 2017

Application Details

  • Description: OSMesa is used since Octave 4.0 for offscreen rendering from OpenGL toolkits FLTK and Qt.
  • Version: 2016-12-21 (compiled with gcc)
  • Modules: sparsehash/2016-12-21/gcc-4.9.3
  • Licence: Github, open-source

Usage

The sparsehash package consists of two hashtable implementations: sparse, which is designed to be very space efficient, and dense, which is designed to be very time efficient. For each one, the package provides both a hash-map and a hash-set, to mirror the classes in the common STL implementation.

These classes are:

  • sparse_hash_map
  • sparse_hash_set
  • dense_hash_map
  • dense_hash_set


In addition to the hash-map (and hash-set) classes, there's also a lower-level class that implements a "sparse" array. This class can be useful in its own right; consider using it when you'd normally use a sparse_hash_map, but your keys are all smallish integers.

Example

[username@login01 ~]$ module add  sparsehash/2016-12-21/gcc-4.9.3


Further Information

Icon home.png