HYP2000 Md always 0.00

[Victor Preatoni]

Hi,

hyp2000 is always producing a 0.00 Md output. I later use localmag to calculate ML and works fine most of the time, but anyway, I would also like to have the Md value in case localmag is not successful. 

These are a few example lines of hyp2000_mgr.log, they always show 0.00 Md:

20190222 2324 36.99 37S47.76  71W 4.13   2.56   0.00  5 304  4.  0.02  4.1  3.2 DW      18983   

20190222 2319 21.13 37S48.01  71W 4.31   1.81   0.00  5 297  4.  0.02  3.6  3.0 DW      18982   

20190222 2328 05.67 37S48.35  71W 4.13   1.64   0.00  5 294  3.  0.04  3.6  2.9 DW      18984

Data comes from a tankplayer, so I sniffed the PICK_RING while tank was playing, and I could see TYPE_CODA_SCNL messages. So I presume pick_ew is doing it's job on calculating codas.

I ran the memphis_test example, and it produces Md values, so I am pretty sure there is something wrong with my configuration, but I am a bit lost on how to debug it.

Any help will be appreciated.

Thanks!

Victor

[Dietz, Lynn D]

I suspect that your hyp2000 config is missing something for your network.  The easiest troubleshooting path would be to get a sample eq from your system and run it through hypoinverse manually, using the same config as your real-time modules but creating  a hypoinverse .prt file (which is a kind of mini-log of each location attempt).  Steps to Md troubleshooting:  

1. Read the hypoinverse manual with regard to Md computation and configuration

2. Run hyp2000 in interactive mode with one of your eqs that you think should have an Md

a. run eqcoda with this command in config:  LogArcMsg     1       

This will have eqcoda write its output .arc msg (input to hyp2000_mgr) to its log.

b. clip one .arc msg from the eqcoda log and write it to a flat file in EW_PARAMS dir :   myinput.arc

A complete .arc file  from eqcoda will look something like this (not inluding ----------- lines):

----------- 

202312260026566738N4886122W4665  773     6132  1   1                                                                                        208318                2

$1

SQK  BG  DPZ  PD0202312260026 5817                                                2       5                 W  --

$   2 2.84 1.80 2.75 1.62 0.40 NSX2   -5 PHP0  588  1 285  3  96  5  42  0   0  0   0  0   0

HVC  BG  DPZ  P 0202312260026 5825                                                2       3                 W  --

$   1 2.57 1.80 0.0099.00 0.00 PSN2    3 PHP0  601  1 163  3  52  0   0  0   0  0   0  0   0

GDXB NC  HHZ  PU2202312260026 5828                                                2       3                 W  --

$   1 2.86 1.80 0.0099.00 0.00 PSN2    3 PHP0  181  1 176  3 101  0   0  0   0  0   0  0   0

SB4  BG  DPZ  PD0202312260026 5837                                                2       3                 W  --

$   1 2.70 1.80 0.0099.00 0.00 PSN2    3 PHP0  604  1 180  3  70  0   0  0   0  0   0  0   0

TCH  BG  DPZ  P 2202312260026 5841                                                1       5                 W  --

$   2 3.04 1.80 2.88 1.45 0.40 PSN1    5 PHP0   98  1  83  3 153  5  73  0   0  0   0  0   0

MCL  BG  DPZ  PD0202312260026 5852                                                2       3                 W  --

$   1 2.55 1.80 0.0099.00 0.00 PSN2    3 PHP0  732  1 145  3  49  0   0  0   0  0   0  0   0

                                                                  208318

$                                                                 208318

----------- 

c. starting in your EW_PARAMS dir, run hypoinverse interactively (yellow highlights are what you type):

UnixPrompt#  hyp2000

COMMAND?  @your-hypoinverse-startup-file.hyp

... response from hypo2000 ...

COMMAND? phs

 PHASE FILENAME

 [CR = ]? myinput.arc

 COMMAND? arc

 ARCHIVE FILE (NONE FOR NONE)

 [CR = ]? myoutput.arc

 COMMAND? prt

 PRINTOUT FILE (NONE FOR NONE)

 [CR = ]? myoutput.prt

 COMMAND? loc

... response from hypo2000 ...

 COMMAND? stop

You may get valuable info at the @ .hyp step (notice of config problems), or the loc step (trouble locating eq). Finally, the .prt file is a human-readable (by hypoinverse standards) report of the location and magnitude computation from hypoinverse. There you may find more clues about what's going on.

---

From: earthwo...@googlegroups.com <earthwo...@googlegroups.com> on behalf of Victor Preatoni <vpre...@gmail.com>
Sent: Tuesday, December 26, 2023 8:19 AM
To: Earthworm Community Forum <earthwo...@googlegroups.com>
Subject: [EXTERNAL] [Earthworm Forum] HYP2000 Md always 0.00

 

--
--
You received this message because you are subscribed to the Google
Groups "Earthworm Community Forum" group.
 
To post to this group, send an email to earthwo...@googlegroups.com
 
To unsubscribe from this group, send an email to
earthworm_for...@googlegroups.com
 
For more options, visit this group at
http://groups.google.com/group/earthworm_forum?hl=en

---
You received this message because you are subscribed to the Google Groups "Earthworm Community Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to earthworm_for...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/earthworm_forum/d855ce4e-f9c6-4148-893e-c85df45689e1n%40googlegroups.com.

[Victor Preatoni]

Hi Lynn,

thanks a lot for your answer. It helped me a lot to debug problem. I was able to realize FC1 command was wrong in my file.

Previously, it was set to a default value of:

FC1 'D' 1 'EHZ'

I changed it to:

FC1 'D' -1

According to documentation, -1 works as a wildcard and will use all components for Md calculation.

Now, a strange fact is that I get different location results when changing FC1... I am working with a single day high-VT activity dataset, where more than 200 events are located on a single day.

If I use the FC1 'D' 1 'EHZ' setting, hyp2000 will locate 275 events, while if I use FC1 'D' -1, it will locate 266 events.

Can this lower number be related to the fact that Md calculation takes more time, and some buffer may overflow?. 

Thanks,

Victor

[Dietz, Lynn D]

Changing FC1 should not change how many events are located. If you are playing this dataset thru your test EW system as fast as possible, perhaps you have an overflow issue somewhere?  There used to be an EW module 'eqbuf' that one could stick between eqcoda and hyp2000_mgr. Not sure if that module still exists ...

Otherwise, I would find an event from run1 (that produces more eqs) that "gets missed" in run2, and then track the progress of that eq thru the run2 logs.

---

From: earthwo...@googlegroups.com <earthwo...@googlegroups.com> on behalf of Victor Preatoni <vpre...@gmail.com>

Sent: Wednesday, December 27, 2023 9:31 AM

To: Earthworm Community Forum <earthwo...@googlegroups.com>

Subject: [EXTERNAL] Re: [Earthworm Forum] HYP2000 Md always 0.00

To view this discussion on the web visit https://groups.google.com/d/msgid/earthworm_forum/82d9a527-d5a4-442e-af21-07d2b7003c27n%40googlegroups.com.