### Archive

Archive for May, 2010

## Weekly report for week ending 16th May 2010

Last week I set the following tasks:

• Continue/Finish worked example of interaction network using vector clocks
• Plan short experiment as above (or at least think about whether it would be useful)
• Get a better understanding of Graph Theory by finishing Barabasi’s book.
• Make some enquiries about datasets

and

• Implement vector clock code in the simulator, based on proximity, and work towards a location based one.
• Generate a rough outline of chapters for my thesis, and identify the main areas for the background section
• Write down ideas about how to define locations (draft)
• Dig out reviews on DTN’s- especially about patterns and finding important nodes
• Find out about funding from September 2010, (IRCSET, CSI, Lero, more?)

I have got a good way through doing a worked example; I have created 6 characters (based on real people) and have given them home, work, and leisure locations. I have created a notation for recording movement events, and have generated skeleton location graphs for all individuals. I have started to generate the characters daily movements.

I have given a little more thought about planning the experiment suggested in my previous post, and have identified some participants (the same ones I based the workthrough on), and I believe collecting this information will be useful to get a good idea for people’s real movements.

The following week is a busy one for me, as I have to demonstrate (Monday 3 hours), attend and mark presentations for the HDIP class on Wednesday (all day) and on Friday I am visiting family in the UK (volcanoes permitting). After this I have very few demonstrating responsibilities. So the following is my plan for then next two weeks.

• Finish worked example of interaction network using vector clocks
• Plan short experiment to collect ground truth location data
• Finishing Barabasi’s book.
• Prepare to show Paddy the finished worked example, picking out interesting parts and identifying next steps

• Implement vector clock code in the simulator, based on proximity, and work towards a location based one.
• Generate a rough outline of chapters for my thesis, and identify the main areas for the background section
• Write down ideas about how to define locations (draft)
• Dig out reviews on DTN’s- especially about patterns and finding important nodes
• Find out about funding from September 2010, (IRCSET, CSI, Lero, more?)
Categories: Uncategorized

## Weekly update for w/e 9th May 2010

In last week’s update I said that I intended to do the following:

• get a better understanding of Graph Theory by finishing the book.
• Implement vector clock code in the simulator, based on proximity, and work towards a location based one.
• Formalise my thoughts on how to use Vector Clocks of proximity and location, and what metrics can be derived from them
• Generate a rough outline of chapters for my thesis, and identify the main areas for the background section

Since then, I had a quick chat with Paddy, and we discussed simplifying what I should work on,  and came up with a plan to create an example work through of interactions and locations.

Before that, I had started a rough plan of network of interactions within a ficticous network, I also continued to work on the simulator software, and had generated latitude longitude pairs for every reading in the database (479,148 in total).

Since our meeting, I concentrated on working up an example workthough, and for this week I plan to continue this.

I also thought about a small and easy experiment to test the validity of what I was generating; ask some volunteers to:

1. Write down their movement for the last week, and identify the locations they considered to be most common.
2. Write down their predicted locations for the next week.
3. Ask them to keep a record of their actual locations over the next week.

This could conceivably be done very easily in written notebook form, or slightly more challenging – as an online system. This will allow us to get a better idea of what peoples real movements are, and see if it looks like the workthrough we have generated.

My plans for this week are as follows:

• Continue/Finish worked example of interaction network using vector clocks
• Plan short experiment as above (or at least think about whether it would be useful)
• Get a better understanding of Graph Theory by finishing Barabasi’s book.
• Make some enquiries about datasets

(note – Laura is coming home this week)

Other tasks to keep in mind:

• Implement vector clock code in the simulator, based on proximity, and work towards a location based one.
• Generate a rough outline of chapters for my thesis, and identify the main areas for the background section
• Write down ideas about how to define locations (draft)
• Dig out reviews on DTN’s- especially about patterns and finding important nodes
• Find out about funding from September 2010, (IRCSET, CSI, Lero, more?)
Categories: Uncategorized

## Quick meeting with Paddy 6th May 2010

Paddy wants to see something tangible by next week’s update – i.e. a worked example of how vector clocks will work in terms of location.

Also emphasised that I should not get sidetracked! (of course!)

Suggested storing temporal  information (parallel vector clocks?) – e.g. a from to, so that we can say things like does this time overlap this one, is it contained withing etc. etc.

Also thought about how to define location – the bounding of the location  gives an experimentation thing – change the grid size – whats the computation impact of the size of the grid – and what the relevance e.g. too big and it makes realistic.

Construct vector stamps – 5 separate path across these locations, two or three allow drop messages – run through and pick various vector clocks at various times, and show them. Then start generalising them.

From this we can draw general things about e.g.: decisions made, what information is stored, what we put in vector clocks, what operators we need.

Then run a simulation and see if generalisation works. Then we can see if some things fall down, and come back and change things.

Should stick with ideas about location, not proximity yet.

Using this it is then possible to write this concisely.

Actions:

• Generate a worked example/scenario
• show examples of vector clocks at times
• show the movements over time
• Don’t get sidetracked!
Categories: