Hello!
I've been working through the introduction and chapter 1 of "The Elements of Computing Systems" on the train this morning. I think a good format for the first meeting would be to try and tackle the first project in small groups at the meeting itself. This project involves implementing Not, And, Or, Xor, Multiplexor, Demultiplexor, and multibit versions of the same using the hardware description language and hardware simulator provided on the website.
In preparation for that it would probably make sense to read the chapter (and optionally the introduction), and perhaps install the software and do one of the tutorials.
I've been doing the chip design on paper too, so that's also an option for us.
I can't make the meeting, sadly, so feel free to ignore the above and do your own thing. Having worked through the chapter this seems like a reasonable approach which would allow us to do some coding/problem solving as a group.
Bonus projects for those who are very familiar with the material might be: research optimal circuit design techniques, research implementing gates using transistors, or building a hardware simulator in a language of your choice, e.g ruby. :-)
Hope that helps,
Chris.
To
--
You received this message because you are subscribed to the Google Groups "London Computation Club" group.
To unsubscribe from this group and stop receiving emails from it, send an email to london-computatio...@googlegroups.com.
To post to this group, send an email to london-comp...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/london-computation-club/D9143D5E-4F65-4E62-9D53-674ED9CF4834%40codon.com.
FWIW I think writing a hardware simulator decomposes nicely into three self-contained (and not too difficult) parts
--
You received this message because you are subscribed to the Google Groups "London Computation Club" group.
To unsubscribe from this group and stop receiving emails from it, send an email to london-computatio...@googlegroups.com.
To post to this group, send email to london-comp...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/london-computation-club/CAMugUeLcnH0WYEv9yB81Eb0jOTH%2B4Xai4nfcp79csQ1MaYbdNg%40mail.gmail.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/london-computation-club/CAMHc1Kbn859ZApLUi%3DCc8%2BUkVGpSV5HwCiRzMwQgEepgZF2XQA%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "London Computation Club" group.
To unsubscribe from this group and stop receiving emails from it, send an email to london-computatio...@googlegroups.com.
To post to this group, send email to london-comp...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/london-computation-club/CALm1c-EtS4r07pFiPeXsYdfaz2oiCARoyJJ5AbjAfLe%3DF4iGMA%40mail.gmail.com.
> and the world propagates an intermediate state between those events, and that produces some weird bugsI think that is what I thought might be interesting how to solve - I wasn't immediately sure about how to approach such a difficulty. Did you get to a point where you'd solved this or not?