79 karma · joined September 14, 2017
Hearing aids though could be ripe for disruption by improved computational power and large supply chain leverage. So it will be a matter of whether or not Apple/Google/ back off once they meet the intractable reality of regulatory compliance in a limited market a la their infrastructure plans.
I think it's most likely that they will buy up those medical companies for expertise, then spin off the medical device manufacturing into a new separate company or otherwise sell it off but keep the key engineers to roll into other random consumer products that are less regulated and more profitable. This is what Google has more or less done with robotics after buying basically every major robotics research company in the US a few years back.
Also copper tape is wonderful but it will also cut the hell out of you so wear gloves.
In any commercial property I have ever dealt with the tenant is responsible for any renovations because every tenant is looking to outfit the space differently. If the market is heavily in the favor of the renters at the time, I have seen landlords offer discounts on the rent to help cover certain renovations, typically expanded electrical service and the like, but even that has it's limits as landlords typically have costs associated with ownership they need to cover out of the rent.
See: https://en.wikipedia.org/wiki/Shadowgraph
Penn State did a lot of pioneering work in and with this technique.
The kernel of a filter would be it's impulse response, which is what you convolve by to get the filter response. That's where the sloppy terminology comes from. A kernel though does not need to be a filter.
A kernel is a function whose product maps a point in one domain onto another domain. For example, the Fourier transform has a kernel of e^jwt. The integral (or sum if discrete) of these products over the function is the transform because it maps the entire function into it's new space. A filter is a function typically defined as having product behavior in the frequency(transformed) domain, which is equivalent to convolution in the time(original) domain. A window is a function that has product behavior in the time(original) domain, and thus convolution behavior in the frequency(transformed) domain.
Particularly in linear algebra (matrix math), if something is a kernel function, there are certain mathematical implications.
Another confusing bit here is that the convolution they are performing to project the original function (the larger image matrix) onto the smaller one isn't a proper convolution, it has a hidden window function in the way the operation is being performed to restrict the output to only the fully overlapped area of an otherwise linear 2D convolution. This is typically called a cropped convolution in image processing.
All that said, it's not a fundamentally bad idea. Pseudo-random xor encoding of signals is a technique used all the time to increase orthoganality between signals for a variety of encoding schemes.
Fuse based programming would have a whole host of issues. You either need a destructive fill device or load at the factory. If you load at the factory you have to trust them to not retain copies, keeping in mind that it will probably me manufactured in China. If you use a fill device you open up for destructive programming (IC fuses) you open up a bunch of liability for accidental damage to the device plus the cost of a technician plus training can quickly swamp out the cost of your low cost sensor network.
Finally, these sorts of networks work best with asynchronous uni-diretional communication applications. This makes good crypto-practices very difficult. If you chose full crypto and handshake protocols, the amount of data you spend just exchanging keys and handshakes will exceed the data the sensors collect.
The bigger issue is that the entire point of this system is to remove cost of deployment and maintenance for cheap highly distributed lo-fi systems. The cost of keying all those devices for encryption would defeat the purpose. Also the added data overhead of the encryption would possibly exceed the amount of actual data you are trying to get out of the system. Also, why do you even want to encrypt it in the first place?