Agreed, this series is excellent, and takes a very interesting look at exactly this sort of thing.

In Canada anyway, any Engineer can get a P.Eng. This includes civil, electrical, mechanical, computer engineering, etc.. . You have to be a member of your local Engineering Society, and do some work experience reports and pass an Ethics exam.

I remember reading the Belgariad (first book is Pawn of Prophecy), and enjoying it a lot when I was younger, rereading it several times. It's a very easy read, and is definitely suitable for a younger audience.

By QAM to analog RF, they mean digital QAM64B or QAM256B to analog NTSC video, so it is in fact the correct box.

That said, it seems like it's likely a lot more expensive than a bank of set top boxes, which would likely be a better choice.

I'm not sure, you would have the contact the company for more information (not my department to sell things ;) ). I would guess it's closer to the $5K-$10k range though.

Logged in as non-AC and updated with an actual clickable link:
http://www.vecima.com/products.php?line=1026&item=1083

Disclaimer: I work for Vecima networks, but this system does do exactly what you want, and is already being used in that capacity in many other places, including some hotels.

Seconding this, this game is excellent from that perspective, and is much slower moving than most modern RTSes.

Read the Lost Fleet series ( http://en.wikipedia.org/wiki/The_Lost_Fleet ) by Jack Campbell. He's got self-consistently handled space battles, and the same kind of light-hours/light-minutes lag, with fleets of ships essentially making high speed passes at each other, shooting for a miniscule fraction of a second, then turning around and doing it again. Obviously has some fantasy technology like deflector shields and artificial gravity, but still awesome.

As someone who writes Verilog for a living, I would have to say yes!

This is definitely an excellent museum, and I recommend visiting if you're going across Western Canada in your trip.

Seconding this. I felt much the same. I visited this for the first time about a month ago, and was very impressed. Definitely one of the best museums I have ever been to.

They have a large room with a bunch of military vehicles/artillery as well, spanning from bore loaded cannons to Leopard Tanks and M109 Mobile Guns. Some of these have decent signage (most of the tanks, and vehicles along the outer building wall), while a lot of the stuff in the middle is interesting, but unfortunately not presented with any documentation.

The main galleries, however, are excellent, as described. If you're going soon, there's an exhibit about camouflage that's currently running there, created in conjunction with the Imperial War Museum in London, that was quite interesting. If you're hardcore into museums, as you seem to be, allocate a full day for this one.

This can't happen (it used to about a year and a half ago with the old timecard selling system). With PLEX though, as soon as you purchase the PLEX, the time is immediately credited to your account, and the PLEX is used up, so you can't resell the thing.

My workplace is primarily a Verilog shop (FPGA design only, no ASICs), though we're forced to use VHDL on occasion when a piece of IP is written in it, or to interface with Xilinx's EDK toolchain, which is mostly written in VHDL. We haven't switched to using System Verilog, but we do attempt to stick to the Verilog 2001 style coding, instead of the Verilog 95 standard. Verilog 95 makes the same code significantly longer and more annoying to change. Things like generate statements and parameter passing have been in place in Verilog since that standard, and all the toolchains that we've used (Xilinx, Altera, Synplicity) support it, albeit only fully since the latest ISE 11 software release in Xilinx's case. Having only done a minimal amount of VHDL, I can tell you that I can't stand it due to the excessive verbosity that is required to do anything in the language, though one of my wishes is that Verilog removed implicit variable declaration, as occasionally a typo will cause a design not to function correctly, which as mentioned will not happen in VHDL. A compiler option for that one would be nice ;). To answer your question as to which you should teach, I would go with Verilog as I find it's easier to use (which may be bias on my part, having used it far more than VHDL), but make sure that you teach "clean" ways of writing the HDL. I've seen a fair bit of excessively verbose, hard to read Verilog code (a lot of the code Xilinx provides for their parts is like this) which could be a lot cleaner if it was written differently. Another thing that I think would be a useful thing to go over is each step of the FPGA build and what it's actual purpose is. What is the output of the synthesizer? What is the output of the mapper?

I hope this translates into further speed ups for EVE online down the road.