Re: [MSNoise] MSNoise Digest, Vol 31, Issue 1

List overview All Threads
Download

newer

older

Re: [MSNoise] MSNoise Digest, Vol...

new user

Esteban Chaves

6 Oct 2016 6 Oct '16

7:17 p.m.

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 **************************************

Show replies by date

Flinders, Ashton

6 Oct 6 Oct

7:38 p.m.

New subject: MSNoise Digest, Vol 31, Issue 1

Thanks Esteban, I have looked through the documentation extensively, as well as the SRL paper, and a bit of grepping on the source code (e.g. it took me a while to figure out why in the world I couldnt remove instrument responses using a RESP or PZ file, since it is listed on the documentation page, until I grepped the source code and saw those were not implemented.) 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. This is only true if the daily segments are always preloaded into memory (IO vs CC time). The SRL paper makes it sounds like this is the case, but I want to make sure that this is always the case, even for processing many stations/days or long segments. I also wasnt sure if these segmented CC were used for any statistics (e.g. uncertainty in daily CC values). 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. Yes, I understand that (the way its been written) filter values should be defined before the CC (which really should only be the whiteneing band or preprocessing), however I dont understand why in the web gui the whiten and MWCS filters are put within the same group. This make me predefine a MWCS filter band, along with my whiten band, even though the MWCS doesnt happed for another two processing steps. This leads to confusion, for example; What happens if I compute the CC's with a defined filter (as written, a MWCS and whiten filter defined together) and then want to compute different MWCS's later on when I actually get to the MWCS step. Can I just define a new filter, with new mwcs_low mwcs_high values? Since the web gui forces me to define a filter high low value (whiten, I assume) does it not use these? Do I have to go back and recalculate the cross correlations everytime I want to add an MWCS filter (which I wouldnt expect I have too)? Similarly, what happens if I want to delete a set of processed MWCS or stacks? I cant just delete the folder, since their are still pointers in the sql database. Just reprocessing doesnt seem to work either. thanks again -ashton On Thu, Oct 6, 2016 at 10:17 AM, Esteban Chaves <echfisica(a)gmail.com> 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

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

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

-- Ashton F. Flinders, Ph.D U.S. Geological Survey 345 Middlefield Road Menlo Park, CA 94025 (650) 329-5050

Flinders, Ashton

7:44 p.m.

New subject: MSNoise Digest, Vol 31, Issue 1

p.s. In the admin gui, under configuration, several of the values are set to numbers with a period "." after them. Is this necessary? E.g. are they there to force a decimal type in python 2.x opposed to an integer? On Thu, Oct 6, 2016 at 10:38 AM, Flinders, Ashton <aflinders(a)usgs.gov> 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

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

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?

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?

_______________________________________________ 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

Thomas Lecocq

10:22 p.m.

New subject: MSNoise Digest, Vol 31, Issue 1

Ahston, No, don't worry about this, the values are converted to the right type when loaded from the config. Thomas On 06/10/2016 19:44, Flinders, Ashton 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

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

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?

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?

_______________________________________________ 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

VICIC BLAZ [PHD0900016]

9:26 p.m.

New subject: MSNoise Digest, Vol 31, Issue 1

Hi, I will use this correspondence for my question, since you already mentioned removal of the response. Do i have to change the code or something if I have different stationxmls for different years, so they are read correctly, or does the code manage this and i just put them into the folder? Thanks ________________________________ 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: Thursday, October 6, 2016 7:38:40 PM To: Python Package for Monitoring Seismic Velocity Changes using AmbientSeismic Noise Subject: Re: [MSNoise] MSNoise Digest, Vol 31, Issue 1 Thanks Esteban, I have looked through the documentation extensively, as well as the SRL paper, and a bit of grepping on the source code (e.g. it took me a while to figure out why in the world I couldnt remove instrument responses using a RESP or PZ file, since it is listed on the documentation page, until I grepped the source code and saw those were not implemented.) 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. This is only true if the daily segments are always preloaded into memory (IO vs CC time). The SRL paper makes it sounds like this is the case, but I want to make sure that this is always the case, even for processing many stations/days or long segments. I also wasnt sure if these segmented CC were used for any statistics (e.g. uncertainty in daily CC values). 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. Yes, I understand that (the way its been written) filter values should be defined before the CC (which really should only be the whiteneing band or preprocessing), however I dont understand why in the web gui the whiten and MWCS filters are put within the same group. This make me predefine a MWCS filter band, along with my whiten band, even though the MWCS doesnt happed for another two processing steps. This leads to confusion, for example; What happens if I compute the CC's with a defined filter (as written, a MWCS and whiten filter defined together) and then want to compute different MWCS's later on when I actually get to the MWCS step. Can I just define a new filter, with new mwcs_low mwcs_high values? Since the web gui forces me to define a filter high low value (whiten, I assume) does it not use these? Do I have to go back and recalculate the cross correlations everytime I want to add an MWCS filter (which I wouldnt expect I have too)? Similarly, what happens if I want to delete a set of processed MWCS or stacks? I cant just delete the folder, since their are still pointers in the sql database. Just reprocessing doesnt seem to work either. thanks again -ashton On Thu, Oct 6, 2016 at 10:17 AM, Esteban Chaves <echfisica(a)gmail.com> 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

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

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?

_______________________________________________ MSNoise mailing list MSNoise(a)mailman-as.oma.be http://mailman-as.oma.be/mailman/listinfo/msnoise

Flinders, Ashton

10:10 p.m.

New subject: MSNoise Digest, Vol 31, Issue 1

...

From the source;

if response_format == "inventory": firstinv = True inventory = None for file in files: try: inv = read_inventory(file) if firstinv: inventory = inv firstinv = False else: inventory += inv except: traceback.print_exc() pass if inventory: stream.attach_response(inventory) stream.remove_response(output='VEL', pre_filt=response_prefilt) On Thu, Oct 6, 2016 at 12:26 PM, VICIC BLAZ [PHD0900016] < BLAZ.VICIC(a)phd.units.it> 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

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

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

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?

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?

_______________________________________________ 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 _______________________________________________ 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

Thomas Lecocq

10:20 p.m.

New subject: MSNoise Digest, Vol 31, Issue 1

Hi all, Indeed, the answer from Ashton is right, if you are using inventories or dataless, both should be OK. The response-removal is neither optimal , nor efficient, so be prepared for loooong processing... Cheers, Thomas On 06/10/2016 22:10, Flinders, Ashton wrote:

...

I believe if you have different xmls from different years, but there all in the same inventory directory, it should attach the correct one automatically. The code loops through the inventory director reading in each xml response file and appending it to a list of station responses (actually a list of obspy inventories). It then attaches this to current stream of seismograms, with obspy's attach_response handling everything. From the source; if response_format == "inventory": firstinv = True inventory = None for file in files: try: inv = read_inventory(file) if firstinv: inventory = inv firstinv = False else: inventory += inv except: traceback.print_exc() pass if inventory: stream.attach_response(inventory) stream.remove_response(output='VEL', pre_filt=response_prefilt) On Thu, Oct 6, 2016 at 12:26 PM, VICIC BLAZ [PHD0900016] < BLAZ.VICIC(a)phd.units.it> 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

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

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

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?

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?

_______________________________________________ MSNoise mailing list MSNoise(a)mailman-as.oma.be http://mailman-as.oma.be/mailman/listinfo/msnoise

Thomas Lecocq

10:19 p.m.

New subject: MSNoise Digest, Vol 31, Issue 1

Hi Ashton, Trying to answer inline below: On 06/10/2016 19:38, Flinders, Ashton wrote:

...

Yeah, that's supposed to pop out if you're using the -vvvv option for the commands (DEBUG level). This should be implemeted (if needed = not for me as I only have either dataless or inventory, but still)..

...

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. This is only true if the daily segments are always preloaded into memory (IO vs CC time). The SRL paper makes it sounds like this is the case, but I want to make sure that this is always the case, even for processing many stations/days or long segments. I also wasnt sure if these segmented CC were used for any statistics (e.g. uncertainty in daily CC values).

They are, the base of MSNoise is a daily job, so traces are preloaded & preprocessed, one by one, in RAM before processing. No "moving window I/O" is done,. In the future, for LargeN or very high freq cases, I want this to be more dynamic, but for the moment it's like this.

...

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. Yes, I understand that (the way its been written) filter values should be defined before the CC (which really should only be the whiteneing band or preprocessing), however I dont understand why in the web gui the whiten and MWCS filters are put within the same group. This make me predefine a MWCS filter band, along with my whiten band, even though the MWCS doesnt happed for another two processing steps. This leads to confusion, for example; What happens if I compute the CC's with a defined filter (as written, a MWCS and whiten filter defined together) and then want to compute different MWCS's later on when I actually get to the MWCS step. Can I just define a new filter, with new mwcs_low mwcs_high values? Since the web gui forces me to define a filter high low value (whiten, I assume) does it not use these? Do I have to go back and recalculate the cross correlations everytime I want to add an MWCS filter (which I wouldnt expect I have too)?

The MWCS values don't need to be predefined when computing the CC, but the logic we defined is the following: 1/ you compute the CC in a quite narrow band 2/ you compute the MWCS is a (slightly) narrower band the original idea is thus not: 1/ you compute the CC in a broad band 2/ you compute MWCS in different bands based on the same CC but I'm completely OK to start a discussion about this, certainly because, for example, the lag-time-related parameters are also filter-related, and somehow should be linked to the filters iff, like now, they are quite narrow-band.

...

Similarly, what happens if I want to delete a set of processed MWCS or stacks? I cant just delete the folder, since their are still pointers in the sql database. Just reprocessing doesnt seem to work either.

Just delete the MWCS & DTT folders, and run "msnoise reset DTT --all" and the jobs will be reset. Cheers, Thomas

...

thanks again -ashton On Thu, Oct 6, 2016 at 10:17 AM, Esteban Chaves <echfisica(a)gmail.com> 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

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

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?

_______________________________________________ MSNoise mailing list MSNoise(a)mailman-as.oma.be http://mailman-as.oma.be/mailman/listinfo/msnoise

Thomas Lecocq

10:30 p.m.

New subject: MSNoise Digest, Vol 31, Issue 1

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:

...

From the SRL article;

_______________________________________________ MSNoise mailing list MSNoise(a)mailman-as.oma.be http://mailman-as.oma.be/mailman/listinfo/msnoise

Flinders, Ashton

7 Oct 7 Oct

1:16 a.m.

New subject: 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:

...

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;

_______________________________________________ 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

VICIC BLAZ [PHD0900016]

7:49 a.m.

New subject: MSNoise Digest, Vol 31, Issue 1

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:

...

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:

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;

_______________________________________________ MSNoise mailing list MSNoise(a)mailman-as.oma.be http://mailman-as.oma.be/mailman/listinfo/msnoise

Thomas Lecocq

10:28 a.m.

New subject: MSNoise Digest, Vol 31, Issue 1

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 :

...

3129

days inactive

3130

days old

msnoise@lists.observatory.be

Manage subscription

11 comments

5 participants

tags (0)

participants (5)

Esteban Chaves
Flinders, Ashton
Thomas Lecocq
Thomas Lecocq
VICIC BLAZ [PHD0900016]