Sugarcane

there are fancy formal languages for this sort of thing, mainly from Planning, e.g.\nTLA (temporal language of action)\nsituation calculus\nevent calculus\n\nthese are modal logics where truth is indexed by time\n<<continue "}}}>>\nthey usually don't give you a "frame rule" for free, so at each time step you have to update everything that doesn't change:\n\nA[t] -> A[t+1]\n\nLinear Logic solves this problem\n(exposit)\n<<continue "}}}">>\nBut PROBLEMS:\n\nit doesn't give us a natural way for encoding actions, loci of control\n\n<pre>do/murder \n: anger C C' * anger C C' * anger C C' * anger C C' *\n at C L * at C' L * has C weapon\n -o {at C L * !dead C' * \n !murdered C C' * has C weapon}.\ndo/thinkVengefully\n: at C L * at Killer L' * \n philia C Dead * murdered Killer Dead\n -o {at C L * at Killer L' * philia C Dead *\n anger C Killer * anger C Killer}.</pre>\n\n*when* can an agent (human or programmatic) interrupt execution? answer in my thesis proposal: <<replace "phases.">>(the ability to partition a logic program into named rulesets, between which control is transfered at <i>quiescence</i>)<<endreplace>>

I. [[The Interactive Simulation]] <<if $part1>>[✓]<<endif>>\nII. [[Simulations in Linear Logic Programming]]<<if $part2>>[✓]<<endif>>\nIII. [[~Interactivity~]]<<if $part3>>[✓]<<endif>>\nIV. [[Pie in the Sky]]<<if $part4>>[✓]<<endif>>\nV. <a href="https://docs.google.com/document/d/1GoROPk65NFGuXF5HwEPyzBmDieVgXrDSnzWc-6g1UWU/edit?usp=sharing">Discussion</a>

a grammatical model of [X] yields a process for generating [X] \n\ne.g. Vladimir Propp:\ngrammatical model of stories\n-> yields a model of the process of storytelling\n\n<img src="protopropp.png">\n\n<<continue "}}}">>\n\n“is [X] a story?”\n→\n“create a story, [X]”\n\njust different modes of the same <b>logic program</b>,\n\n?- story(X)\n\n<<continue "}}}">>\n\nstateless (e.g. markov models)\n--->\nmore complex generation structures \n\nBosser et. al.: Linear Logic for Nonlinear Storytelling\n“proofs as stories”\n\n<img src="linear-logic-storytelling-papertop.png">\n\n<<set $part1 = true>>Back to [[Outline]]

<<replace "proofs">>linear logic proofs<<endreplace>> as stories<<continue "}}}>>\n\nsimulated environments can be modeled as linear logic contexts.\n\neat-poison : ∀C.alive(C) * apple -o {dead(C)}.\n\nΔ = { apple, alive(princess), alive(witch) }\n\nΔ |- (alive(princess)*dead(witch)) (+) (alive(witch)*dead(princess))\n\n<<continue "}}}">>\n\nwe think about changes to the environment in terms of resource <b>consumption</b> & <b>production</b>.\n\n<<continue "}}}">>\n<pre>do/eat\n: alive(C) * has(C, apple)\n -o {dead(C)}.\n\ndo/give\n: at(C, L) * at(C', L) *\n has(C, apple)\n -o {at(C, L) * at(C', L) * has(C', apple)}.</pre>\n<<continue "}}}">>\n\nLINEAR LOGIC PROGRAMMING as implemented in Celf:\nnondeterminism yields generativity/simulation\nconstructivity yields proofs as <<replace "stories">>artifacts for <<replace "analysis">>analysis of resource dependency structure<<endreplace>><<endreplace>>\n\n<<continue "}}}>>\n<img width=800 src="celf2graph.png">\n\n<<set $part2 = true>>Back to [[Outline]]

<<replace>>proofs as stories<<gains>>\nproof search as interaction<<gains>>\nlogic programs as interactive stories<<gains>>\nlogical frameworks as sketching tools\n\n<<continue "}}}">><<endreplace>>\n\nthe terms in which we advertize our language designs (and therefore invent them):\n\n<<replace>>rigidity<<becomes>>expressivity<<becomes>>immediacy<<endreplace>>, <<replace>>correctness<<becomes>>abstraction<<becomes>>playfulness<<endreplace>>, <<replace>>security<<becomes>>elegance<<becomes>>whimsy<<endreplace>>, <<replace>>safety<<becomes>>structure<<becomes>>tangibility<<endreplace>>, <<replace>>limitation<<becomes>>clarity<<becomes>>surprise<<endreplace>>\n\nBack to [[Outline]]\n<<set $part4 = true>><<endreplace>>

"The Interactive Simulation"\n\nrelated to Generative Media: a long tradition of algorithmically generated music, poetry, 2d art...\n<<continue "}}}">>\n<img src="great-art-bot.png">\n<<continue "}}}">>\nwhen we add interactivity, we get games:\n\n<img src="great-artist.png">\n<<continue "}}}">>\n<img height=256 src="sim-ant.png"> <img height=256 src="simcity.png"> <img height=256 src="the-sims.jpg">\n<<continue "}}}">>\n<img height=256 src="versu.png">\n<img height=256 src="minecraft.jpg"> <img height=256 src="868-hack.jpg">\n<<continue "}}}">>\nin general:\n- there is a system of rules governing the environment\n- human can <<cyclinglink "control part of" "poke at" "explore">> the environment & create interesting, surprising behavior\n\nWarren Spector, as summarized on Gamasutra:\n<blockquote>\nCreate global rules versus specific, instanced behavior of objects and characters; build interlocking systems that are predictable and consistent (some objects are flammable, some guards are light-sensitive, the player has torches) but not pre-determined. Have a variety of object properties with plausible or simulated effects ("let water be water") that players can learn and engage with.\n</blockquote>\n\nGenerative Narrative<<continue "}}}">>\n<<display "generative narrative">>

<<silently>>\n<<set $part1 = false>>\n<<set $part2 = false>>\n<<set $part3 = false>>\n<<set $part4 = false>>\n<<endsilently>><h3><<replace "Languages for Actions in Simulated Worlds">>Or: [[what I know about doing game design with logic programs|Outline]]<<endreplace>></h3>\nChris Martens - CMU CS department\nOBT 2014\nhttp://www.cs.cmu.edu/~cmartens/obt2014/obt.html

version.extensions["cyclinglinkMacro"]={major:3,minor:1,revision:1};macros.cyclinglink={handler:function(a,b,c){var l=Wikifier.createInternalLink(a,null);\nl.className="internalLink cyclingLink";l.setAttribute("data-cycle",0);var v="";var end=false;\nif(c.length&&c[0][0]=="$"){v=c[0].slice(1);c.shift();}if(c[c.length-1]=="end"){end=true;\nc.pop();}var h=state.history[0].variables;for(var i=0;i<c.length;i++){var on=(i==Math.max(c.indexOf(h[v]),0));\nvar d=insertElement(null,"span",null,"cyclingLink"+((on)?"En":"Dis")+"abled");if(on){h[v]=c;\nl.setAttribute("data-cycle",i);}insertText(d,c[i]);l.appendChild(d);}l.onclick=function(){var t=this.childNodes;\nvar d="cyclingLink";var u=this.getAttribute("data-cycle")-0;var m=t.length;if(end&&u==m-2){var n=this.removeChild(t[u+1]);\nn.className=d+"End";this.parentNode.replaceChild(n,this);return;}t[u].classList.toggle(d+"Enabled");\nt[u].classList.toggle(d+"Disabled");u=(u+1)%m;if(v){h[v]=c[u];}t[u].classList.toggle(d+"Enabled");\nt[u].classList.toggle(d+"Disabled");this.setAttribute("data-cycle",u);};},init:function(){addStyle(".cyclingLinkDisabled { display:none; } ");\n}};macros.cyclinglink.init();

Languages for Actions in Simulated Worlds

<a href="http://www.cs.cmu.edu/~cmartens">Chris Martens</a>\n(<a href="http://www.twitter.com/chrisamaphone">@chrisamaphone</a>)

<<replace "interactive SIMULATIONS">>INTERACTIVE simulations<<endreplace>>\n\nmy hypothesis is: we need domain-specific "Action Languages"<<continue "}}}">>\n\n<<revision genspec>>generating random stories<<becomes>>specifying an *interactive* story<<endrevision>> <<revise genspec "vs.">>\n\n<<continue "}}}">>\n“interactive” =~ a human can interrupt and influence execution\n\nwe start with this program\n<pre>\ndo/eat : alive(C) * has(C, A) * poisonous(A) \n -o {dead(C)}.\n\ndo/give : at(C, L) * at(C', L) * has(C, A)\n -o {at(C, L) * at(C', L) * has(C', A)}.\n</pre>\nto introduce interactivity we need to know:\nwhat is the <<replace>>locus of action?<<becomes>>locus of action?\n\n"which one am i?" "what is the control interface?"<<endreplace>>\n\n<<continue "}}}">>\n\nidea: parameterize the program by locus of control. index every rule with a "do" predicate specifying the acting agent:\n\n<pre>\ndo/eat : do(C, eat (O)) * \n alive(C) * has(C, O) * poisonous(O)\n -o {dead(C)}.\n\ndo/give : do(C, give(C',O)) * \n at(C, L) * at(C', L) * has(C, O)\n -o {at(C, L) * at(C', L) * has(C', O)}.</pre>\n<<continue "}}}">>\n<pre>do(C, Action)</pre> is introduced in a <<replace>>phase<<becomes>>phase (idea from my thesis proposal for transfering control between subprograms)<<endreplace>> corresponding to C's "turn", which can be designated as an opportunity for user input\n<<continue "}}}">>\n<pre>Action</pre>ranges over the set of available actions, i.e. the control interface!\n\nQ: can we automatically derive/extract the constructors for A in terms of the rules available in the bird's-eye-view simulation?\n<<continue "}}}">>\nACTION LANGUAGE example from IF:\n\n<<cyclinglink "VERB" "eat" "take" "examine" "push" "stand on">> <<cyclinglink "NOUN" "apple" "flask" "flower" "crate" "no tea" "weasel">>\n\nthe way we interpret actions in a simulation environment is A LOT LIKE interpreting PL terms in a program environment.\n\nQ: how do we specify these languages in a way that we can reason about them (the way we're used to reasoning about formal languages)?\n\n<<set $part3 = true>>Back to [[Outline]]

a {font-size:100%!important;}\n\n#passages{font-size:24px; font-family:'Open Sans';\nborder-left: 0px !important; margin:200px 0px 0px 200px !important;}\n\n#footer{display:none!important;}\n#toolbar{display:none!important;}\n#sidebar{display:none!important;}\n\n\n.revision-span-in {\n opacity: 0;\n}\n.revision-span {\n transition: 1s;\n -webkit-transition: 1s;\n}\n.revision-span-out {\n position:absolute;\n opacity: 0;\n}\n\n.transition-out {\n display:none;\n}\n