The Binary Chop is a technique most typically associated with data processing but the logic applies to just about anything.
When there is a large number of cases to be examined for a problem (or anything in some other purpose), they can be examined and tested individually and this will give a perfect result but it's time-consuming.
The alternative is to test one half all at once. If the system fails when that half is active, you know the problem is in this set and not the other half which is instantly vindicated.
Continue with this binary chop process within the subset of cases that was active and repeating this process a relatively short number of times will identify the desired case.
(Ed: the above won't catch a situation with two bugs rather than just one)
In fact, it will. After repairing the one you found and bringing all back up again, if it fails then you know there's another one or your repair to the first one sucked. Repeat your binary chop from the top and you will find your second bad guy in exactly the same way. Even if you do need to repeat it, this mechanism will still be significantly faster than comparing case by case.
(Ed: you're thinking of being clever?)
Not that clever as I think why not bring all the hardware online at once as only one installs any software and that won't happen automatically. If that fails, pull it back off and test one by one. This approach looks good to me and will keep me amused until tomorrow when I can start throwing software at it.
Update:
Things look more civilized already.
USB 3.0 drive online for all video, audio files
Logitech headset for Skype
Mackie mixer for all audio kit
Kensington Trackball
No software was installed and Skype is not active. It's strictly an Apple environment but tomorrow it will start to expand.
When there is a large number of cases to be examined for a problem (or anything in some other purpose), they can be examined and tested individually and this will give a perfect result but it's time-consuming.
The alternative is to test one half all at once. If the system fails when that half is active, you know the problem is in this set and not the other half which is instantly vindicated.
Continue with this binary chop process within the subset of cases that was active and repeating this process a relatively short number of times will identify the desired case.
(Ed: the above won't catch a situation with two bugs rather than just one)
In fact, it will. After repairing the one you found and bringing all back up again, if it fails then you know there's another one or your repair to the first one sucked. Repeat your binary chop from the top and you will find your second bad guy in exactly the same way. Even if you do need to repeat it, this mechanism will still be significantly faster than comparing case by case.
(Ed: you're thinking of being clever?)
Not that clever as I think why not bring all the hardware online at once as only one installs any software and that won't happen automatically. If that fails, pull it back off and test one by one. This approach looks good to me and will keep me amused until tomorrow when I can start throwing software at it.
Update:
Things look more civilized already.
USB 3.0 drive online for all video, audio files
Logitech headset for Skype
Mackie mixer for all audio kit
Kensington Trackball
No software was installed and Skype is not active. It's strictly an Apple environment but tomorrow it will start to expand.
No comments:
Post a Comment