Thursday, November 10, 2011

Exp_2_Research_Assignment

 sandbox 2_How to make time travel with xml reading 




Flow graph:





500 Words:


In this research task, the tutorial is addressing on how to make a time travel effect by taking xml data from its file. What nodes will be needed and what parameter needs to be changed are clearly explained in this tutorial step by step. Xml document reading is quite significant for the experiment 2, analytics engine. Especially for after getting the data from xml document, implement them into the environment. Therefore this tutorial is very helpful for this point. From the flow graph in the tutorial, it tells people how to get the value from the xml document, how to show the data on the screen and implement the data into the environment such as a certain object to do some typical responses. There has two key points: one is the customise model, another key point is the about the analytics engine how to analysis the data. From the experiment one, we had learned how to make the model suits the real time environment, implement the theme into the model and create customise flow graph to help the model. So, the tutorial is designed for the second key. After people understanding this tutorial, they could use the flow graph as a reference or template, to develop another advanced effect or movement to make the analytics engine work properly. This tutorial is based on another tutorial from Week 6 task, experiment two. After understanding how to get a flow graph to read data from pachube feed via xml from Rosamond’s tutorial, using the data as a trigger or value to assign on the object and make it to do some typical responses to stand for and synchronise the variation of the data from pachube feed. The viewer therefore can understand what the analytics engine is and what they do. 

In the flow graph, the proximity trigger node is actually a trigger, and there has two parts left, the xml document reading and the object movement. The xml:OpenDocument node is linking to Xml:GetRoot, it opens the xml file when the player get close enough to the trigger. The Xml:GetRoot is pointing out the root form xml document, Xml:GetChild nodes are getting the child from the root, they link to Xml:GetChildAt node, and then the Xml:GetValue node is getting the value, the last one, HUD:ShowHUDMessege will show the value on the screen. The second part is the changing of time and the object movements. Using the ProximityTrigger node, we can get the trigger from the node, it is linking to the Math:ToBoolean and the Movement:Rotation (it could be other movement). So that when the local player get close to or far away from the trigger, those assigned object will do some movements as response. The Time:TimeOfDay nodes are linking to the Xml:GetValue and the ProximityTrigger, they can modify the time speed to achieve the time travel effect in game.

Friday, November 4, 2011

Exp_2_Week_4_The_Breif_of_Exp_2

The idea for the Analytics Engine – Exp 2 is to expand on the chosen pachube feed even further. The live feed is capturing data from a sensor and displays it in graphical way. The idea will be developed through the use of flow graphs, models and the environments in Crysis. All of those data will be displayed in different ways, hope this will help the viewer to have a better understanding of the given data.
Outline



The model I am going to create is a laboratory with different equipment, according to the chosen pachube feed data, those equipment will respond the viewer through graphical way such as glow, increase the equipment density or increase the length, and read the data from xml which provided by the chosen pachube feed. There have three types of data in the chosen pachube feed: Temperature, Light, and Time. The laboratory therefore will be given three equipments, they are spinning time sensor rings, light sensor sticks and triangular bars to represent those different data, meanwhile, at the time the model react some movement to the viewer, they also would show the data from the live feed. In this pachube feed, the light actually is the key, people are sensitive to light, and more importantly, with some more addition effect, the light would make the installation distinct and significant. This model therefore will have some lighting effects through flow graphs to demonstrate several variations and movements when analysis the data from updated pachube feed.
DatasNOverall

The first data is the temperature, in the laboratory, the triangular bars will analysis the variation in the data and then convert the data into bar graph. The graph will increase its length with a certain speed to a certain height, depending on the numerical data, display the data and start glowing.
TemperatureBars

The second data is the light data. They will be gathered by the light sensor sticks and displayed as integer data when these sticks start glowing through HUD massage. The sensor sticks will also be lined up on the ground to show the dimension of the data with different levels of glowing and the length of the glowing sticks (if the data is not great enough, some of the light sensor sticks will not glow until the data gets a certain level). 
StickSensors(W/O data)

The last equipment will be measuring the time. Because of the time is dynamic, therefore the equipment it is assigned is also dynamic. That will be the spinning time sensor rings. They are spinning around within an area, displaying the data with the HUD massage, and also increase the density when the data gets certain level. When the data change, these rings will have some flash effect as response. 
SpinningRings(W/O data)



Chosen Pachube Feed
https://pachube.com/feeds/35441




Three 30 second(max) video clips demostrating flowgraph analysis


Draft Video_3
Reading updated Pachube feed
Analysis data
Time data




Flowgraphs_Time_data_Reading_and_Change_Time:

Overall
Part_1

Part_2


Draft Video_2
Reading updated Pachube feed
Analysis data
 Light data
 


Duplicate_This_for_Each_Stick_Sensor_Then_Change_the_Value_order



Draft Video_1
Reading XML document
Temperature Analysis


Flowgraphs_Temperature_xml_Reading:

Friday, October 28, 2011

Exp_2_Week_3_Infographics

App Store Wars infographic
There has a comparison between the Apple store, Android Market, Blackberry App World, and the Nokia, Palm and Windows Phone 7 application directories. The interesting thing is they are using the mobile phone icon to display the smartphone distribution by operating system, easy to comprehend.
An Ode to Horror Cult Classics(1933-2006)
The Halloween Horror Films infographic has a distribution of all kinds of horror movie genres and display them within an eye ball to make it suits its theme.
What is a Stock?
This infographic from Mint.com explains what stock ownership is.

Sunday, October 16, 2011

Exp_2_Week_2_Task_and_Independent_Study

 
Xml_Recorded_Video 


This video shows the flowgraph in action from week 2 task for the experiment 2. From the data and the images it can be seen how the flowgraph capture the distance between the local player and the entity (in this case is the house model) by pressing a button. It stores the data into an xml document, open it, save it, update it.

Xml_file_data
Xml_Flowgraph_Overall
Xml_Flowgraph_3
Xml_Flowgraph_2
Xml_Flowgraph_1

Analytics_Engine

The techniques this blog displays so far could be integrated into the chosen environment and flow graph system. On one of the videos below, the flow graph has been assigned in a series specified entities, the data is displaying on the screen from an xml document when the local player press a button. This could be applied to display the data updating from the live feed.  The specified entity will be assigned a series of flow graphs to do some movements to display the variation of the data.