Skip to Content
Last modified by robert on 2026/09/07 17:05
From version 119.2
edited by robert
on 2026/09/07 15:45
Change comment: There is no comment for this version
To version 120.3
edited by robert
on 2026/09/07 17:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -441,15 +441,26 @@
441 441  
442 442  = Copying raw MiniSeed data without the Software =
443 443  
444 -Lately we have been advocating for not writing to the proprietary DFD format (we don't know how this is structured) in the event that the software is misbehaving or one wants to use a linux machine or for whatever reason. This involves simply reading the devices as a mounted USB device and copying off the .MiniSeed files manually~-~- easy enough!
444 +Lately we have been advocating for not writing to the proprietary DFD format (we don't know how this is structured!) in the event that the software is misbehaving or one wants to use a Linux or OSX machine or for whatever reason. If the nodes are programmed with an output set to MiniSeed, harvesting can be as simple as reading the devices as a mounted USB device and copying off the .MiniSeed files manually.
445 445  
446 -However please note the filename and channel convention:
446 +However please note the filename and channel convention. Raw data (here a BD3C-5) as usual has completely bizarre default channel codes (e.g. this should be DH?). Take care to interpret XYZ correctly though- many manufacturers will define X as East and Y as North to coincide with a typical Cartesian frame. **This is backwards here.**
447 447  
448 -3 Trace(s) in Stream:
448 +This raw stream...
449 +
450 +##3 Trace(s) in Stream:
449 449  XX.TEST..LHX | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples
450 450  XX.TEST..LHY | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples
451 -XX.TEST..LHZ | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples
453 +XX.TEST..LHZ | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples##
452 452  
455 +Should be renamed as:
456 +
457 +##3 Trace(s) in Stream:
458 +XX.TEST..DH**N** | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples
459 +XX.TEST..DH**E** | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples
460 +XX.TEST..DH**Z** | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples##
461 +
462 +With** X = +North, Y = +East, and Z = +Z**
463 +
453 453  = Instrument Response =
454 454  
455 455  We are aware that there are various different published responses for these instruments and trust very few of them. One has to be careful with how polarity is handled between groups as well, and if one is working in integer counts (the ANSIR default) or mV (unclear why anyone would use this as it makes file sizes enormous). The response information published below is in **counts** and seems to fit well in huddle tests. Note that the response is the same for all channels and all units (e.g. there are no bespoke calibrations!), all appear to be sample rate insensitive, and the IGU data has been inverted (multiplied by -1) as described here: [[5Hz Node Polarity Issues>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodePolarityIssues]]