joey_meyer

Glad you enjoyed it! I don't have plans to make more and sell them, but the robot is safe–like I mentioned in the other comment it actually moves slower than the speed it does in the video and the servos aren't powerful enough to significantly injure someone.

The robot actually moves much slower than the speed in the video, so it would be hard to get caught without trying. The servos are also weak enough that they wouldn't be able to really hurt you.

Ah yes clearance height is the same for all pieces, the servo raises the piece to the piece height + the "resting" height. Relevant code can be found here:

https://github.com/joeymeyer/raspberryturk/blob/master/raspb...

I considered moving pieces via magnet underneath the board as well, but decided to go with the arm to remain more true to the original Turk. The robotics was the hardest part of this project for me since my experience is software not hardware, but I found the resources on the ServoCity website to be incredibly useful.

The error was too high so I haven't integrated it into the actual code base yet, so it hasn't been a problem in practice yet! Ha. Yes I think the best thing I can do will be to collect more data, I am hoping that will close the gap a bit more. Also, I haven't spent that much time tuning hyperparameters.

It's hard-coded at the moment. I just measured the height of each piece and stored the values.

Thanks! No at the moment the robot just places it's pawn the last rank. You have to watch the status page on screen to see what it promoted it to. Definitely need to come up with a better way to do that.

The robotics components were the pricey part. The breakdown is something like this:

  - Table (w/ paint, wood, pipes, lights, etc): less than $50
  - Electronics (Raspi, camera, cables, electromagnet, microcontroller, etc): about $150
  - Robot arm (structural components + servos): $350

It's hard to say what I would do a second time around since there are aspects I still want to work on, I want to write my own chess engine for it!

Wow, my project is on the front page! Happy to answer questions if anyone has them.

Dan Carlin has an episode[0] of Hardcore History on this exact topic. I highly recommend it (along with the rest of the podcast).

[0] http://www.dancarlin.com/product/hardcore-history-10-the-wha...

Could it be the top comment of this somewhat recent post?

https://news.ycombinator.com/item?id=12152658

It was this HN comment that prompted me to read it, fascinating book. The topic of the post, Boltzmann brain, is also well worth reading into.

The alternative is to go halfway and just use nmap regardless of the context, apparently it's the way to go: http://nmap.org/movies/

I tend to agree with the article. I am a senior, studying computer science and also a tutor at the engineering building on campus. The large majority of students that come in and need help are from the CS1 and CS2 classes. It's really frustrating for me sometimes because these students typically know very little about how at program and they are asked to make decently large/complex programs. As a result they all think programming is this insanely hard field that only geniuses can understand. I tell them that learning programming is like learning a language, to someone that doesn't understand it or is learning it it looks like gibberish. However once you get it, it's just like reading. Unfortunately, most of the students don't believe me and end up not continuing CS.

In addition, at my university I feel like the majority of students who are in the upper level classes with me (CS majors past their second year) got credit for the intro courses in high school. The way I interpret this is, it is a lot more likely for students to continue study CS past the first year if they take high school CS, which is a longer slower moving intro CS course.

I think the intro courses need to be much easier. They are discouraging too many smart students!