MSNoise

msnoise@lists.observatory.be

349 discussions

by anthony.abi_nader＠univ-fcomte.fr

Hello, I am working on an msnoise project in sqlite environment, I am trying to launch the command "msnoise admin" to access the visual interface, however am I getting this error: CRITICAL:root:Unable to read project configuration: error connecting to the database: (sqlite3.OperationalError) database is locked [SQL: SELECT config.name AS config_name, config.value AS config_value FROM config WHERE config.name = ? LIMIT ? OFFSET ?] [parameters: ('plugins', 1, 0)] (Background on this error at: http://sqlalche.me/e/13/e3q8) Does anyone know how to deal with such errors? Best regards, -- Anthony ABI NADER Civil Engineer PhD student in Seismology Laboratoi re Chrono-Environneme nt - UMR 6249 CNRS Bureau -116L, 16 Route de Gray, 25030 Besançon Université Bourgogne Franche-Comté tel.+33769260628

1 year, 10 months

I got a question when I'm using MSNoise 1.6

by Zhang Rui

Hi, dear monitor。 My names Zaire and I am a postgraduate from China using MSNoise to do some research on the data we recorded. I've got a problem when I used MSNoise 1.6, "compute_dtt". G:\cal>msnoise compute_dtt 2022-01-13 11:04:07.813875 msnoise [pid 17668][INFO]: *** Starting: Compute DT/T *** 2022-01-13 11:04:08.187253 msnoise [pid 17668][INFO]: Loading mov=1 days for filter=01 Traceback (most recent call last): File "F:\Anaconda\lib\site-packages\pandas\core\series.py", line 1062, in __setitem__ self._set_with_engine(key, value) File "F:\Anaconda\lib\site-packages\pandas\core\series.py", line 1095, in _set_with_engine loc = self.index._engine.get_loc(key) File "pandas\_libs\index.pyx", line 76, in pandas._libs.index.IndexEngine.get_loc File "pandas\_libs\index.pyx", line 82, in pandas._libs.index.IndexEngine.get_loc TypeError: '[ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780]' is an invalid key During handling of the above exception, another exception occurred: Traceback (most recent call last): File "F:\Anaconda\lib\runpy.py", line 197, in _run_module_as_main return _run_code(code, main_globals, None, File "F:\Anaconda\lib\runpy.py", line 87, in _run_code exec(code, run_globals) File "F:\Anaconda\Scripts\msnoise.exe\__main__.py", line 7, in <module> File "F:\Anaconda\lib\site-packages\msnoise\scripts\msnoise.py", line 1202, in run cli(obj={}) File "F:\Anaconda\lib\site-packages\click\core.py", line 1128, in __call__ return self.main(*args, **kwargs) File "F:\Anaconda\lib\site-packages\click\core.py", line 1053, in main rv = self.invoke(ctx) File "F:\Anaconda\lib\site-packages\click\core.py", line 1659, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "F:\Anaconda\lib\site-packages\click\core.py", line 1395, in invoke return ctx.invoke(self.callback, **ctx.params) File "F:\Anaconda\lib\site-packages\click\core.py", line 754, in invoke return __callback(*args, **kwargs) File "F:\Anaconda\lib\site-packages\click\decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) File "F:\Anaconda\lib\site-packages\msnoise\scripts\msnoise.py", line 824, in compute_dtt main(loglevel=loglevel) File "F:\Anaconda\lib\site-packages\msnoise\s06compute_dtt.py", line 231, in main df['err'][tmp] = 1.0 File "F:\Anaconda\lib\site-packages\pandas\core\series.py", line 1088, in __setitem__ self._set_with(key, value) File "F:\Anaconda\lib\site-packages\pandas\core\series.py", line 1123, in _set_with self._set_labels(key, value) File "F:\Anaconda\lib\site-packages\pandas\core\series.py", line 1134, in _set_labels raise KeyError(f"{key[mask]} not in index") KeyError: '[ 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115\n 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133\n 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151\n 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169\n 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187\n 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205\n 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223\n 224 225 226 227 228 229 331 332 333 334 335 336 337 338 339 340 341 342\n 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360\n 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378\n 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396\n 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414\n 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432\n 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 551\n 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569\n 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587\n 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605\n 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623\n 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641\n 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659\n 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677\n 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695\n 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713\n 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731\n 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749\n 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767\n 768 769 770 771 772 773 774 775 776 777 778 779 780] not in index' I wonder how to solve this problem and I don't know if there's something wrong I set or what else. I'm sure I can do it if I got your help. Thanks for your time!

1 year, 11 months

Problems with compute_cc

by Rueda Nuñez Juán José

Hello, After installing MSNOISE in a UBUNTU virtual machine, I have loaded my SeisComP structured data (SDS) in db and I created the cross-correlation jobs correctly from data_availability.. But, when I run "compute_cc" it doesn't compute the correlations and I get the following output for all pairs: (msnoise) sysop@ogcvm01:~$ msnoise -v compute_cc 2023-02-28 15:41:42.598632 msnoise [pid 188872][INFO]: *** Starting: Compute CC *** 2023-02-28 15:41:42.641014 msnoise [pid 188872][INFO]: Will compute [ZZ] for different stations 2023-02-28 15:41:42.641259 msnoise [pid 188872][INFO]: Will compute [] for single stations 2023-02-28 15:41:42.641464 msnoise [pid 188872][INFO]: Checking if there are jobs to do 2023-02-28 15:41:42.644425 msnoise [pid 188872][INFO]: Getting the next job 2023-02-28 15:41:42.658902 msnoise [pid 188872][INFO]: New CC Job: 2017-02-08 (3 pairs with 3 stations) 2023-02-28 15:41:42.797933 msnoise [pid 188872][DEBUG]: ES.EGOM.Z Reading 1 Files 2023-02-28 15:41:42.798029 msnoise [pid 188872][DEBUG]: ERROR reading file /nfs/respaldo1/CANARIAS/2017/ES/EGOM/HHZ.D/ES.EGOM..HHZ.D.2017.039 2023-02-28 15:41:42.798128 msnoise [pid 188872][DEBUG]: ES.EHIG.Z Reading 1 Files 2023-02-28 15:41:42.798176 msnoise [pid 188872][DEBUG]: ERROR reading file /nfs/respaldo1/CANARIAS/2017/ES/EHIG/HHZ.D/ES.EHIG..HHZ.D.2017.039 2023-02-28 15:41:42.798240 msnoise [pid 188872][DEBUG]: ES.TBT.Z Reading 2 Files 2023-02-28 15:41:42.798282 msnoise [pid 188872][DEBUG]: ERROR reading file /nfs/respaldo1/CANARIAS/2017/ES/TBT/HHZ.D/ES.TBT..HHZ.D.2017.039 2023-02-28 15:41:42.798317 msnoise [pid 188872][DEBUG]: ERROR reading file /nfs/respaldo1/CANARIAS/2017/ES/TBT/SHZ.D/ES.TBT..SHZ.D.2017.039 2023-02-28 15:41:42.798403 msnoise [pid 188872][DEBUG]: Not enough data for this day ! 2023-02-28 15:41:42.798433 msnoise [pid 188872][DEBUG]: Marking job Done and continuing with next ! 2023-02-28 15:41:42.817136 msnoise [pid 188872][INFO]: Getting the next job The path to my data is correct, but I seem to have a problem. You can help? Thaks Juan

2 years, 2 months

autocorrelations

by anthony.abi_nader＠univ-fcomte.fr

Hello, I was using msnoise to compute autocorrelation for 60 stations. I was checking the DTT files and I saw that there are autocorrelations for few stations that are missing each day. I checked in the "job" section, the corresponding jobs for the missing stations exist (as DTT). I didn't have this problem while computing the crosscorrelations. While doing the computation, the mwcs step reached 98%, I do not know if my problem might be connected to this (I read that these 2% are connected to the ref). Do you have an idea what might be the cause of this? Best regards, Anthony -- Anthony ABI NADER Civil Engineer PhD student in Seismology Laboratoi re Chrono-Environneme nt - UMR 6249 CNRS Bureau -116L, 16 Route de Gray, 25030 Besançon Université Bourgogne Franche-Comté tel.+33769260628

2 years, 2 months

Launch with bash

by anthony.abi_nader＠univ-fcomte.fr

Hello, Is it possible to launch msnoise commands through a bash script (.sh) and not directly in a terminal? The objective is to have more computation time, in the terminal the commands get killed after 6 hours, if i launch it in bash i will have 30 days before it gets killed (this is related to the computing center I work on). Thank you for your help! Cheers, Anthony -- Anthony ABI NADER Civil Engineer PhD student in Seismology Laboratoi re Chrono-Environneme nt - UMR 6249 CNRS Bureau -116L, 16 Route de Gray, 25030 Besançon Université Bourgogne Franche-Comté tel.+33769260628

2 years, 3 months

Compute CC of data from the same network and station code but using different location code.

by CHANINTHON RATTANAVETCHASIT

Hi Msnoise team, My name is New, a PhD student from Thailand. I have been using Msnoise for a couple of years, thank you for your hard work in developing the package. I would like to compute CC of data from two seismometers using the same network and station code but different location code. I tried to scan the archive and create new jobs. I know it definitely will not work because the code use network and station name to create jobs or station pair-up. Do you have any suggestions on this location code issue? Thanks in advance, New Chaninthon Rattanavetchasit PhD student in Department of Geosciences, National Taiwan University

2 years, 6 months

Windows station coordinates

by Matthew Agius

Hi MSNoisers, I have msnoise installed on Linux and on Windows. The station coordinates of the attached inventory file (and others of the same network) are read without problems on Linux when executing "msnoise config sync" but not on Windows. It says "No coords for ML.MELT, skipping,..." The command "msnoise db update_loc_chan" works well on both Linux and Windows. What could be the problem for Windows to read the station coordinates? I appreciate your help or suggestions with this problem. Sincerely, Matthew

2 years, 8 months

Problem -- No output folder created

by Lulu Hsiao

Hi Thomas, I am very new to ambient seismic noise analysis and MSNoise, and I recently encountered an issue. I followed the workflow step by step to do my cc jobs and all the other jobs, but I didn't find the output anywhere in my hard disk. (I have set keep_all and keep_days to Y) Please tell me what's wrong:( Thank you. My data format is miniSEED, and below is my msnoise info. General: - the MSNoise module is installed in: c:\users\lulu hsiao\appdata\local\programs\python\python39\lib\site-packages - db.ini is present in the current directory Database information stored in the db.ini file: - database type: MySQL - hostname: localhost - database: msnoise - username: MSNoise - password: ********** - table prefix: (none) Configuration: - C:\Users\Lulu Hsiao\MSnoise\data_test exists - C:\Users\Lulu Hsiao\MSnoise\CROSS_CORRELATIONS does not exists and that is not normal (3 CC jobs done) Configuration values: | Normal colour indicates that the default value is used | Green indicates "M"odified values M data_folder: C:\Users\Lulu Hsiao\MSnoise\data_test M output_folder: C:\Users\Lulu Hsiao\MSnoise\CROSS_CORRELATIONS data_structure: SDS archive_format: '' network: * channels: * M startdate: 2022-01-07 M enddate: 2022-01-08 M analysis_duration: 50 M cc_sampling_rate: 100 resampling_method: Lanczos M preprocess_lowpass: 30 preprocess_highpass: 0.01 M preprocess_max_gap: 5 preprocess_taper_length: 20.0 remove_response: N response_format: dataless response_path: inventory response_prefilt: (0.005, 0.006, 30.0, 35.0) M maxlag: 5 M corr_duration: 10.5 M overlap: 0.5 windsorizing: 3 whitening: A whitening_type: B stack_method: linear pws_timegate: 10.0 pws_power: 2.0 crondays: 1 components_to_compute: ZZ cc_type: CC M components_to_compute_single_station: ZZ cc_type_single_station_AC: CC cc_type_single_station_SC: CC autocorr: N M keep_all: Y keep_days: Y M ref_begin: 2022-01-07 M ref_end: 2022-01-08 M mov_stack: 1,3,4 M export_format: SAC sac_format: doublets dtt_lag: static dtt_v: 1.0 dtt_minlag: 5.0 dtt_width: 30.0 dtt_sides: both dtt_mincoh: 0.65 dtt_maxerr: 0.1 dtt_maxdt: 0.1 plugins: '' hpc: N M stretching_max: 0.2 M stretching_nsteps: 5000 Filters: ID: [low:high] [mwcs_low:mwcs_high] mwcs_wlen mwcs_step Used? 1: [0.010:30.000] [0.010:30.000] 12 4 Y Stations: NET.STA Long. Lat. Alt. Coord. Used? TW.OF067 0.0000 0.0000 0.0 UTM Y TW.OF235 0.0000 0.0000 0.0 UTM Y Jobs: CC: D : 3 STACK: D : 3 MWCS: D : 3 DTT: D : 3 Best Wishes, Lulu Hsiaoundergraduate studentDepartment of Earth Science, National Central University, R.O.C.

2 years, 8 months

Issue in computing dtt

by Faisal Umer

Hi everyone, I am new to msnoise therefore facing some issues. While trying to compute dtt, suddenly this message starts appearing in the terminal: "/home/zee/anaconda3/lib/python3.9/site-packages/scipy/optimize/minpack.py:833: OptimizeWarning: Covariance of the parameters could not be estimated warnings.warn('Covariance of the parameters could not be estimated'," Can anyone tell me the reason behind it and how to sort out this issue. Regards, Faisal Umer

2 years, 9 months

source of coherence calculation

by Kohtaro R. Araragi

Dear Thomas (c.c. MSNoise community), I'm Run, a former student of ERI who has been working with Florent, (Yosuke) Aoki-san, (Takao ) Ohminato-san. I hope you are doing well. I am recently checking the processing of MWCS method and noticed that the algorithm of coherence ( functions of "smooth(x, window='boxcar', half_win=3):" and "getCoherence(dcs, ds1, ds2)" at move2obspy.py) is different from matlab (mscohere) or python (scipy.signal.coherence) though it works very well. Could you let me know if there were some original papers or documents that explain the background about it? I appreciate if someone tell me about relevant information how to obtain the coherence in detail. Thanks in advance, Run -- ____________________________________________________ K. Run Araragi Research student/M.Sc. Earthquake Research Institute University of Tokyo 1-1-1 Yayoi, Bunkyo-ku Tokyo, Japan 113-0032 Skype name: kalessinlord Tel: 81-3-5841-5697 Cel: 81-90-1166-3091 ____________________________________________________

2 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

MSNoise