Crowd Sim :D

.gitignore

@@ -0,0 +1 @@
+node_modules

README.md

@@ -1,40 +1,46 @@
 # BioCrowds
 Biocrowds is a crowd simulation algorithm based on the formation of veination patterns on leaves. It prevents agents from colliding with each other on their way to their goal points using a notion of "personal space". Personal space is modelled with a space colonization algorithm. Markers (just points) are scattered throughout the simulation space, on the ground. At each simulation frame, each marker becomes "owned" by the agent closest to it (with some max distance representing an agent's perception). Agent velocity at the next frame is then computed using a sum of the displacement vectors to each of its markers. Because a marker can only be owned by one agent at a time, this technique prevents agents from colliding.
 
-## Agent Representation (15 pts)
-Create an agent class to hold properties used for simulating and drawing the agent. Some properties you may want to consider include the following:
-- Position
-- Velocity
-- Goal
-- Orientation
-- Size
-- Markers
-
-## Grid/Marker Representation (25 pts)
-Markers should be scattered randomly across a uniform grid. You should implement an efficient way of determining the nearest agent to a given marker. Based on an marker's location, you should be able to get the nearest four grid cells and loop through all the agents contained in them.
-
-## Setup (10 pts)
-- Create a scene (standard, with camera controls) and scatter markers across the entire ground plane
-- Spawn agents with specified goal points
-
-## Per Frame (35 pts)
-- Assign markers to the nearest agent within a given radius. Be sure that a marker is only assigned to a single, unique agent.
-- Compute velocity for each agent
-- New velocity is determined by summing contributions from all the markers the agent "owns". Each marker contribution consists of the displacement vector between the agent and the marker multiplied by some (non-negative) weight. The weighting is based on
-	- Similarity between the displacement vector and the vector to agent's goal (the more similar, the higher the weight. A dot product works well)
-	- Distance from agent (the further away, the less contribution)
-Each contribution is normalized by the total marker contributions (divide each contribution by sum total)
-  - Clamp velocity to some maximum (you probably want to choose a max speed such that you agent will never move further than its marker radius)
-- Move agents by their newly computed velocity * time step
-- Draw a ground plane and cylinders to represent the agents.
-- For a more thorough explanation, see [HERE](http://www.inf.pucrs.br/~smusse/Animacao/2016/CrowdTalk.pdf) and [HERE](http://www.sciencedirect.com/science/article/pii/S0097849311001713) and [HERE](https://books.google.com/books?id=3Adh_2ZNGLAC&pg=PA146&lpg=PA146&dq=biocrowds%20algorithm&source=bl&ots=zsM86iYTot&sig=KQJU7_NagMK4rbpY0oYc3bwCh9o&hl=en&sa=X&ved=0ahUKEwik9JfPnubSAhXIxVQKHUybCxUQ6AEILzAE#v=onepage&q=biocrowds%20algorithm&f=false) and [HERE](https://cis700-procedural-graphics.github.io/files/biocrowds_3_21_17.pdf)
+## Agent Representation 
+My agents hold their current position on the grid, their goal position, thier color, and a list of the markers they own.
+
+## Grid/Marker Representation 
+I used stratified sampling to find 10 samples for every cell in my 20 x 20 grid to decide the locations of markers. Here is a picture of my board with all the markers represented by a pink dot:
+
+![](./markers01.PNG)
+
+When I added in obstacles to the simulation, I stopped the agents from entering those obstacles and passing through them by not placing markers at those obstacles positions. Here is a picture of the markers when an obstacle was on the board:
+
+![](./markersNoOb.PNG)
+
+In order to assign markers to the agents I used the following process: I went through each of the markers on my grid and for each of them, I had a variable closestDist, which was set to the radius I wanted to search for markers around the agent, and a variable closestAgent, which was set to undefined. I went through each of the agents, reassigning closestDist and closestAgent if a closer agent than the search radius distance away. If closestAgent was defined, then that agent was given the marker to "own". This process ensured each marker would only be assigned to one unique agent.
+
+## Per Frame 
+Every frame I updated which markers each agent owned, calculated those markers' weights based on the cosine of the angle between the vector from the agent to the marker and the vector from the agent to its goal, and combined them to get a vector of displacement for this frame, which I multiplied by the time step (based on speed) and added to the agent's position. In order to keep the agents from colliding with each other, I clamped the final displacement on this frame so that it would not exceed the agent's search radius. 
 
 ## Two scenarios
-- Create two different scenarios (initial agent placement, goals) to show off the collision avoidance. Try to pick something interesting! Classics include two opposing lines of agents with goals on opposite sides, or agents that spawn in a circle, which each agent's goal directly across.
-- Provide some way to switch between scenarios
+I provided two simulations. In the first one, 5 agents are lined up on each of the top, bottom, left , and right sides of the board. Each of the agents' goals are to get to the exact opposite side of the board. Thus, some difficulty and confusion occurs in the middle of the board. Here are some images of the simulation:
+
+![](./cross01.PNG) 
+![](./cross02.PNG)
+![](./cross03.PNG)
+
+In the second simulation, 10 agents are lined up on the top and bottom sides of the board and their goals are again to get to the opposite side. In this simulation, two obstacles with a gao between them provide a simulated doorway, so the agents must wait and form streams to get across. Here are some images of this simulation:
+
+![](./doorway01.PNG)
+![](./doorway02.PNG)
+
+##Interactivity
+I provided a speed parameter, which increases the time step, making the agents move more quickly. 
+
+I also provided parameters to add an obstacle on the crossing simulation and move that obstacle on the board, as well as parameters to move the doorway on the board and increase or decrease the gap of the doorway.
+
+Here are images of the crossing simulation with an obstacle:
+
+![](./crossOb02.PNG)
+![](./crossObDiffPlace.PNG)
+
+And an image of the doorway simulation with a smaller gap:
 
-## Deploy your code! (5 pts)
-- Your demo should run on your gh-pages branch
+![](./doorwaySmallGap.PNG)
 
-## Extra credit
-- Add obstacles to your scene, such that agents avoid them

index.html

@@ -0,0 +1,19 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <title>Project 6: Implicit Surfaces</title>
+    <style>
+      html, body {
+        margin: 0;
+        overflow: hidden;
+      }
+      canvas {
+        width: 100%;
+        height: 100%;
+      }
+    </style>
+  </head>
+  <body>
+    <script src="build/bundle.js"></script>
+  </body>
+</html>