|
Boost : |
From: Eric Niebler (eric_at_[hidden])
Date: 2008-01-31 11:15:45
Neal Becker wrote:
> Eric Niebler wrote:
>
>> Matthias Troyer wrote:
>>> On 30 Jan 2008, at 08:26, Neal Becker wrote:
>>>> I don't think that helps. How can I specify apriori the number of
>>>> bins and the min and max? AFAICT, the above would let me do this
>>>> by forcing in some fake data, that has the effect of filling the
>>>> cache and thus setting num_bins, min, max, but is has the side
>>>> effect of causing that data to effect the histogram - which is not
>>>> what I need.
>>>>
>>>> Unless I misunderstand, we need another (simpler) class "histogram"
>>>> that implements just this simpler behavior. Perhaps density could
>>>> be build on top of it?
>>> It would indeed be nice to be able to explicitly specify the min and
>>> max for the bins and I guess that should not be too hard to do.
>>> Eric, what do you think?
>> Sounds reasonable. I'm super-busy at the moment getting proto ready for
>> its upcoming review. I can add this to the list, or someone (Neal?) can
>> submit a patch which I would gladly accept.
>
> I haven't gotten it working - I haven't learned about boost::parameter yet.
> Someone familiar with that could probably finish this quickly. Here is
> what I have so far:
<snip>
I took Matthias' suggestion above to mean he thought the density
accumulator could be given additional "min" and "max" constructor
parameters, not that we need a whole new accumulator. Matthias, was that
what you were suggesting? I'd rather go that route.
-- Eric Niebler Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk