Re: [gsoc2020] Answer to histogram design questions from Slack

From: Debabrata Mandal (mandaldebabrata123_at_[hidden])
Date: 2020-06-09 14:31:20

Pardon the error in the link, ->
https://lists.boost.org/boost-gil/2020/06/0441.php
Thanks.
Deb

On Tue, Jun 9, 2020 at 7:58 PM Debabrata Mandal <
mandaldebabrata123_at_[hidden]> wrote:

> I want to make some additions to the previous post.
> 1. I believe unordered_map should be used instead of vector/array, since
> apart from the many problems of using a vector/array we cannot give an O(1)
> guarantee on every access (due to resizing) which was the primary reason we
> wanted to use it.
> 2. We should provide the support for multi dimensional storage (upto 3
> dims) for this class, since anyways if we decide to make a Matrix class for
> GIL (in the future), this histogram class would become redundant.
>
> Some doubts that I had posted on the slack group as well :
>
> I was wondering if we should go for aggregation instead of inheritance as
> mentioned in the mail
> <https://slack-redir.net/link?url=https%3A%2F%2Flists.boost.org%2Fboost-gil%2F2020%2F06%2F0441.php&v=3>.
> The primary reason being I also want to add a bunch of histogram algorithms
> like mean, normalize, etc. Also I wanted to provide an overloaded
> operator() for multi-dimensional element access.
> The plus point in inheriting is that we get control over the hash function
> used, but then we could also use an alternative method of creating our
> method of hashing a tuple to a unique key and then use hashed key (which we
> can do in aggregation).
>
> Please correct me if I am wrong.
> Thanks.
> Deb
>