Ticket #106 (closed defect: fixed)

Opened 10 years ago

Last modified 10 years ago

localmag under 7.4 doesn't work on Windows

Reported by: paulf Owned by: stefan
Priority: critical Milestone: Windows
Component: localmag Version: 7.5
Keywords: Cc:

Description

The localmag code works fine in a new memphis magnitude test we created and tested for Linux/Mac? OS X/Solaris, but the same code does not work at all on Windows. It seems there must be some byte order issue because what works on Linux/Mac? OS X shows for a working station GNAR:

20110606_UTC_21:56:34 Processing <GNAR.HHN.NM.-->
Est P:    10.1281
Est S:    17.4203
requested times for GNAR.HHN.NM.--: start 1307397171.1904 end 1307397249.5442l
                received start 1307397170.2518 end 1307397250.2418
trace start:     1.2104 end:    79.5642 (7872)
search start:    12.4203 (1121) end:    60.6465 (5944)
20110606_UTC_21:56:34 Processing <GNAR.HHE.NM.-->
Est P:    10.1281
Est S:    17.4203
requested times for GNAR.HHE.NM.--: start 1307397171.1904 end 1307397249.5442l
                received start 1307397170.2518 end 1307397250.2418
trace start:     1.2104 end:    79.5642 (7872)
search start:    12.4203 (1121) end:    60.6465 (5944) 

but on windows has some non-sensical numbers:

20110607_UTC_14:56:27 Processing <GNAR.HHN.NM.-->
Est P:     9.8385
Est S:    16.9223
requested times for GNAR.HHN.NM.--: start 1307458363.0951 end 1307458441.1643l
        received start 1307458362.1100 end 1307458442.1000
trace start:     0.9351 end:    79.0043 (7855)
search start:    11.9223 (1099) end:    60.1008 (5917)
getPeakAmp: <GNAR.HHN.NM.--> z2p max (8.48899e+060) too small for pre-event threshold (1.39001e+061)
20110607_UTC_14:56:27 Processing <GNAR.HHE.NM.-->
Est P:     9.8385
Est S:    16.9223
requested times for GNAR.HHE.NM.--: start 1307458363.0951 end 1307458441.1643l
        received start 1307458362.1100 end 1307458442.1000
trace start:     0.9351 end:    79.0043 (7855)
search start:    11.9223 (1099) end:    60.1008 (5917)
getPeakAmp: <GNAR.HHE.NM.--> z2p max (5.13014e+056) too small for pre-event threshold (8.18717e+056) 

Change History

comment:1 Changed 10 years ago by paulf

  • Status changed from new to closed
  • Resolution set to fixed

Stefan and I fixed the windows compilation which produced bogus numbers and never got a magnitude (despite running fine). The issue was a output array was filled with garbage numbers (not zeroed). While this was easy to solve (zero the array before calling convertWave()), it was not easy to find!

The fix is in revision r4250

New version is 2.1.4 (DOES NOT EFFECT ANY UNIX build of this)

Note: See TracTickets for help on using tickets.