Archive

Archive for the ‘What Paddy Says’ Category

Meeting with Paddy 20 Nov 2008

November 20th, 2008 No comments

Brief meeting with paddy.

We both like the idea of the City wide sensing idea using mobile devices. I mentioned that Jo K had thought the whole routing thing had been done, but paddy suggested that there is different view on similar problems that still yield interesting research topics.

We discussed simulations, and I mentioned the idea of using some datasets from Dublin traffic, and maybe even the wireless access point data from UCD campus to simulate social networks.

Paddy mentioned an IBM city simulator that has since disappeared, but will see if he can find out more about it (I will too).

Going forward, I should have a project to get my teeth into, that has some proper research outcomes, which should be a shot term project – 3 months.

I will arrange a meeting with myself, Paddy, Aaron and Simon for sometime very soon to come up with ideas.

I should probably come up with some suggestions to work with, for what the project could be. *thinking cap on*

Supervisor Meeting 09 Oct 2008

October 9th, 2008 No comments

Meeting with Paddy – pep talk to make me feel better – Paddy took 3 1/2 years to complete PhD, but changed his subject after tranfer report – and still managed to finish on time – even though I AM NOT brighter than him, I should be ok 😉

OK – lets get going with the city wide environmental sensing!

Need to think about:

What simulators are there? What infrastructure do we need to get it to work?

The underlying hard questions are:

1- Collecting Data

Offloading data in normal operation to fixed nodes or drop off points about the city-

issues

  • Storage
  • Sampling
  • Longevity
  • Power consumption
  • Date/Time  corroboration

The things on the body communicate, perhaps one is doing the monitoring, and others are managing the storage and dissemination of data across local nodes

Managed the local set as a community

2 – Global Control – Global Phenomena drives local operations

If we can assume nodes have a facility to geo-locate themselved, nodes can use or build a map of the area they are in. As the overall control system (?) detects issues or hotspots, it may increase the frequency of sampling in a particular area – this will require mechanisms to cope with this – considering multiple hot spots.

The idea being that some how nodes would be told to make more detections on certain areas – or even based on certain criteria – e.g if CO2 level > x increase freq.?

This then feeds back to the community – perhaps imagined as a  big async. query over the community.

3 – Cute part

When nodes pass through a hot-spot – what happens if they are not going past any other known drop off  node? Communicate with a node passing the other way through?  How to we manage this and what data – dead-reckoning? probability of passing another node?

Do the nodes always promiscuosly send data – or just sometimes?

Nodes Collaborate to communicate a response and are managed as a community or a swarm

We defined some next actions:

1 – Create  1 page vision document – deadline 3-4 days

To describe –

  • Community management
  • Fixed Nodes about an space
  • Group of devices about a person
  • Community of individuals with wearables
  • Granularity of resources (?)
  • How the overall community will work – what will be the infrastructure  – given our resources

2 – Slick the document up, and send it off to out peers in Harvard, to see if it will fit into their project

3 – When bored of writing – consider:

  • How do cities work? where do people go?
  • How do we simulate a city wide sensor network like this
  • Look at existing applications to simulate cities -flame.ac.uk – metropolis.tcd.ie – Steve Collins and Carol Sullivan
  • Look into cheap environmental sensors – bluetooth based – if we can get some which are cheap enough – we can get some and deploy over CASL/CSI/Campus?

4 – Overall Goal is to have a 6 month project – which will support my PhD, to make these new tecniques that we will develop – either as a simulation, real world deployment, or a mixture of both,

  • Will need to research the idea of decision theory
  • Community resource management

5 – Personal Task

  • to find out what research is going on in UCD and Clarity
  • Start with Barry Smith – ask who is doing what work – paddy wants to do wearbles – and wants to know who’s doing what research in the area

6 – Look for places to put position papers into

Finally – we need to keep some pressure on – and have some quick turn-arounds – and I should talk go talk to him if the ideas we discussed dont make sense afterwards.

Supervisor Meeting 02 Oct 2008

October 2nd, 2008 No comments

Met with Paddy and discussed what we need to be on with – we both seem to have been thinking about different things – I seem to have gone down a route of something to do with mobile phones – but it needs to be linked to what we are getting at. I said that I don’t really know what wearable computing really means – as I haven’t seen it in the flesh!

Really need to get into the idea of what infrastructure is needed to make wearable systems work – think of it more as network of wearable sensors.

What issues are there when we are thinking about transferring data amongst nodes – what if instead of being centrally managed – what if they could freely communicate with each other.

Discussed the idea of city wide environmental sensing – a mixture of fixed and mobile nodes which are tagging and recording data – offloading to nodes with big pipes – how does this work – and how do we implement it?

Also need to think about issues such as transient and persistant data – what is kept and what is shared and removed – what is private what is encrypted what is not?

Example application is
citywide environmental monitoring – fixed nodes talk each other and share data,
they also talk to mobile nodes to get data –application to monitor an area.

Nodes about the body can
communicate to other nodes on other bodies, handing off data – gossiping –
every piece of data has timestamp – and is tagged so that that it can be
synchronised at a later date.

Also –  talked about  developing some things that we say is good for
wearable computing – i.e. p2p vs managed nodes then compare previous wearable implementations
to our idea of whats best and see if they succeeded.

Hundreds of shimmers
downstairs in clarity to have a play with.

Speak to Julie doyle
about user study – work out what we are trying to get out and keep it in the back of my head.

Paddy suggested this was a turning point – are we
interested in hard computer science part?  Or more the HCI part?

Overall we really get down to the
basics –

What will be good
about P2P vs Central Node?

What is persistant
what is transient?

Matt Walsh – they have
the OS with low level access to data – what do we need to do to get something up and running?

Supervisor meeting 20 Aug 2008

August 20th, 2008 No comments

Part 1 – Wearables

Assumptions – Paddys Notes

Met with Paddy to talk about Wearable computing Assumptions.

Discussed the short-list that I had come up with: Assumptions about Wearable Computing

Paddy gave his thoughts about what I had come up with – and we came to the following main assumptions that we will look at and question their validity:

  • Communication bandwidth is an issue
    • What data do we really send? – Sensors/Video/Other
    • 3G is quick
  • Wearables are individual
    • Data is private, Infrastructure is community
  • We need to optimize for power
    • What if we don’t – usage patterns
  • Processing power is minimal
    • Not any more – processing power is good – PDA -iPhone etc.
  • One managing node
    • Emergence
    • pure p2p
    • individually addressable(ipv6?)

Tasks:

Matt:

Rethink the systems/paradigms/stuff that I have read/seen/tested and see what would happen if we took out these assumptions.

Suggest that these things are not really true anymore, and that they can be considered to be a myth.

Write up an internal paper/report (3 pages) that suggests this, and  covers the reasons why, and see what people think. – Debunking the Wearable Myth

Part 2 – Basadaeir

I suggested to Paddy that  we should do something with Basadaeir, and that it is one of the missing parts of the construct project, the profiled/static/persistent entity that contributes to the pervasive environment. He agreed that we should develop it, and was planning to require that all new people register with it.

He also suggested a case/research study for it, building collaboration not just through keywords, but also by matching presence of other people at the same time – e.g. when people are often in the same place at the same time, they may be connected somehow.

Tasks:

Matt:

Get the system robust and working – so that people can sign up and start using it –

  • CRUD for profiles
  • Efficient processing of data
  • API for external applications
  • Internalised third part applications (like fbook) – so that others can solicit more information about topics – e.g. research keywords.

Paddy:

Will tell people that this system will be available, and will expect that at some point Matt will have it working – no particular timescale.

Supervisor Meeting 17 July 2008

July 17th, 2008 No comments

Met with paddy this morning to talk about where to go from here.

I’ve been reading around Context, Privacy, Infrastructure, Management etc. in relation to wearable computing. There are a number of texts that mention it, but nothing (so far) that has dealt with it directly.

Paddy suggested reading and using the idea from http://infoblog.stanford.edu/ that you take the main assumptions about an area, list them out, then change one or two of them, and see what happens. (yet to read artical)

Also, paddy suggested to have a think about stream processing.

I should also look at the locations/conferences/groups that are doing these thing – i.e. find papers that are newer, and may not be highly cited.

Suggested conferences to look into:

MobHoc, MobiCom, Middleware, etc

Paddy also mentioned that reading can expand to fill all available time, so don’t let!