Hi all,
I was wondering if anyone had already implemented something like this. I'd
like to be able to select which CC pairs I calculated, instead of all
combinations. My reasoning is, I want to use this for monitoring changes
associated with a potential magma reservoir, and only want to look at ray
paths that cross the caldera.
Thanks!
-ashton
--
Ashton F. Flinders, Ph.D
U.S. Geological Survey
345 Middlefield Road
Menlo Park, CA 94025
(650) 329-5050
Hi Asthon,
So far, I think we can compute the CC with a minimum of 3 stations (Am I right Thomas?). What I did for Costa Rica was computing seismic velocity variations for selected station pairs instead of the average seismic velocity change for the whole N array. You can adapt the scripts for this...
It would be really cool if we can implement sub-arrays from the N stations and monitoring these sub-arrays and compare results.
Changing gears a bit:
** Another cool idea that I am throwing here is to implement a tool/ function that allow us to use the final Green’s functions as virtual earthquakes!! So we can perform moment tensor inversions (for instance) and make some seismic hazard analysis.
Cheers;
-Esteban
> On Oct 21, 2016, at 5:00 AM, msnoise-request(a)mailman-as.oma.be wrote:
>
> Send MSNoise mailing list submissions to
> msnoise(a)mailman-as.oma.be
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman-as.oma.be/mailman/listinfo/msnoise
> or, via email, send a message with subject or body 'help' to
> msnoise-request(a)mailman-as.oma.be
>
> You can reach the person managing the list at
> msnoise-owner(a)mailman-as.oma.be
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of MSNoise digest..."
>
>
> Today's Topics:
>
> 1. selective pairs (Flinders, Ashton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 20 Oct 2016 08:47:50 -0700
> From: "Flinders, Ashton" <aflinders(a)usgs.gov>
> To: "Python Package for Monitoring Seismic Velocity Changes using
> Ambient Seismic Noise" <msnoise(a)mailman-as.oma.be>
> Subject: [MSNoise] selective pairs
> Message-ID:
> <CAPbWHEMzu7y40649A5TesRz9i80yjn9t6KRwnAzRhUzAAP04JA(a)mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi all,
>
> I was wondering if anyone had already implemented something like this. I'd
> like to be able to select which CC pairs I calculated, instead of all
> combinations. My reasoning is, I want to use this for monitoring changes
> associated with a potential magma reservoir, and only want to look at ray
> paths that cross the caldera.
>
> Thanks!
> -ashton
>
>
> --
> Ashton F. Flinders, Ph.D
> U.S. Geological Survey
> 345 Middlefield Road
> Menlo Park, CA 94025
> (650) 329-5050
>
>
> ------------------------------
>
> _______________________________________________
> MSNoise mailing list
> MSNoise(a)mailman-as.oma.be
> http://mailman-as.oma.be/mailman/listinfo/msnoise
>
>
> End of MSNoise Digest, Vol 31, Issue 13
> ***************************************
Hi Thomas!
Is it possible to get the filtered (coherent, min error, etc) dv/v data, to plot in another way?
Saludos!
--
Sergio Morales Méndez
Profesor de Estado en Ciencias m/Física
sergio.morales(a)sernageomin.cl
@ProfeSergioM
------------------------------------------------
Grupo Sismología
Observatorio Volcanológico de los Andes del Sur - OVDAS
RNVV - SERNAGEOMIN
Rudecindo Ortega 03850
045-2270700
Temuco
Hi !
I would like to use MSNoise and was wondering if you had, in addition to the documentation on your website, a tutorial with a small dataset.
Actually, I’ve installed MSNoise on my Mac with SQLite, see the web interface but as soon as I try to create a station list I get an error message :
builtins.TypeError
TypeError: __init__() missing 8 required positional arguments: 'net', 'sta', 'X', 'Y', 'altitude', 'coordinates', 'instrument', and 'used'
I’m not very familiar with Python so I don’t know if it’s because I’ve missed something in the way I use MSNoise (parameters to change/ files to be present in the project folder…) or if it comes from the installation itself.
Thanks,
Julie
--
Julie Albaric
UMR 6249 Chrono-environnement
Université de Franche-Comté
16 route de Gray
25030 Besançon, France
Tel. +33 3 81 66 63 69
Hi all, I was just reading through Taka'aki and Forents new paper using
MSNoise, and was hoping just for a wee bit more clarification on the
MSnoise processing scheme (wasnt quite clear in the docs).
The paper says;
"We first removed the instrument response from 1-day-long waveform to
obtain ground motion in displacement. Daily displacement data were
bandpassed between 0.08 and 2.0 Hz, down-sampled into 10 Hz, and split
into 30-min-long data. Those 30-min-long data were spectral whitened in a
frequency range of 0.1–0.9 Hz and then one-bit normalized. With those
one-bit normalized data, the NCFs were computed for all possible
combinations of components. Daily NCFs were then obtained by stacking
30-min NCFs."
Q1) So just in terms of implementation in msnoise admin, the 30-min-long
duration would be controlled by "analysis_duration" correct?
Q2) If you remove the instrument response, is it always removed from a 1
day chunk, or is it removed from a chunk equal in size to
"analysis_duration"? (the docs say 1 day, but I wasnt sure if this was just
referencing the default "analysis_duration" time).
Q3) This probably isnt the intended usage, but if you used
"analysis_duration" longer than a day, would you expect things to behave?
Thanks as always!
-ashton
p.s. paper;
http://earth-planets-space.springeropen.com/articles/10.1186/s40623-016-053…
--
Ashton F. Flinders, Ph.D
U.S. Geological Survey
345 Middlefield Road
Menlo Park, CA 94025
(650) 329-5050
Thanks Thomas!
We will!
-Esteban
> On Oct 7, 2016, at 5:00 AM, msnoise-request(a)mailman-as.oma.be wrote:
>
> Send MSNoise mailing list submissions to
> msnoise(a)mailman-as.oma.be
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman-as.oma.be/mailman/listinfo/msnoise
> or, via email, send a message with subject or body 'help' to
> msnoise-request(a)mailman-as.oma.be
>
> You can reach the person managing the list at
> msnoise-owner(a)mailman-as.oma.be
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of MSNoise digest..."
>
>
> Today's Topics:
>
> 1. Re: MSNoise Digest, Vol 31, Issue 1 (VICIC BLAZ [PHD0900016])
> 2. Re: MSNoise Digest, Vol 31, Issue 1 (Thomas Lecocq)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 7 Oct 2016 05:49:18 +0000
> From: "VICIC BLAZ [PHD0900016]" <BLAZ.VICIC(a)phd.units.it>
> To: "Python Package for Monitoring Seismic Velocity Changes using
> AmbientSeismic Noise" <msnoise(a)mailman-as.oma.be>
> Subject: Re: [MSNoise] MSNoise Digest, Vol 31, Issue 1
> Message-ID:
> <VI1PR04MB1389D35A8164302922C86CB9A3C60(a)VI1PR04MB1389.eurprd04.prod.outlook.com>
>
> Content-Type: text/plain; charset="Windows-1252"
>
> Thank you on clarification of responses!
>
>
> Bla?
>
> ________________________________
> From: msnoise-bounces(a)mailman-as.oma.be <msnoise-bounces(a)mailman-as.oma.be> on behalf of Flinders, Ashton <aflinders(a)usgs.gov>
> Sent: Friday, October 7, 2016 1:16:46 AM
> To: Python Package for Monitoring Seismic Velocity Changes using AmbientSeismic Noise
> Subject: Re: [MSNoise] MSNoise Digest, Vol 31, Issue 1
>
> Thanks for all the info Thomas! I'm coming from an AN tomography
> background, so things are a little different to me, e.g. I tend to
> preprocess, whiten and do the CC over a broad band, and then do different
> narrow-band filtering on the final stacked CC to get my frequency-band
> dependent dt's.
>
> I look forward to actively contributing, so I'll be sure to push any
> problems I encounter to the github thread too.
>
> On a sidenote, is the python3 version stable, or still a work in progress?
>
> thanks again!
>
> ashton
>
> On Thu, Oct 6, 2016 at 1:30 PM, Thomas Lecocq <Thomas.Lecocq(a)seismology.be>
> wrote:
>
>> Dear All,
>>
>> small note here:
>>
>> pleaaaase, if something is not clear in the Documentation and you think
>> that, after asking your questions and getting answers from the mailing
>> list, you have suggestions to be more accurate, precise or else, don't
>> hesitate to suggest changes (via github issues, pull requests or even
>> email), it'll be beneficial to all users!
>>
>> I'm the worst person to write doc about MSNoise, because I know it too
>> well.
>>
>> Cheers
>>
>> Thomas
>>
>>
>>
>> On 06/10/2016 19:17, Esteban Chaves wrote:
>>
>>> Hi Ashton,
>>>
>>> As an active user:
>>>
>>> I highly recommend you to check the documentation:
>>> http://msnoise.org/doc/workflow.html#module-msnoise.s03compute_cc <
>>> http://msnoise.org/doc/workflow.html#module-msnoise.s03compute_cc>
>>> I think the pre-processing and processing steps are well documented in
>>> the web site.
>>>
>>> 1) Yes. It is more efficient to compute the cross-correlation functions
>>> or Green?s functions using 30-min chunks. Although you can change this
>>> feature if you will. Segments are re-build afterwards.
>>>
>>> 2) You need to define the filters in order to compute the
>>> cross-correlations and extract the coherent part of the ambient noise for a
>>> given frequency range. MWCS is used to compute the moving window cross
>>> spectral analysis after the cross-correlation procedure.
>>>
>>> 3) dunno. May be Thomas can give you more info.
>>>
>>> -Esteban J. Chaves
>>>
>>>
>>> On Oct 6, 2016, at 5:00 AM, msnoise-request(a)mailman-as.oma.be wrote:
>>>>
>>>> Send MSNoise mailing list submissions to
>>>> msnoise(a)mailman-as.oma.be
>>>>
>>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>> http://mailman-as.oma.be/mailman/listinfo/msnoise
>>>> or, via email, send a message with subject or body 'help' to
>>>> msnoise-request(a)mailman-as.oma.be
>>>>
>>>> You can reach the person managing the list at
>>>> msnoise-owner(a)mailman-as.oma.be
>>>>
>>>> When replying, please edit your Subject line so it is more specific
>>>> than "Re: Contents of MSNoise digest..."
>>>>
>>>>
>>>> Today's Topics:
>>>>
>>>> 1. new user (Flinders, Ashton)
>>>>
>>>>
>>>> ----------------------------------------------------------------------
>>>>
>>>> Message: 1
>>>> Date: Wed, 5 Oct 2016 13:10:53 -0700
>>>> From: "Flinders, Ashton" <aflinders(a)usgs.gov>
>>>> To: <msnoise(a)mailman-as.oma.be>
>>>> Subject: [MSNoise] new user
>>>> Message-ID:
>>>> <CAPbWHEO7J_9dyMdKJ3SQkpGy9hG7N1M-COwgzGTpkVmy85ig5g@mail.
>>>> gmail.com>
>>>> Content-Type: text/plain; charset="UTF-8"
>>>>
>>>> Hi all, long-time obspy user new MSnoise user.
>>>>
>>>> I just had a couple quick questions I was hoping to get clarification on;
>>>>
>>>> From the SRL article;
>>>>>
>>>> "Once all waveforms are loaded in memory, the computation is done by
>>>> iteration of the station pairs, on the different components to compute
>>>> and
>>>> the on the different filters for each defined window (30 minutes slices
>>>> by
>>>> default)."
>>>>
>>>> 1) To be clear, the two time-series from a station-station pair are
>>>> divided
>>>> into segments (30 minutes long, no overlap, by default), and the CC is
>>>> done
>>>> on these segments? Are these segments then rebuilt into the daily CCF? Is
>>>> this segmentation purely for efficieny reasons, or is there something
>>>> else
>>>> going on?
>>>>
>>>> 2) Why does msnoise compute_cc, not work if there is no MCWS filter
>>>> defined?
>>>>
>>>> 3) Is there an intelligent way to search the mailing list archive?
>>>>
>>>> Thanks for the help!
>>>>
>>>> -ashton
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> _______________________________________________
>>>> MSNoise mailing list
>>>> MSNoise(a)mailman-as.oma.be
>>>> http://mailman-as.oma.be/mailman/listinfo/msnoise
>>>>
>>>>
>>>> End of MSNoise Digest, Vol 31, Issue 1
>>>> **************************************
>>>>
>>> _______________________________________________
>>> 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
>>
>
>
>
> --
> Ashton F. Flinders, Ph.D
> U.S. Geological Survey
> 345 Middlefield Road
> Menlo Park, CA 94025
> (650) 329-5050
> _______________________________________________
> MSNoise mailing list
> MSNoise(a)mailman-as.oma.be
> http://mailman-as.oma.be/mailman/listinfo/msnoise
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 7 Oct 2016 10:28:48 +0200
> From: Thomas Lecocq <thomas.lecocq(a)oma.be>
> To: msnoise(a)mailman-as.oma.be
> Subject: Re: [MSNoise] MSNoise Digest, Vol 31, Issue 1
> Message-ID: <570e92d8-4cee-bdbf-1184-173420e947e2(a)oma.be>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi Ashton,
>
> For you to know, we are "about" to release MSNoise-TOMO "soon"...
>
> The python3 version is as stable as the python2 one, both are tested
> continuously on independent CI services (Travis for Linux & Appveyor for
> Windows).
>
> Note that this holds "as long as" I don't need py3 specific things in
> the code base, because if this happens, I'll drop py2 support.
> Aaaaanyway, py2 end of life is 2020.
>
> Cheers,
>
> Thomas
>
>
> Le 07/10/2016 ? 01:16, Flinders, Ashton a ?crit :
>> Thanks for all the info Thomas! I'm coming from an AN tomography
>> background, so things are a little different to me, e.g. I tend to
>> preprocess, whiten and do the CC over a broad band, and then do different
>> narrow-band filtering on the final stacked CC to get my frequency-band
>> dependent dt's.
>>
>> I look forward to actively contributing, so I'll be sure to push any
>> problems I encounter to the github thread too.
>>
>> On a sidenote, is the python3 version stable, or still a work in progress?
>>
>> thanks again!
>>
>> ashton
>>
>> On Thu, Oct 6, 2016 at 1:30 PM, Thomas Lecocq <Thomas.Lecocq(a)seismology.be>
>> wrote:
>>
>
>
>
> ------------------------------
>
> _______________________________________________
> MSNoise mailing list
> MSNoise(a)mailman-as.oma.be
> http://mailman-as.oma.be/mailman/listinfo/msnoise
>
>
> End of MSNoise Digest, Vol 31, Issue 5
> **************************************
Hi Ashton,
As an active user:
I highly recommend you to check the documentation: http://msnoise.org/doc/workflow.html#module-msnoise.s03compute_cc <http://msnoise.org/doc/workflow.html#module-msnoise.s03compute_cc>
I think the pre-processing and processing steps are well documented in the web site.
1) Yes. It is more efficient to compute the cross-correlation functions or Green’s functions using 30-min chunks. Although you can change this feature if you will. Segments are re-build afterwards.
2) You need to define the filters in order to compute the cross-correlations and extract the coherent part of the ambient noise for a given frequency range. MWCS is used to compute the moving window cross spectral analysis after the cross-correlation procedure.
3) dunno. May be Thomas can give you more info.
-Esteban J. Chaves
> On Oct 6, 2016, at 5:00 AM, msnoise-request(a)mailman-as.oma.be wrote:
>
> Send MSNoise mailing list submissions to
> msnoise(a)mailman-as.oma.be
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman-as.oma.be/mailman/listinfo/msnoise
> or, via email, send a message with subject or body 'help' to
> msnoise-request(a)mailman-as.oma.be
>
> You can reach the person managing the list at
> msnoise-owner(a)mailman-as.oma.be
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of MSNoise digest..."
>
>
> Today's Topics:
>
> 1. new user (Flinders, Ashton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 5 Oct 2016 13:10:53 -0700
> From: "Flinders, Ashton" <aflinders(a)usgs.gov>
> To: <msnoise(a)mailman-as.oma.be>
> Subject: [MSNoise] new user
> Message-ID:
> <CAPbWHEO7J_9dyMdKJ3SQkpGy9hG7N1M-COwgzGTpkVmy85ig5g(a)mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi all, long-time obspy user new MSnoise user.
>
> I just had a couple quick questions I was hoping to get clarification on;
>
>> From the SRL article;
> "Once all waveforms are loaded in memory, the computation is done by
> iteration of the station pairs, on the different components to compute and
> the on the different filters for each defined window (30 minutes slices by
> default)."
>
> 1) To be clear, the two time-series from a station-station pair are divided
> into segments (30 minutes long, no overlap, by default), and the CC is done
> on these segments? Are these segments then rebuilt into the daily CCF? Is
> this segmentation purely for efficieny reasons, or is there something else
> going on?
>
> 2) Why does msnoise compute_cc, not work if there is no MCWS filter defined?
>
> 3) Is there an intelligent way to search the mailing list archive?
>
> Thanks for the help!
>
> -ashton
>
>
> ------------------------------
>
> _______________________________________________
> MSNoise mailing list
> MSNoise(a)mailman-as.oma.be
> http://mailman-as.oma.be/mailman/listinfo/msnoise
>
>
> End of MSNoise Digest, Vol 31, Issue 1
> **************************************
Hi all, long-time obspy user new MSnoise user.
I just had a couple quick questions I was hoping to get clarification on;
>From the SRL article;
"Once all waveforms are loaded in memory, the computation is done by
iteration of the station pairs, on the different components to compute and
the on the different filters for each defined window (30 minutes slices by
default)."
1) To be clear, the two time-series from a station-station pair are divided
into segments (30 minutes long, no overlap, by default), and the CC is done
on these segments? Are these segments then rebuilt into the daily CCF? Is
this segmentation purely for efficieny reasons, or is there something else
going on?
2) Why does msnoise compute_cc, not work if there is no MCWS filter defined?
3) Is there an intelligent way to search the mailing list archive?
Thanks for the help!
-ashton
