Dayplot error when giving the events argument

[QuLogic]

I am giving the events argument to generate the dayplot with events labeled on the plot, but it gave me the following error, looking into the waveform.py, it seems this check should be checked when the code automatically download the Catalog object (when using events={"min_magnitude": 5.5}) instead of manually giving the time of the events.

st.plot(type = 'dayplot', events=[{"time": UTCDateTime("2014-03-29T04:09:42"), "text": "M 5.1"}])

/Library/Python/2.7/site-packages/obspy/imaging/waveform.pyc in _plotEvent(self, event)
    573                 markersize=12, linewidth=self.linewidth)
    574 
--> 575         for pick in event.picks:
    576             # check that network/station/location matches
    577             if pick.waveform_id.getSEEDString().split(".")[:-1] != \

AttributeError: 'dict' object has no attribute 'picks'

[barsch]

st = read("http://examples.obspy.org/GR.BFO..LHZ.2012.108")
st.plot(type = 'dayplot', events=[{"time": UTCDateTime("2014-03-29T04:09:42"), "text": "M 5.1"}])

works for me as expected on master - in order to fix this I need more details - e.g. python version, obspy version, input data

[QuLogic]

Your example actually fails with a different error on master now (maybe Py 3 problem?):

obspy/imaging/waveform.py in plotDay(self, *args, **kwargs)
    445         self.axis = [ax]
    446         # Set ticks.
--> 447         self.__dayplotSetYTicks(*args, **kwargs)
    448         self.__dayplotSetXTicks(*args, **kwargs)
    449         # Choose to show grid but only on the x axis.

obspy/imaging/waveform.py in __dayplotSetYTicks(self, *args, **kwargs)
   1082             ticks -= 0.5
   1083         else:
-> 1084             tick_steps = list(range(0, intervals, self.repeat))
   1085             ticks = np.arange(intervals, 0, -1 * self.repeat, dtype=np.float)
   1086             ticks -= 0.5

TypeError: 'float' object cannot be interpreted as an integer

[QuLogic]

I've added two tests for day plots; one plain, one with an event. I've also fixed the bug indicated by the reporter. However, the error I found above is not fixed yet, since it doesn't seem to be triggered by the example I used.

This will probably fail due to a bug in python-future (PythonCharmers/python-future#76). There are also some warnings due to a bug in matplotlib (matplotlib/matplotlib#3271).

[QuLogic]

One more test for plotting events with a catalog. However, I'm pretty sure that plotting events is actually broken here. Things seem to end up on the wrong line at times. Edit: Never mind, was due to my workaround for the python-future bug. Will update reference images soon.

[krischer]

I'll merge this as soon as future 0.12.4 is released. Otherwise we would have a constantly failing build...