Archive

Archive for the ‘weekly report’ Category

Weekly update 8th June 2010

June 8th, 2010 No comments

In my last update, I identified the following tasks:

  • 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

other tasks

  • Implement vector clock code in the simulator, based on proximity, and work towards a location based one.
  • Read Knox’s thesis.
  • 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?)

Since then, if I am honest, I haven’t achieved much, partly due to my being useless at time management, and due to various commitments that required more time than I thought, and in hindsight I should have avoided (Demonstrating, ODCSSS, Computer Science Summer School, visiting family, buying a car) my plans have gone out of the window. I am also obliged to give up more time this week (CSSS, Tues 2 hours, Wed 5 hours, Thurs and Friday 8 hours each!) which I would rather have avoided.

I really want to get up to speed, and I am very conscious of the little amount of time I have left, so after my commitments this week, I will dedicate all of my time to my PhD work, and will endeavour to get my work back on track. But in order to do so, I need to have a clear path to completion, so I propose the following tasks:

Overview Tasks

  • Meet with Paddy to discuss a plan for completion
  • Investigate options for continued funding

Project specific tasks

  • Plan short experiment to collect ground truth location data
  • Prepare to show Paddy the finished vector clock implementation (workthrough), picking out interesting parts and identifying next steps
  • Summarise findings from vector clock implementation (workthrough)

Other tasks

  • Implement vector clocks in simulator, based on location
  • Read Knox’s thesis.
  • Read Barabasi’s book.
  • 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 (any suggestions would be appreciated!)

And in context, my conflicting obligations and plans etc. are as follows

  • Computer Science Summer School – w/e 13 June  (23 hours!)
  • ODCSSS Student  – until w/c 9 August
  • Planned trip (home 1week,  Germany 1 week) – Fri, 30 July – Sun, 15 August
Categories: weekly report

Weekly Update 30 Apr 2010

April 30th, 2010 No comments

Last week I set out the following plan for the week:

For the next week I plan to nail down how I can implement vector clocks for location and proximity, also think about what metrics we can derive from this. At the same time I plan to read through Knox’s thesis, and read Simons paper, and try to formalise my ideas about location.

Since then, I have read Simon’s paper, which provided a nice discussion about what needs to be thought about when we deal with location. I have made progress with the simulator software. I also wrote code to process all of the data I collected from N95s, so that each reading in the database has a location associated with it. The simulator will now be able to use this to drive the location aspects of nodes.

I had some thoughts about planning a chapter about deriving location from sensor readings (e.g. WiFi position, GPS Readings, Cell Tower Positioning and Triangulation) – e.g. how can we measure the accuracy of our posistion calculations, how accurate does a the position need to be, and how should we represent location.

I also started to read up on Graph Theory, but starting with Barabasi’s book ‘Linked’ , which gives a really interesting overview of Graph Theory and how to measure aspects of complex networks. This made me realise that I will also need a chapter about this subject, and so I plan to write a review of Graph Theory based roughly based on this book.

I have also been giving more thought regarding Vector Clocks and how to use them, but I have not implemented anything yet.

My plan for next week is:

  • to 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.
  • Read Knox’s thesis.
  • 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

weekly report 16 Apr 2010

April 16th, 2010 1 comment

This is the first weekly report to Paddy.

Since our meeting on Wednesday, there is not much for me to report, however as this is the first report, I will summarise what the short term plan for the next few weeks is.

At our meeting we discussed my ideas about where my PhD will focus, which I documented here, the actions I identified from the meeting are as follows:

  • Refine contributions section – (this will come with time as the project progresses)
  • Refine and tighten up the hypothesis section – remove negative items
  • Beware of going down unneccasary rabbit holes – don’t get distracted
  • Nail down what each main part is
    • using  vector clocks to derive metrics,
    • predicting mobility and proximity,
    • exploring the value of distance to other nodes (e.g. is 3 hops enough?)
    • how to bring it all together
  • Dig out reviews on DTN’s- especially about patterns and finding important nodes
  • Make some enquiries about datasets
    • Email: GW, Barry Smith, Aaron, Knox
    • Intel Placelab
  • Think about the meaning of location (Read Simons paper: Where’s Waldo)
  • Start with prototype to explore the following:
    • Complexity of data
    • What data can we store in vector clocks
  • Things to think about:
    • Using Barabasi’s prediction approach to generate traces
    • Mechanisms for discovering best next hop
      • individuals only calculate their own ability to deliver
      • individuals ask other nodes if they can deliver
      • combination of different approaches depending on who we are trying to contact (e.g. friend, vs friend of a friend, vs everyone else)
    • Consider complexity analysis

Since the meeting I have started to reconsider the hypothesis questions as follows:

  1. Human mobility patterns are predictable
  2. Human proximity patterns are predictable
  3. Knowledge of proximity and location makes opportunistic routing more efficient than proximity alone.
  4. There are low complexity algorithms based on vector clocks that can be used for routing
  5. Any given node will only need to communicate with with other nodes that they know of

For the next week I plan to nail down how I can implement vector clocks for location and proximity, also think about what metrics we can derive from this. At the same time I plan to read through Knox’s thesis, and read Simons paper, and try to formalise my ideas about location.

Categories: weekly report