annotate winston-intro.txt @ 555:c8f7d10b1a2a

further clarification about skin partitioning per winston's request
author Robert McIntyre <rlm@mit.edu>
date Fri, 02 May 2014 14:27:29 -0400
parents 9ba3959b261b
children
rev   line source
rlm@302 1 Dear Professor Winston,
rlm@302 2
rlm@325 3 I've finished the first part of my project, building a
rlm@325 4 framework for virtual sensate creatures; I would like your
rlm@325 5 help evaluating what I've done so far, and deciding what to
rlm@325 6 do next.
rlm@302 7
rlm@325 8 For the work I've done so far, I compiled the results into
rlm@325 9 short articles that explain how I implemented each sense,
rlm@325 10 with videos that show each sense in action. Please look
rlm@325 11 through the articles, in particular the video showcase, and
rlm@325 12 tell me what you think.
rlm@302 13
rlm@310 14 Video Showcase : http://aurellem.org/cortex/org/cover.html
rlm@302 15
rlm@302 16 Introduction:
rlm@302 17 http://aurellem.org/cortex/html/intro.html
rlm@302 18 http://aurellem.org/cortex/html/sense.html
rlm@302 19
rlm@305 20 Physical Bodies : http://aurellem.org/cortex/html/body.html
rlm@305 21 Vision : http://aurellem.org/cortex/html/vision.html
rlm@305 22 Hearing : http://aurellem.org/cortex/html/hearing.html
rlm@305 23 Touch : http://aurellem.org/cortex/html/touch.html
rlm@325 24 Proprioception : http://aurellem.org/cortex/html/proprioception.html
rlm@305 25 Muscles : http://aurellem.org/cortex/html/movement.html
rlm@305 26 Full Demonstration : http://aurellem.org/cortex/html/integration.html
rlm@302 27
rlm@325 28 I think this work could be a fruitful foundation for a
rlm@325 29 Master's thesis, so in particular, I'd like critiques,
rlm@325 30 suggestions, and project ideas. For example, here are some
rlm@325 31 projects I think would be worthy, in increasing order of
rlm@325 32 complexity:
rlm@302 33
rlm@325 34 * Create a self-powered joint that can determine its
rlm@325 35 range of motion and joint type (hinge, cone,
rlm@325 36 point-to-point, etc.) by making exploratory muscle
rlm@325 37 movements and observing their effect.
rlm@302 38
rlm@325 39 * Develop an agent that writes and debugs low-level
rlm@325 40 motor control programs to achieve simple goals like
rlm@325 41 "look at the light" or "extend all of your
rlm@325 42 fingers". These simple "calisthenic" programs could
rlm@325 43 then be combined to form more elaborate procedures of
rlm@325 44 motion, which in turn could be the basic instinctive
rlm@325 45 reflexes in the "spinal cord" of some more advanced
rlm@325 46 creature. (like Sussman's HACKER program but in a
rlm@325 47 richer world)
rlm@302 48
rlm@305 49 * Program a group of creatures that cooperate with each
rlm@325 50 other. Because the creatures would be simulated, I
rlm@325 51 could investigate computationally complex rules of
rlm@325 52 behavior which still, from the group's point of view,
rlm@325 53 would happen in "real time". Interactions could be as
rlm@325 54 simple as cellular organisms communicating via
rlm@325 55 flashing lights, or as complex as humanoids completing
rlm@325 56 social tasks, etc.
rlm@302 57
rlm@325 58 * Simulated Imagination -- this would involve a creature
rlm@325 59 with an effector which creates an entire new
rlm@325 60 sub-simulation where the creature has direct control
rlm@325 61 over placement/creation of objects via simulated
rlm@325 62 telekinesis. The creature observes this sub-world
rlm@325 63 through it's normal senses and uses its observations
rlm@325 64 to make predictions about its top level world.
rlm@302 65
rlm@325 66 * Integrate the simulated world with Genesis, so that
rlm@325 67 Genesis could use the simulated world to answer
rlm@325 68 questions about a proposed physical scenario. For
rlm@325 69 example "You stack two blocks together, then hit the
rlm@325 70 bottom block with your hand. Does the top block
rlm@325 71 move?". This project is complicated and very large in
rlm@325 72 scope, but it could be narrowed to focus on a single
rlm@325 73 key aspect. For example, one key aspect of turning a
rlm@325 74 scenario into a simulation is knowing when you're
rlm@325 75 constructing "typical" or "atypical" examples of the
rlm@325 76 scenario. So, a narrower project might simply learn
rlm@325 77 about the edge cases of different scenarios (e.g. "A
rlm@325 78 block stacked on top of another block is usually
rlm@325 79 stable, provided the bottom block is large enough, and
rlm@325 80 is not moving, and is level, etc."). With this
rlm@325 81 knowledge, this kind of program could aid Genesis not
rlm@325 82 only in answering common-sense questions, but in
rlm@325 83 refining them: "A block is stacked on top of another
rlm@325 84 block. Is it stable?"; "Usually, but do you know if
rlm@325 85 the bottom block is slanted?", etc.
rlm@302 86
rlm@325 87 These are some ideas, but I think you can come up with
rlm@325 88 better ones. I can't wait to hear your critiques and
rlm@325 89 suggestions.
rlm@302 90
rlm@325 91 Finally, regarding next year at MIT, can I be considered for
rlm@325 92 the position of TA for 6.034 or 6.xxx? Also, do you want me
rlm@325 93 to return to MIT at the beginning of Fall or at the
rlm@325 94 beginning of Summer?
rlm@302 95
rlm@305 96 Sincerely,
rlm@302 97 --Robert McIntyre