Home > weekly report > weekly report 16 Apr 2010

weekly report 16 Apr 2010

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
  1. Paddy
    April 16th, 2010 at 17:17 | #1

    OK – looks like a fair summary. The plan for next week is solid.

    I will try to always write a short response to show i’ve read this!!!



  1. No trackbacks yet.