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(a)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…
> 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@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(a)mailman-as.oma.be
> > http://mailman-as.oma.be/mailman/listinfo/msnoise
>
> _______________________________________________
> MSNoise mailing list
> MSNoise(a)mailman-as.oma.be
> http://mailman-as.oma.be/mailman/listinfo/msnoise
>
Dear all,
Someone can explain me in which way I can populate in the configurator the filters tab?? When I try to start cross correlation give me this error message: 'NO FILTERS DEFINED, exiting'. what it means? thank you very much and I hope to find a solution as soon as possible.
cheers,
Carmelo
The University of Aberdeen is a charity registered in Scotland, No SC013683.
Tha Oilthigh Obar Dheathain na charthannas clàraichte ann an Alba, Àir. SC013683.
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)
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…
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.
4. Is it correct that sqlite can only work on one thread?
[devora@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
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?
Cheers,
kasper
Dear MSNoise users,
You might have noticed I am working on the codes, and updating the
"branches" of the GitHub repository.
I just wanted to remind you all that, except if you're really reckless,
you should only use "Releases" versions of the code.
The releases are available here :
https://github.com/ROBelgium/MSNoise/releases
to be sure, always download the "Lastest" :
https://github.com/ROBelgium/MSNoise/releases/latest
The branches (tests, msnoise-admin, etc) and the 'master' branch are
often updated with code that is not yet fully tested or complete, and so
could not work. I have started writing unit tests for the code, so, in a
near future, one could just look at the "Build Status" of TravisCI (CI
stands for Continuous Integration) to check if all is OK to test the
"master" instead of "Releases" !
Best regards from Brussels
Thomas
ps: as always, if you use MSNoise, please let me/us know! Certainly if
you had/have problems ! If you think something would be useful for
others, submit ideas/issues/suggestions to the
https://github.com/ROBelgium/MSNoise/issues !
--
Dr. Thomas Lecocq
Geologist
Seismology - Gravimetry
Royal Observatory of Belgium
*
* * * * *
* * * *
---------
http://www.seismology.behttp://twitter.com/#!/Seismologie_be