mag picks rejected

[Mitch Withers]

We're having a problem with coda picks being rejected, especially with N4 network channels.  Our jiggle logs look something like below.  Some of the rejected picks have smaller residuals than the accepted ones.  But I don't have enough information to understand why they're being rejected and what to change to fix it.  Does anyone know how I can fix this or get more information to troubleshoot?

DEBUG: MagnitudeEngineTN db channelList lookup enabled: false
HypoinvMd filterDataBeforeChannelMagCalc TOTAL channels rejected: 0
HypoinvMd filterDataBeforeSummaryMagCalc is rejected:  N4 U56A HHZ 00
HypoinvMd filterDataBeforeSummaryMagCalc is rejected:  N4 W57A HHZ 00
HypoinvMd filterDataBeforeSummaryMagCalc is rejected:  N4 KMSC HHZ 00
HypoinvMd filterDataBeforeSummaryMagCalc is rejected:  N4 V58A HHZ 00
HypoinvMd filterDataBeforeSummaryMagCalc is rejected:  N4 U54A HHZ 00
HypoinvMd filterDataBeforeSummaryMagCalc TOTAL channels rejected: 5
MagEng magnitude statistics for event id: 60083228 wgtMedian: 1.78 median: 1.78 mean: 1.75 stdDev: 0.14 medDev: 0.05 count:   4
    Channel                 Dist ChMag Resid  Corr InWgt    Wt  Segments
  ET_TVNC2_EHZ_00           65.4  1.86  0.08  0.00  1.00  1.00   1
  ET_DSNC_EHZ_00            99.4  1.76 -0.02  0.00  1.00  1.00   1
  CO_PAULI_HHZ_00          155.4  1.81  0.03  0.00  1.00  1.00   1
  ET_TRYN_EHZ_00           162.6  1.55 -0.23  0.00  1.00  1.00   1

HypoinvMd filterDataAfterSummaryMagCalc TOTAL channels rejected: 5

[Renate Hartog]

I believe you can get a bit more info about why they are rejected. You've got to crank up all the debug flags. In your Jiggle properties file I would set these to "true":

debug=true

debugCommit=false

debugSQL=false

debugTN=true <--------------------- this is probably the one that will let the magnitude engine be more verbose.

verbose=true   <--------------------- or maybe this one.

I will often set all of the above to true when I am trouble shooting something.

--
You received this message because you are subscribed to the Google Groups "AQMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to anss-aqms+...@googlegroups.com.
To post to this group, send email to anss...@googlegroups.com.
Visit this group at https://groups.google.com/group/anss-aqms.
To view this discussion on the web visit https://groups.google.com/d/msgid/anss-aqms/CAP3dVmPVrW9G%2B5dBhT0qbof61LDuT0GKjQ54jA1FmtvS_OHAfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Yoon, Clara]

Set "debug=true" and “verbose=true” in your magnitude properties file (such as mdMagEng.props or mlMagEng.props), see https://pasadena.wr.usgs.gov/jiggle/magprops.html.

Also, set "debug=true”, "delegateDebug=true”, and “verbose=true” in your main Jiggle properties file, see https://pasadena.wr.usgs.gov/jiggle/JiggleProperties.html.

Another thing to try - If your magnitude properties file has "requireBothHoriz=true", try setting "requireBothHoriz=false" and run Jiggle again with your N4 network channels.  

To view this discussion on the web visit https://groups.google.com/d/msgid/anss-aqms/CAPWJi93YpuNoS7eLedkew0KuWTrEFgbcQ7-Yu1sY8gQp%3DDWMmg%40mail.gmail.com.

[Mitch Withers]

Sorry I should have closed the loop with the list.  The problem was I hadn't updated my channelmap tables and then when I did, I neglected to "unreject" the coda picks before testing. 

To view this discussion on the web visit https://groups.google.com/d/msgid/anss-aqms/CABsbyfynR5YxvJb5umLsE694TFs8sjveopOeCh8_S_%2Bz0J%3Dydw%40mail.gmail.com.