Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sigh. I've coded too much this week. My brain just immediately went to: comment out half the city at a time and binary search the source. Guess you can't really do that.

I wonder if the hum persists during a power outage.



Replace "comment out" by "turn off the electricity for" and maybe we can binary search it.


Your implicit assumption is that the hum is caused by something electrical; i.e. not a diesel engine or some natural cause.


But that's exactly the point. It would rule out a ton of stuff.


Then we can turn off the electricity for the whole town and see if it stops! :D


"The University of Windsor report said the hum’s likely source was blast furnace operations on Zug Island" ... which is over the border in the United States.

Cutting off the power to that island would be a good thing to try, but apparently the US is uncooperative.


But might have to turn off electricity for days if generators are used.


I don't think that Windsor was compiled with the debug flags turned on.


I've heard the hum in a city in the UK quite frequently. I hear it more on monday bank holiday mornings, oddly. So a weekday but less people at work.

I actually think it's the sound of traffic.


A few samples of amplitude should be able to triangulate it no?


I'd guess amplitude is massively affected by microphone sensitivity. This is not easy to measure and might depend on the direction.

Consider:

* The amount of walls between a mic and the outside.

* The absorbance/reflection of nearby materials, including their shape (flat surface will reflect sounds amplifying certain directions).

* The clutter between the source and receiver. Sound carries over water, not over cities or forests.

* Similarly, elevation of the receiver. Higher means less effect of clutter, and obviously, a hill in between will be an issue.

* Wind direction. Wind will blow the sound away.

It might still work with enough measurements with the same microphone, but that is not a given. A decent backup plan would be measuring the phase difference. This is still frustrated by wind, but doesn't depend on the senstivity of the microphones. It does require synchronization of the recordings, which might also be difficult.


It does require synchronization of the recordings, which might also be difficult.

Could you record with a multiple "microphone connected to a Raspberry Pi" setup, with the time synchronized using something like the NIST time signal[1] using an RTL-SDR, or a cellular signal, or GPS, or maybe using NTP?

[1]: https://www.nist.gov/pml/time-and-frequency-division/nist-ra...


Yes, that seems like the best approach. At 20Hz waves, ntp would probably be good enough. The real issue I can see is to get that time-data into the sound data. Maybe you could time-stamp the beginning of a recording, and start a new recording every minute (to compensate clock drift). That might work, biggest issue I see is potential variable latency between 'starting a recording' and the actual first recording happening.


Just install the debugging microphones all over, collect the data, find the source (if it's real).


Why install anything? Fly a drone around to take 5s recordings at points on a grid.


Since cities support parallel execution you must have an array to capture coherent debug information.


Wouldn't the sound of the drone be louder than the hum?


My assumption is that he would touch down first.


This actually sounds like a good idea.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: