the last time that i checked, hpcviewer used a sparse set of (sometimes) large numbers for metric indices. it should not present such numbers. if such numbers arise (perhaps while computing metrics in the viewer), we should build a bi-directional map from internal sparse metric indices to a set of dense small indices. a hash table can be used for the sparse to dense mapping. an array can map back to internal sparse metric indices if necessary.
blue42u
commented
2 years ago
the last time that i checked, hpcviewer used a sparse set of (sometimes) large numbers for metric indices. it should not present such numbers. if such numbers arise (perhaps while computing metrics in the viewer), we should build a bi-directional map from internal sparse metric indices to a set of dense small indices. a hash table can be used for the sparse to dense mapping. an array can map back to internal sparse metric indices if necessary.