You've already done it. But we encourage you to take a crack at it. I would
suggest just first factoring it out into a new file
lib/matplotlib/hexbin.py and have the current function utilize it. When
that is done, we can look to getting it into numpy as well. We will need a
copy of it ourselves for
A thats too bad (that we can't recover the original ids.)
What could one (as user) do to officially request it be fixed/factored out
to numpy?
On Fri, Jan 29, 2016 at 7:30 PM, Thomas Caswell wrote:
> Factor it out and give it to numpy!
>
> On Fri, Jan 29, 2016, 17:27 Benjamin Root wrote:
Factor it out and give it to numpy!
On Fri, Jan 29, 2016, 17:27 Benjamin Root wrote:
> Hmm, you are right, there is no way to get back the information that
> hexbin computed. The hexbin function is massive (in
> lib/matplotlib/axes/_axes.py) and is a bit tangled up with the
> artist-handling cod
Hmm, you are right, there is no way to get back the information that hexbin
computed. The hexbin function is massive (in lib/matplotlib/axes/_axes.py)
and is a bit tangled up with the artist-handling code, too. I think it
would make sense to factor out the hexbinning component into its own
hexbin.p
Is there a simple way to hexbin using "pyplot.hexbin" and to return the ids
of the set of
points in each hexbin? That is to output an array of n elements
(one for each hexbin), and each element itself an array with the point ids?
The sum
of the number of inner elements would be equal the sum of all
