This is unfortunately the case when using mother nature, she can be fickle. Mitchell had linked the line direction to wind direction and the type (font) size to the wind speed. During testing, the wind was consistently from the south west and at a low speed (4-5 km/h) However, during the hour or so between testing and the presentation the wind had swung around to the east and risen to about 17 km/h. This placed to bulk of the type off the screen and the partial letter seen was considered to be a glitch. To be expected in the pressure of setting up.

The attached image is to show that the system is working. 

As the image only updates every 10 minutes I have not had it running for long, but as you can see the wind is mostly from the south and the strength is about 10 km/h. How can I tell this, well guess work mostly for the speed and seeing as how the words are pointing straight down I can guess that the wind is mostly consistently south and developing a swing to the east.

The Tweets we are receiving are the latest top of the listing for tweets arising within 1 kilometre of the Ultimo area.

tweet_wind image Wind from south 10 km/h

I have also attached to file from processing to allow those with greater skill to modify this file as it would be cool if the type could move like the sentences in the Kinetic type example.

This would give the final result a more cohesive feel.import-processing 

I have saved to processing file as a word document. This was done with cutting and pasting for the processing file. I hope that this works.

Good Luck 

Gary

Thanks for the lessons Mitchell, I will attempt to get the lines waving in the breeze. I will send you the file to play with as well just in case I struggle a bit with it.

Gary

The FM radio microphone has been completed and the lights say it is working, Jason has a plan for this little beauty. (images to follow)

On the processing side of the coin, I am continuing with the baby steps. I have developed my ideas for the fire cube and the waving type and am now looking at a sparkline type of indicator to help with indication of the weather and its effects.

beth has completed her assignment of getting the birds to flock in the direction of the wind and is now looking at making the smoke act as a pollution or pollen indicator.

I will try to bring data into my pages and get the 3 processing files to be one.

I have also been able to bring in the make movie files and have produced Quicktime movies of my processing files. (not attached as you cannot upload .mov files)

The review is at 2.00pm and up till then I will be attempting to bring my work to a wholeness that is complementary to the main work.

Fingers crossed

Gary

rain.. matrix style

running values across screen.. could be used to track local vs sydney temperature?

live motion through web cam

these codes look relatively easy to modify to read our data.. unlike the boids (sorry..)

code for sound data looks very complex.. nice example by flight404… http://www.flight404.com/_videos/magnetosphere/index.html

Beth

i. Bridge Sensors – there are three light/humidity/temp sensors in the vicinity of the bridge.  One is on the door frame of the opening from the DAB onto the bridge, one is in the corridor on the angled glass wall (at 45 degrees between the interactivation lab and the bridge) and the third unit is on the bridge itself. The data is being logged to a file on the public (m\mda masterclass\sensors\data\log2.csv) as well as the pachube service (1187 is the doorframe, 1182 is the glass wall and 1186 is the bridge).

These sensors are logging somewhat consistently, the only thing to watch is battery life.  There are rechargable batteries charging in the interactivation lab and a ladder which is needed to reach two of the units.  Please be careful using the ladder, and replace any batteries in the charger when used.

ii. Webcam – there are two webcams capturing image data from the street and from the cafe courtyard.  The street-facing webcam is located in the interactivation lab near the stairwell and is accessible over the network. The webcam is capturing 1 frame per second, so will be a rich source of traffic data.

The cafe courtyard webcam is on the screen of the computer facing the courtyard, and is logging frames to a directory on that machine (Documents/Processing/watching_the_street_ls/frames/) which will need to be copied manually to a drive on the public.  The cafe cam is capturing at 1 frame per minute, so should be appropriate for the cafe traffic, but this may increase to match the other webcam.

iii. Phidgets – There are a suite of phidgets recording data from the interactivation lab facing the courtyard, including light/temperature/magnetism/proximity and are being logged in a processing sketch on the machine facing the courtyard.  This data will need to be grabbed from the print window of the sketch and pasted into a text file for munging.  The data is being collected at 30 second intervals.

iv. Bluetooth – The courtyard and street-facing interactivation lab computers are continually logging bluetooth data and saving these files as .csv locally.  The log files are located in the same directory as the sketches, and will need to be saved to the public drive for access.

v. Weather station -  wind speed and rainfall are being logged by the weather station, but not uploaded or saved anywhere unfortunately.  The weather station is an analogue method of getting at this data, we may need to organise for some pencils and paper – but a very useful source of info nonetheless.

vi. We now also have sound!  There is a microphone logging sound levels from the stairwell outside the interactivation lab (facing harris st), in a processing sketch which is logging the data locally.  This info will be made available tomorrow so should be interesting to observe along with all the other info.  The audio levels are being logged every 15 seconds so we should see some more finegrained patterns emerging.  These levels will need to be copied from the output window of a processing sketch in the interactivation lab (facing the courtyard) and saved somewhere on the public to be of use to others.

That’s it!  We *may* be able to get some kind of gps system happening as well, but not by tomorrow so we’ll have a look at that before the exhibition and see if it yields anything interesting or useful.

- jm

Hoping to get some direction from you. These is the idea;

- to show relationship between DA applications to the Australian Stock Exchange.

1. Red and grey colour boxes that popping in represent DA that being approved on that date. The date should pop up on top of the boxes, same time as its popping up. Currently, its popping up at same place, overlapping each others. Both of these data is not related to each other, as the way it should be. How to write the script as to make it relating to each other.

Next level, we wanted to get some text regarding type of project ( such as renovation, conversion of commercial to residential etcs ) for each of that projects.

Thanks

We processed the images in a three step process.

1. Get live feed

2. Apply Threshold

3. Detect Blobs using script of processing website

4. Finetune the graphics to produce outlines of movement

Some snapshots over time indicating traffic / people flow