But the tricky part of the machine vision problem seems to be the sensor design. Doing this with straightforward machine vision doesn't seem hard either. The background is static and the stick is moving. Plenty of industrial systems use vision to work out which direction a stick is pointing.
Yet the video is titled "Pencil Balancer on Changing Background" (emphasis mine).
Strange, the memory use of my Firefox 3.6.13 is stable at ~200MB. If yours is leaking, it's quite likely some difference between my FF and yours, say an extension you have installed that I don't.
Actually in IPv4 the TTL is in seconds, but every hop must reduce it by at least 1, making it effectively a hop count (and it's often implemented as such). In IPv6 the TTL field is renamed "Hop Count", and is an actual hop count.
This would be more awesome if it had 6 flames and they were hooked into the different strings of the Squier guitar, with perhaps flame size matching position down the string.
It is indeed an example on how not to implement buffering, and older buffered routers used to be even worse: they'd use one buffer per physical network socket, which may be serving multiple endpoints, allowing one person to trash everyone's latency.
For true fairness, you need one buffer per TCP connection.
Actually with the HTTP spec you just request "the whole file", and the webserver sends it all to you. You don't request individual chunks of the file. Other protocols (e.g. bittorrent) work on file chunks and so can actually do this.
At the TCP level, the modern spec allows the sender to send more packets without acks on the previous packets, which massively increases throughput on high-latency connections. You can only scale the rate you receive the transfer at by dropping/delaying the packets, and that only works if the sender cares. Dropped packets just get resent, reducing your bandwidth even more, so routers normally delay (buffer) the packets, which (guess what) trashes your latency.
As an extreme example, say you request a 1GB file from a download site. That site has a monster internet connection, and manages to transmit the entire file in 1 second. The file makes it to the ISP at that speed, who then buffers the packets for slow transmission over your ADSL link, which will take 1 hour. During that time you try to browse the web, and your PC tries to do a dns lookup. The request goes out ok, but the response gets added to the buffer on the ISP side of your internet connection, so you won't get it until your original transfer completes. How's 1 hour for latency?
The situation is only not that bad because: A: Most download sites serve so many people at once and/or rate limit so they won't saturate most peoples' connections B: Most buffers in network hardware are still quite small
The problem is that maxing your connection from one site is causing everything else you do on your connection to be delayed / dropped as well, because it ends up queued behind anything that got buffered mid-transit from the first site. With a smaller buffer the large transfer would start to drop packets and back off sooner, allowing packets from other sources to "hop the queue".
It was essentially failing a comparison of a number to itself, because one copy was in the 80-bit fpu register and the other had been truncated into a 64-bit memory location.
I was just answering drsmithy's question. IMO a crime for being drunk without causing any trouble is an insanity. Presumably a US-only insanity, I haven't heard of a similar law here in the UK.
The flipside being, of course, that without a "public intoxication" charge, you have no way of stopping some drunken moron from wandering the streets being a nuisance or yelling abuse at passers-by.
In IPv6 every PC will automatically get a static Link-Local address (based on the static link-local prefix and its MAC) in addition to its (probably varying) public address (based on your ISP-assigned prefix and its MAC).
You mean their owners are. In most cases they are subsidiaries rather than brands, and in all cases their actual factories are in the UK. They don't make knock-offs of foreign designs (like Vauxhall vs Opel). They may not be all-British, but it's hard to argue that they're not British.
Slashdot Mirror
with a whopping 2 seeders
One of whom is on dial-up (judging from the speed) and the other is not accepting connections?
I stopped using torrents because of that.
But the tricky part of the machine vision problem seems to be the sensor design. Doing this with straightforward machine vision doesn't seem hard either. The background is static and the stick is moving. Plenty of industrial systems use vision to work out which direction a stick is pointing.
Yet the video is titled "Pencil Balancer on Changing Background" (emphasis mine).
Strange, the memory use of my Firefox 3.6.13 is stable at ~200MB. If yours is leaking, it's quite likely some difference between my FF and yours, say an extension you have installed that I don't.
Actually, the first response is google answering the question itself, not a search result. Try it.
Google: define: string quartet. What's wrong here?
Actually in IPv4 the TTL is in seconds, but every hop must reduce it by at least 1, making it effectively a hop count (and it's often implemented as such). In IPv6 the TTL field is renamed "Hop Count", and is an actual hop count.
For the other extreme, get the Fender Squier Stratocaster Pro Controller for Rock Band 3, a real guitar with midi pickups and some xbox 360 buttons for playing Rock Band 3 in Pro mode.
This would be more awesome if it had 6 flames and they were hooked into the different strings of the Squier guitar, with perhaps flame size matching position down the string.
Fair queuing in the routers is the real solution to this.
Just did some reading on the TCP window size, I apparently had it confused with the congestion window size (which is estimated by the sender).
Again though, it only works if the sender sticks to it, and if you advertise a correct window size (which would be very difficult to do).
It is indeed an example on how not to implement buffering, and older buffered routers used to be even worse: they'd use one buffer per physical network socket, which may be serving multiple endpoints, allowing one person to trash everyone's latency.
For true fairness, you need one buffer per TCP connection.
Actually with the HTTP spec you just request "the whole file", and the webserver sends it all to you. You don't request individual chunks of the file. Other protocols (e.g. bittorrent) work on file chunks and so can actually do this.
At the TCP level, the modern spec allows the sender to send more packets without acks on the previous packets, which massively increases throughput on high-latency connections. You can only scale the rate you receive the transfer at by dropping/delaying the packets, and that only works if the sender cares. Dropped packets just get resent, reducing your bandwidth even more, so routers normally delay (buffer) the packets, which (guess what) trashes your latency.
So naturally, I instantly get modded down.
As an extreme example, say you request a 1GB file from a download site. That site has a monster internet connection, and manages to transmit the entire file in 1 second. The file makes it to the ISP at that speed, who then buffers the packets for slow transmission over your ADSL link, which will take 1 hour. During that time you try to browse the web, and your PC tries to do a dns lookup. The request goes out ok, but the response gets added to the buffer on the ISP side of your internet connection, so you won't get it until your original transfer completes. How's 1 hour for latency?
The situation is only not that bad because:
A: Most download sites serve so many people at once and/or rate limit so they won't saturate most peoples' connections
B: Most buffers in network hardware are still quite small
The problem is that maxing your connection from one site is causing everything else you do on your connection to be delayed / dropped as well, because it ends up queued behind anything that got buffered mid-transit from the first site. With a smaller buffer the large transfer would start to drop packets and back off sooner, allowing packets from other sources to "hop the queue".
It was essentially failing a comparison of a number to itself, because one copy was in the 80-bit fpu register and the other had been truncated into a 64-bit memory location.
I would define length as distance around the hard-disk data track, it would likely be some impressively large number.
Quake required you to hold a button to use mouselook, unless you made some tweaks. That alone would make keyboard+mouse very annoying to use.
< = <
&lt; = <
recurse as needed.
I believe it's a reward for people with good karma.
I was just answering drsmithy's question. IMO a crime for being drunk without causing any trouble is an insanity. Presumably a US-only insanity, I haven't heard of a similar law here in the UK.
The flipside being, of course, that without a "public intoxication" charge, you have no way of stopping some drunken moron from wandering the streets being a nuisance or yelling abuse at passers-by.
"Disturbing the peace"?
Beta purchasers are not eligible for the unlimited future updates, unfortunately.
They are eligible for all updates up until the final release, and all bugfixes, though.
In IPv6 every PC will automatically get a static Link-Local address (based on the static link-local prefix and its MAC) in addition to its (probably varying) public address (based on your ISP-assigned prefix and its MAC).
You mean their owners are. In most cases they are subsidiaries rather than brands, and in all cases their actual factories are in the UK. They don't make knock-offs of foreign designs (like Vauxhall vs Opel). They may not be all-British, but it's hard to argue that they're not British.
And don't get me started on British automobiles....
What's wrong with Bentleys? Or Rolls-Royces? Or Jaguars? Or Land Rovers? What about Lotus?
There are more, too.