[MSNoise] Some little things and one question about data from more than one network.

Fri Oct 3 17:13:57 UTC 2014

Hi Kasper, Tomas and MSNoise users,

I think I had the same problem and it's more related to Obspy than to
MSNoise. I did not have time to do some tests to narrow the cause but I
think it was related to the fact that in my data folder I had two files
corresponding to the same station and the same day of data but with two
different location codes.

IF you rerun s03compute_cc.py after this error, it will jump to the next
job. It's a dirty quick fix and it does not help if the error happens every
two days of data...

Aurelien

2014-10-03 3:49 GMT-04:00 Kasper van Wijk <k.vanwijk at auckland.ac.nz>:

> Tom, as you suggested, the problem may be bigger than file names/ networks.
> Here's the output after changing to the NZ network name of our extra
> station to match that of the rest of the stations. Both are mseed data
> types:
>
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File
>
> "/usr/lib/python2.7/site-packages/spyderlib/widgets/externalshell/sitecustomize.py",
> line 540, in runfile
> execfile(filename, namespace)
> File "/home/devora/Test/s03compute_cc.py", line 214, in <module>
> stream.merge(fill_value=0)
> File "/usr/lib64/python2.7/site-packages/obspy/core/stream.py", line 1715,
> in merge
> self._mergeChecks()
> File "/usr/lib64/python2.7/site-packages/obspy/core/stream.py", line 1660,
> in _mergeChecks
> raise Exception(msg)
> Exception: Can't merge traces with same ids but differing data types!
>
> On 3 October 2014 20:27, Thomas Lecocq <thomas.lecocq at oma.be> wrote:
>
> > Dear Kasper,
> >
> > Le 02/10/2014 23:38, Kasper van Wijk a écrit :
> > > Dear Tom et al.,
> > >
> > > I am working with a student to replicate the install of MSNOISE for the
> > > Auckland Volcanic Field. Below are a few things we have ran into:
> > >
> > > 1.
> http://msnoise.org/doc/workflow.html#module-MSNoise.s001configurator
> > > misses the explicit call to start the configurator:  python
> > > s001configurator.py
> > >
> > > (this is obvious to anyone who has used MSNOISE before, but stumped the
> > > aforementioned new student)
> > I've updated the documentation, thanks !
> > >
> > > 2. On CENTOS linux, I have an issue with sqlalchemy. The "fix" is as
> ugly
> > > as it is mysterious:
> > >
> > >
> >
> http://stackoverflow.com/questions/14600530/cant-import-from-sqlalchemy-ext-declarative
> > Well, this looks strange indeed, but good to know, I'll make a new
> > "Troobleshooting" section in the doc !
> > >
> > > 3. We have a font problem (which I don't know how to fix), but starting
> > the
> > > configurator, we get the attached warning. Just a warning, though.
> > Never seen this before... probably somehow specific to paranoid-CentOS
> > ... :)
> > >
> > > 4. Is it correct that sqlite can only work on one thread?
> > >
> > > [devora at localhost MSNoise-master]$ python s01scan_archive.py --init
> -t 2
> > > 2014-08-22 10:14:13,724 [INFO] *** Starting: Scan Archive ***
> > > 2014-08-22 10:14:13,727 [INFO] Initializing (should be run only once)
> > > 2014-08-22 10:14:13,727 [INFO] You can not work on 2 threads because
> > SQLite
> > > only supports 1 connection at a time
> > > 2014-08-22 10:14:13,727 [INFO] Will work on 1 threads
> >
> > Well, in "theory", it could work on more than one thread, but there is a
> > very big risk of problems, because SQLite can only accept one
> > transaction at a time, so if two process try to insert, update (...) in
> > the DB at the same time, you'll get a "Cannot insert, database locked"
> > and the data will be lost...
> >
> > >
> > > 5. And this is where are currently: we imported a station into our NZ
> > > network with a different network name. This resulted in errors when
> > pairing
> > > the AK station with an NZ station. What should we do? After getting an
> > > error, we tried renaming the AK data to NZ to be consistent, but we are
> > > unable to cleanly perge the AK info in the database. Alternatively, can
> > we
> > > set up two networks in the configurator?
> >
> > Are you trying to run a second "project", independent of the AVF ? Or
> > using a NZ station for the AVF monitoring ? I don't get this.
> >
> > Renaming station files is usually not enough, if you don't rename
> > metadata within the files + update the database... I'd say it's usually
> > not worth the effort, MSNoise should be able to process data from
> > different networks... What is the error you get ?
> >
> > Best regards and thanks for using MSNoise :)
> >
> > Tom
> > >
> > > Cheers,
> > > kasper
> > >
> > >
> > > _______________________________________________
> > > MSNoise mailing list
> > > MSNoise at mailman-as.oma.be
> > > http://mailman-as.oma.be/mailman/listinfo/msnoise
> >
> > _______________________________________________
> > MSNoise mailing list
> > MSNoise at mailman-as.oma.be
> > http://mailman-as.oma.be/mailman/listinfo/msnoise
> >
> _______________________________________________
> MSNoise mailing list
> MSNoise at mailman-as.oma.be
> http://mailman-as.oma.be/mailman/listinfo/msnoise
>

-- 
==========================

Aurelien Mordret

Postdoctoral fellow
Department of Earth, Atmospheric and Planetary Sciences
Massachusetts Institute of Technology
54-526
Cambridge, MA  02139-4307
e-mail: mordret at mit.edu
web: http://web.mit.edu/mordret/www