search

CelsoReyes / zmap7

ZMAP Seismology Software. V 7.x has been updated to MATLAB R2018a.
79 stars 40 forks source link

Wrong magnitude after Decluster a catalogue #61

Open dedalomarchetti opened 3 years ago

dedalomarchetti commented 3 years ago

I declustered a wide catalogue of M5+ events from USGS and I noticed that an event that originally is M6.1 occurred on 2013-01-31 at 3:33 UT after decluster with the option "Replace with the equivalent event" in the ZMap Catalogue is 8.1461 that is not possible for physics... USGS_M5_1980_2020.zip

To Reproduce Steps to reproduce the behavior:

  1. Go to 'Catalogue', select 'get/load catalogue' --> from .mat file and select the attached USGS catalogue
  2. Go to 'Catalogue' select 'Decluster (Reasenberg)'
  3. Input the following parameters: 10, 20, 0.95, 0.5, 5.0, 10, 8, 7
  4. Click on "Replace clusters with equivalent event"
  5. Click "ok" in the result window
  6. Move to Matlab parent window and open manually the "declustered catalogue"
  7. Open the "Date" field and scroll to found the "2013-01-31 03:33:43" that would be the 42150 row
  8. Open the "Magnitude" field and scroll at the same row (42150th) and check the magnitude
  9. See error that original event of magnitude 6.1 has been replaced by 8.1 that is impossible that the equivalent magnitude of the cluster is 2.0 magnitude higher

If you export the declustered catalogue the mistake is still present.

I suppose the mistake is due to a mix of lines that happened also in ZMAP6.0 and in that version, I found that saving the results, closing the Whole Matlab and reopen at each passage can overpass the bug.

Expected behavior The equivalent magnitude of the cluster I expect can be greater of 0.1 / 0.3 not 2.0