search

jbrzusto / sensorgnome

master control process for a sensorgnome receiver
GNU General Public License v2.0
1 stars 2 forks source link

occasional crossing-over between pulse and Cornell tag detection records #52

Open jbrzusto opened 6 years ago

jbrzusto commented 6 years ago

This occurs with low frequency (35 instances out of 1.4M Cornell tag detections), but sometimes pulse records are interrupted by Cornell tag detection records. Why? e.g. in AVFP-3214BBBK1004-000128-2017-06-06T20-58-13.8170P-all.txt.gz we have this bold interloper:

p1,1496783517.5290,-7.083,-70.07,-78.42 p2,149T7,1496783517.646,8E1CC1CA 6783517.5633,4.247,-67.8,-74.12 p3,1496783517.6244,-5.92,-69.01,-75.38

jbrzusto commented 6 years ago

Likely a consquence of receivng detections from VAH over a stream connection to a UNIX domain socket. It would be better to use SOCK_DGRAM with a unix domain socket (which is reliable and doesn't re-order), but nodejs doesn't support this. Probably need to split data in vah.js::gotData, just as we do in vah.js::gotCmdReply, so that we only do Matron.emit(X) with full lines for X. It's okay for multiple lines to be sent at once, just not partial lines.

jbrzusto commented 6 years ago

For now, fix data files.