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

From: Pranam Lashkari (plashkari628_at_[hidden])
Date: 2020-05-13 12:54:48

On Wed, May 13, 2020 at 6:13 PM Mateusz Loskot <mateusz_at_[hidden]> wrote:

>
> By asking some questions I did not suggest they should be answered now.
> I just hoped to direct the thinking/discussion towards quite obvious
> conclusion:
> - do not focus on unnecessary stuff (e.g. controlling details of of
> histogram)
> - focus on what we know to start prototyping/implementing early
> - start from easy to complex
>
> Obviously, solving a problem for a single channel is easier than
> solving it for multiple channels and dimensions.
>

On the other hand, I forgot to mention things related to boost.histogram.
In my opinion, we should use it only if we are going to use it
permanently(not a lifetime but a long time, you know what I mean). It may
make our work a little simple for now, but if we are gonna remove it
eventually and we know it at the point then why to use it now? it just
increases the workload for the future.

This is just my opinion I may be wrong(i.e starting all the histogram and
container both from scratch may be more work for now than removing
boost.histogram in future)

-- 
Thank you,
Pranam Lashkari