I have been doing quite a bit of work collecting data over
periods of days and weeks, an have started working on a
partitioner which produces nice looking time axes in PyX. I
am attaching the code, which should take very much
massaging to include in the main PyX distribution, if you
think this would be useful (I do). In the near future, I will
probably implement another partioner useful for data
extending over months & years (which will create non-
uniform partitions with ticks at real month boundaries,
A sample of a web page which is being updated with this is:
which shows some environmental data from our building.
Note that to get the most current graphs, you have to click
the 'update graphs' button, then go back to the original
page and refresh it. We are still developing the website, so
it is a little crude in the mechanistics.
Note that becasue of the way I have declared the format
strings as class globals, it is very easy to override the
formatting. The small sample subclass michaeltimepart is
the one being used on the webpage. The main difference
in this case is the slash in the month/day spec.
I prefer this method for handling variations to including all
possible information in the arguments to the constructor,
since python subclassing is so easy. If you would rather
handle format variations as arguments, the changes are
easy. Maybe the best bet would be to have format string
as arguments defaulted to None, in which case the class
defaults arre used, but if non-None formats are given, they
override the class defaults. This would allow both
Log in to post a comment.