logout by plotting

When plotting a large number of traces, e.g. 63, the plot command causes my system to logout. Although plotting such a high number of traces seem awkward, an error message would be prefered instead of logging out from my PC.

Here is my code:



st[0:63].plot(color='black', tick_format='%I:%M:%S %p',handle=True,equal_scale=False)


Hi Dirk,

this is probably better tracked as an issue at github. To try and
reproduce we would also need more information on your system (OS, RAM
etc.) and also the data to reproduce (make available for download
somewhere or send me per private mail).


Dear All;
I run into a problem when using the seisSim function from obspy in a MacOSX 10.9 machine, don’t know if the problem is the version I am using, which was downloaded from macports recently.
The following is the error I get and I don’t know how to interpret it:

/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/oldnumeric/__init__.py:11: ModuleDeprecationWarning: The oldnumeric module will be dropped in Numpy 1.9
  warnings.warn(_msg, ModuleDeprecationWarning)
Traceback (most recent call last):
  File "/Users/javier/bin/rd.py", line 72, in <module>
  File "/Users/javier/bin/rd.py", line 40, in main
    tr.data = seisSim(tr.data,tr.stats.sampling_rate,paz_remove=None,remove_sensitivity=True,pre_filt=(fl1,fl2,fl3,fl4),seedresp=seedresp)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/obspy/signal/invsim.py", line 485, in seisSim
KeyError: 'network'

Thank you in advance for any clue;

Javier Francisco Pacheco

This is something that could be fixed.. in one way or the other. So feel
free to open a ticket for this issue.
But.. it's connected to an earlier fix related to making sure to safely
look up correct Network/Station/Location/Channel from the provided RESP
file (see #686).

However, actually, in your case there is no reason whatsoever to use the
low-level routine seisSim(). If possible at all, always stick to the
high-level routines, in this case Stream/Trace.simulate(). They are
there for a reason. In this case they automatically supply evalresp with
all the correct Network/Station/Location/Channel information from each
trace's stats (also.. each trace's sampling rate gets filled in internally).