Good idea! Why don't you start a Kickstarter campaign for an alarm clock that pours water on your face to wake you up? No need for a robot to go to your bathroom - it can have a water tank.
I've heard back from the users of my app that Sonalarm actually worked pretty well when they shared their bed with their partner. The idea is that you place your iPhone on your bedside table (which has to be at your side of the bed, so the other person sleeping will be out of range).
Starting with the iPhone 5, the iPhone actually has 3 built-in microphones. They are used to improve intelligibility during phone calls, but unfortunately on iOS an app can't record from multiple microphones directly (i.e. by getting 2- or 3-channel PCM sample data). I'm not sure how this is for Android phones. (Disclaimer: I'm the developer of the Sleep Cycle Sonalarm Clock app that I've referenced in the post.)
Starting with the iPhone 5, the iPhone actually has 3 built-in microphones. They are used to improve intelligibility during phone calls, but unfortunately an app can't record from multiple microphones directly (i.e. by getting 2- or 3-channel PCM sample data). I'm not sure how this is for Android phones.
I've had users report back that the Sonalarm app worked well for them while sharing the bed with their partner. You have a bit of directionality because both the loudspeaker and the mic are located at the bottom edge of the iPhone, and also range is limited to around 1 to 2 meters, depending on the selected sensitivity. (Disclaimer: I'm the developer of the Sleep Cycle Sonalarm Clock app that I've referenced in the post.)
I've read on a German website about the UW prototype that it requires a smartphone that can record from two microphones at the same time, so this probably solves the directional discrimination. The UW prototype uses 18-20 kHz which most adults can't hear. I know the iPhone's frequency range and it goes right up to 20 kHz for both playback and recording (disclaimer: I'm the developer of the Sonalarm app that I've referenced in the post and my app uses the 18.5 - 20 kHz range, IIRC).
I didn't have much time to look at the language guide, but in the short time I already discovered many things that exist in Scala, and even the syntax is very similar:
* Tuples
* Closures
* Swift seems to be a functional programming language, even more than Objective-C (the 'functions'/closures there are called blocks).
* For comprehensions
* var/val is named var/let here
My thinking was that if two far-away detectors measure an entangled pair of photons (e.g.), each detector will measure both possible results (e.g. up *and* down). Each detector and thereby their environment becomes entangled with that photon. So each detector and it's environment starts a new branch in their respective many-worlds reality. (One side of the branch for “up” and one branch for “down”).
When you later compare the measurements of the detectors, you will find the measurements pair up (for example they are opposite). In the classical interpretation this could be thought of as a “spooky action at a distance” (instantaneous synchronization). But in the many-worlds interpretation only the worlds where the two separate measurements pair up would survive (the worlds where there is no match would cease to exist, as you put it). This would require no instantaneous synchronization, but would appear as such at the moment when the station that is comparing the measurements is becoming entangled with both detectors, e.g. by receiving the measurement outcome information from both detectors. The four “realities” (e.g up-up, up-down, down-up, down-down) meeting at that moment would be reduced to two “realities”, by merging pairs of “compatible realities” (only up-down and down-up “survive”).
INAQP (I’m not a quantum physicist) so I hope all of this makes sense. And I guess I haven’t added much to the parent’s point except adding a (hopefully valid) example.
If any expert reads this, I would love to know where I can read more about these ideas. There would certainly be a term for this already.
I only wonder why this possibility isn’t discussed more often, I seems such an easy way out of the paradox.
You can also use the device in a single device mode (with headphones), as shown in the second video. I just thought that the dual device mode would be more interesting and therefore emphasized it in my submission.
Nobody in their right mind would buy two iOS devices just to use this app. But somebody who's got two of them already might consider buying this app for under a dollar. (Just one purchase required if you have both devices on the same iTunes account.)
Please watch the second video, it shows how the app can be used with just one iOS device and headphones.
I agree that by having the clocks exactly synchronized this could be a lot easier. (But even 1 ms of deviation means an uncertainty of around 34cm.) The challenge was to do it without having the devices synced by an external source (it works on iPod touch devices and iPad as well) and without using a communication channel other than sound.
Minor correction: the so called one time pad is easily proven to be uncrackable by any method. The only problem with it, of course, is the key exchange. (The key is as long as the message, and needs to be securely transferred beforehand.)
The "App Store lottery". That's what I keep reading on developer forums. But except for buying a ticket you have to work really hard creating an app or game.
I hope to hit the jackpot with my newest app called Acoustic Ruler Pro which lets you measure distances of up to 25 meters (82 feet) by clocking the time delay of the emitted sound waves.
About I year ago I've started a small project with a friend, written in C++, that does some improvements to lossless audio compression (currently to FLAC). It calculates the autoconvolution of the audio signal to find similar parts in the audio. Especially for electronically generated music, this can be used to predict other parts in the audio, and thus reduce the entropy of the signal (i.e. compress the file better).
If you (or anybody else) are interested in further development, I would open-source the project, and may be start working on it again a bit myself. Just drop me a line, at polarspaceflo (at) googlemail (dot) com.
I recommend you find some source code virus, one that finds a source file and copies itself into the source file... While it has to rely on somebody compiling the source in order to spread (if it is written in a compiled language), this is easier to understand and analyze (and remove!) than a "binary virus"
Here is a long list of problems that have superpolynomial i.e. more than polynomial speedup compared to classical computation. Even though the author doesn't think so many do have practical applications.
You can improve the algorithm to go from exponential to constant time (ignoring the finiteness of the speed of light) if you don't apply the optical setup to the TSP, but to the existence of a http://en.wikipedia.org/wiki/Hamiltonian_path or circle, in a given input graph, which is still NP-Complete.
You can make sure a photon has passed through every node exactly once if you put power of two delays in every node. If the delays sum up to 111....111 (in binary notation) a Hamiltonian exists. Big plus: you're done with only one measurement.
Yes, but at least in theory the paths can be made almost infinitely short. No you can't because the 'algorithm' sums powers of two length to make sure every node was visited exactly once. If you make variable a arbitrarily small, imprecisions sum up, and you can't be sure any more that every node was visited exactly once.
The paper says that the path the photons have to travel for a TSP with N cities is
N*d + a*(2^N+1)
Since the speed of light is finite, the algorithm still takes O(2^N) i.e. exponential time to complete.
A miniature sender for the german radio controlled clocks (DCF-77). Only using a PIC 16F84 + resonator, resistors and the antenna of a broken radio controlled clock, changed from parallel to series L-C resonator. It could set the radio controlled clocks within a short radius, and was used as a birthday gift (celebrating on the birthday, time signal was of the day before 11:55 pm, so we could repeatedly clink glasses as the date changed to my friends birthday).
Slashdot Mirror
Good idea! Why don't you start a Kickstarter campaign for an alarm clock that pours water on your face to wake you up? No need for a robot to go to your bathroom - it can have a water tank.
I've heard back from the users of my app that Sonalarm actually worked pretty well when they shared their bed with their partner. The idea is that you place your iPhone on your bedside table (which has to be at your side of the bed, so the other person sleeping will be out of range).
Starting with the iPhone 5, the iPhone actually has 3 built-in microphones. They are used to improve intelligibility during phone calls, but unfortunately on iOS an app can't record from multiple microphones directly (i.e. by getting 2- or 3-channel PCM sample data). I'm not sure how this is for Android phones. (Disclaimer: I'm the developer of the Sleep Cycle Sonalarm Clock app that I've referenced in the post.)
Starting with the iPhone 5, the iPhone actually has 3 built-in microphones. They are used to improve intelligibility during phone calls, but unfortunately an app can't record from multiple microphones directly (i.e. by getting 2- or 3-channel PCM sample data). I'm not sure how this is for Android phones.
I've had users report back that the Sonalarm app worked well for them while sharing the bed with their partner. You have a bit of directionality because both the loudspeaker and the mic are located at the bottom edge of the iPhone, and also range is limited to around 1 to 2 meters, depending on the selected sensitivity. (Disclaimer: I'm the developer of the Sleep Cycle Sonalarm Clock app that I've referenced in the post.)
I've read on a German website about the UW prototype that it requires a smartphone that can record from two microphones at the same time, so this probably solves the directional discrimination. The UW prototype uses 18-20 kHz which most adults can't hear. I know the iPhone's frequency range and it goes right up to 20 kHz for both playback and recording (disclaimer: I'm the developer of the Sonalarm app that I've referenced in the post and my app uses the 18.5 - 20 kHz range, IIRC).
I didn't have much time to look at the language guide, but in the short time I already discovered many things that exist in Scala, and even the syntax is very similar:
* Tuples
* Closures
* Swift seems to be a functional programming language, even more than Objective-C (the 'functions'/closures there are called blocks).
* For comprehensions
* var/val is named var/let here
Does the following make any sense?
My thinking was that if two far-away detectors measure an entangled pair of photons (e.g.), each detector will measure both possible results (e.g. up *and* down). Each detector and thereby their environment becomes entangled with that photon. So each detector and it's environment starts a new branch in their respective many-worlds reality. (One side of the branch for “up” and one branch for “down”).
When you later compare the measurements of the detectors, you will find the measurements pair up (for example they are opposite). In the classical interpretation this could be thought of as a “spooky action at a distance” (instantaneous synchronization). But in the many-worlds interpretation only the worlds where the two separate measurements pair up would survive (the worlds where there is no match would cease to exist, as you put it). This would require no instantaneous synchronization, but would appear as such at the moment when the station that is comparing the measurements is becoming entangled with both detectors, e.g. by receiving the measurement outcome information from both detectors. The four “realities” (e.g up-up, up-down, down-up, down-down) meeting at that moment would be reduced to two “realities”, by merging pairs of “compatible realities” (only up-down and down-up “survive”).
INAQP (I’m not a quantum physicist) so I hope all of this makes sense. And I guess I haven’t added much to the parent’s point except adding a (hopefully valid) example.
If any expert reads this, I would love to know where I can read more about these ideas. There would certainly be a term for this already.
I only wonder why this possibility isn’t discussed more often, I seems such an easy way out of the paradox.
The times when Apple would reject any other browser are over. There's Chrome avaible here: https://itunes.apple.com/de/app/chrome/id535886823?mt=8 I even managed to get my own browser on the app store https://itunes.apple.com/us/app/resworb/id520270702?mt=8. I'm still waiting to win a most-useless-app-award with that one though.
I got one as a child. Seems they have a few new models now. I'm not sure if they ship to the US. http://www.kosmos.de/kosmos/wrs/wrs.nsf?openDatabase&_id=4002051636029&_lang=DE http://www.kosmos.de/kosmos/wrs/wrs.nsf?openDatabase&_id=4002051635213&_lang=DE http://www.kosmos.de/kosmos/wrs/wrs.nsf?openDatabase&_id=4002051635718&_lang=DE
Or two iOS devices...
You can also use the device in a single device mode (with headphones), as shown in the second video. I just thought that the dual device mode would be more interesting and therefore emphasized it in my submission.
Thanks for clearing this up! I will use the word accuracy in the next update!
Nobody in their right mind would buy two iOS devices just to use this app. But somebody who's got two of them already might consider buying this app for under a dollar. (Just one purchase required if you have both devices on the same iTunes account.)
Please watch the second video, it shows how the app can be used with just one iOS device and headphones.
I agree that by having the clocks exactly synchronized this could be a lot easier. (But even 1 ms of deviation means an uncertainty of around 34cm.) The challenge was to do it without having the devices synced by an external source (it works on iPod touch devices and iPad as well) and without using a communication channel other than sound.
Minor correction: the so called one time pad is easily proven to be uncrackable by any method. The only problem with it, of course, is the key exchange. (The key is as long as the message, and needs to be securely transferred beforehand.)
The "App Store lottery". That's what I keep reading on developer forums. But except for buying a ticket you have to work really hard creating an app or game.
I hope to hit the jackpot with my newest app called Acoustic Ruler Pro which lets you measure distances of up to 25 meters (82 feet) by clocking the time delay of the emitted sound waves.
Here are two short videos showing what the app can do: http://iqtainment.wordpress.com/acoustic-ruler/.
Hello, anonymous submitter,
About I year ago I've started a small project with a friend, written in C++, that does some improvements to lossless audio compression (currently to FLAC). It calculates the autoconvolution of the audio signal to find similar parts in the audio. Especially for electronically generated music, this can be used to predict other parts in the audio, and thus reduce the entropy of the signal (i.e. compress the file better).
If you (or anybody else) are interested in further development, I would open-source the project, and may be start working on it again a bit myself. Just drop me a line, at polarspaceflo (at) googlemail (dot) com.
I recommend you find some source code virus, one that finds a source file and copies itself into the source file... While it has to rely on somebody compiling the source in order to spread (if it is written in a compiled language), this is easier to understand and analyze (and remove!) than a "binary virus"
Here is a long list of problems that have superpolynomial i.e. more than polynomial speedup compared to classical computation. Even though the author doesn't think so many do have practical applications.
Thanks,
Did you hear of www.kalador.com ? Any opinions?
You can improve the algorithm to go from exponential to constant time (ignoring the finiteness of the speed of light) if you don't apply the optical setup to the TSP, but to the existence of a http://en.wikipedia.org/wiki/Hamiltonian_path or circle, in a given input graph, which is still NP-Complete.
You can make sure a photon has passed through every node exactly once if you put power of two delays in every node. If the delays sum up to 111....111 (in binary notation) a Hamiltonian exists. Big plus: you're done with only one measurement.
The paper says that the path the photons have to travel for a TSP with N cities is
N*d + a*(2^N+1)
Since the speed of light is finite, the algorithm still takes O(2^N) i.e. exponential time to complete.
A miniature sender for the german radio controlled clocks (DCF-77). Only using a PIC 16F84 + resonator, resistors and the antenna of a broken radio controlled clock, changed from parallel to series L-C resonator. It could set the radio controlled clocks within a short radius, and was used as a birthday gift (celebrating on the birthday, time signal was of the day before 11:55 pm, so we could repeatedly clink glasses as the date changed to my friends birthday).