problem about dv/v

[amell567]

Hi ,

I’ve followed the NoisePy tutorial and successfully completed the correlation computation and stacking. Now, I’m looking to move on to the dv/v calculation. The paper "NoisePy: A New High-Performance Python Tool for Ambient-Noise Seismology" mentions that this step can be handled using the measure_dvv.py file. However, I couldn’t find this file in the GitHub repository.

I noticed that the monitoring_demo.ipynb file includes velocity change processing, but it’s only for single-station measurements. The monitoring_methods.py file contains the core functions for seven processing methods, but my programming skills aren’t strong enough to write the full code for the entire post-processing workflow.

Could you offer some guidance or suggestions on how to proceed? Thanks in advance, and I hope you’re having a great day!

老师您好！
我根据noisepy的教程已经完成了相关性计算和堆栈，我想要继续进行dv/v的计算，“NoisePy: A New High-Performance Python Tool for Ambient-Noise Seismology”中提到这一部分的处理可以根据measure_dvv.py文件来进行，但是我在github上的模块里并没有找到这个py文件，monitoring_demo.ipynb文件里有速度变化的处理，但是只是用于单站测量，而monitoring_methods.py文件里包含了七种处理方法的核心函数，但我的编程水平不足以支撑我编写完整的代码来进行后处理的全部流程，所以请给我一些建议，祝您生活愉快！

[kuanfufeng]

Hi @amell567,

Thank you for using NoisePy.

The instructions in that paper are for the original NoisePy version. Since last year, we have been working on refactoring to make this package easier to develop and deploy. To use NoisePy to get noise correlation functions, you can find the up-to-date document via this link: https://noisepy.github.io/NoisePy/.

Regarding the monitoring module measure_dvv.py, it has been renamed and placed here: src/noisepy/monitoring/monitoring_methods.py. All the modules in monitoring_method.py for computing temporal seismic velocity changes handle both single-station and two-station cases. The notebook monitoring_demo.ipynb is a quick demonstration of how NoisePy and its post-processes are connected as a workflow. To use the monitoring modules, you can get the results by replacing the pref and pcur with the NumPy arrays of your reference and current functions.
For instance, the pref and pcur in this case.
( returns... ) = stretching(pref, pcur, config_monito.epsilon, config_monito.nbtrial, para)

Lastly, if you are interested in monitoring methods, you can find descriptions and tests about those methods in tutorials/monitoring/monitoring_methods_tutorial.ipynb.

Feel free to let me know if you have any questions.

[SeismoFelix]

Hi!

I would like to chime in on this issue since I am trying to do also dv/v measurements. I was working with the monitoring_methods_tutorial.ipynb and I got an error when I tried to run the cell on the section 5. Homogeneous half-space setting (example 01):

The error is in the second group of methods, when I tried to run:

dvv, error = mwcs_dvv(ref_homo[itvec], cur_homo[itvec], moving_window_length, window_slide_step, para, smoothing_half_win=5)

Thanks for any help you can provide.

[kuanfufeng]

Hi Felix,

Regarding this error, I have tested the notebook from my side and can run through it without this issue. Can you do a git pull and test it again so that we can make sure we are on the same and up-to-date repo when troubleshooting this issue?

Please let me know if there are any updates. Thank you!

[SeismoFelix]

Hi Kuan, thanks for your reply.

I am confused regarding your suggestion, sorry. I did for installing:

conda create -n noisepy -y python=3.10 pip
conda activate noisepy
pip install noisepy-seis

So I am unsure whether the git pull command should work since the installation was made through pip rather than Anaconda. However, the installation was done under a recently created Anaconda environment.

If I activate the environment noisepy and just make git pull I got:

fatal: not a git repository (or any of the parent directories): .git

and it does make sense to me because usually, the git pull command works after activating a package that has been cloned through a git clone command.

Probably I am missing something here and I apologize for that. However, you are right in the sense that my code version is not up to date with the latest version. However, the scripts I got are the ones fetched after I followed the installation process. Indeed I opened another issue about this situation.

Thanks again for your help!

[amel1567]

Hi！
I have finished running the monitoring_demo.ipynb file, now I want to process the local miniseed data, Therefore, I created ststation.csv and allfiles_time.csv files according to the requirements of the S0B_to_ASDF_2019.py file, and set the file path and parameters. However, when running the S0B_to_ASDF_2019.py code, errors were reported as shown in the figure. Please give me some advice, thank you, wish you a happy life!

[niyiyu]

Please refer to the noise_module file in the functions_2019 folder, which is compatible with S0B_to_ASDF_2019.py. You can find the make_timestamps functions here.