Thanks Max!
I was planning to add a more interactive interface, really similar to what
you're suggesting. I haven't gotten around to it, but hopefully, I'll have
some time to play around with that.
On Thu, Jan 8, 2015 at 4:56 PM, Maximilian Albert <
maximilian.alb...@gmail.com> wrote:
> Hi Tony,
On Thu, Jan 8, 2015 at 10:30 PM, Maximilian Albert
wrote:
> Hi Nathaniel,
>
>>
>> > Basically, it allows you to pick the start/end color of a colormap from
>> > two
>> > cross sections in CIELab space and interpolates those colors linearly
>> > (see
>> > the README file for more details).
>>
>> Th
Hi Tony,
This is awesome. Great work!
I was wondering, is there an easy way to cycle through all available styles
for a given plot? For instance, clicking on the top left plot displays a
maximized image of the "bmh" style. It would be great if one could press
arrow-down (say) to cycle through th
Hi Federico,
Thanks for trying it out and for the feedback!
Indeed, I started out writing a simple IPython notebook along the lines you
suggested, with just a couple of sliders and plots, but it quickly became
too slow and unwieldy for quick explorations, hence the slightly more
elaborate GUI.
I
Let's say we want a time zone aware date time converter. The basic goal is to
convert some input type (datetime) to the MPL internal type (float days past
Jan 0, 0001). We also need to tell MPL how to format the axis (default
formatter, locator, limits, label).
- The convert() method takes
I was hoping for something a bit more extensive of the intenals. I have
tried to understand the units code a couple of times now and always hit a
brick wall.
On Thu Jan 08 2015 at 2:07:02 PM Drain, Theodore R (392P) <
theodore.r.dr...@jpl.nasa.gov> wrote:
> Google search "matplotlib units" yiel
Google search "matplotlib units" yields:
http://matplotlib.org/api/units_api.html
So it sounds like the update is to make MPL's internal date system higher
resolution which would be great. We would just need to update our converters
to convert to that format instead of the current floating
One of the other driving factors to over-haul the default date handling is
that floats do not have enough precision to deal with nano-second
resolution data (which is what I think drove pandas to use datetime64).
It sounds like the correct solution
Is the unit framework documented anywhere and ar
I agree w/ the original poster that it would help to have a MEP to clearly
define what the goals of the overhaul are
Something else to keep in mind: we at least don't normally plot dates in
"earth" based time systems. ~10 years ago we contracted with John Hunter to
add the arbitrary unit sys
On Tue, Jan 6, 2015 at 2:37 AM, Maximilian Albert
wrote:
> Happy new year everyone!
>
> Apologies for the long silence. I was snowed in with work before Christmas
> and then mostly cut off from the internet for the past two weeks.
> Fortunately, I had a chance over the holidays to flesh out the GU
Nice job.
I find your GUI a little bit confusing (new to colormap stuff) but I
like the idea, basically I find it overkill, I would replace the gui
by a plot and a couple of slider widgets something simpler to
integrate without new dependencies.
Do you really need the third 3d plot on the right?
On Thu, Jan 8, 2015 at 7:04 AM, Skip Montanaro wrote:
> I'm real naive about this stuff, but I have always wondered why
> matplotlib didn't just use datetime objects, or at least use
> timezone-aware datetime objects as an "interchange" format to get the
> timezone stuff right.
>
Time zone handl
I'm real naive about this stuff, but I have always wondered why
matplotlib didn't just use datetime objects, or at least use
timezone-aware datetime objects as an "interchange" format to get the
timezone stuff right.
Skip
---
13 matches
Mail list logo
