New Zealand story

I’m back in Dublin from my two-week expedition to New Zealand, the main reason for which was (ostensibly) to attend the IEEE Congress on Evolutionary Computation in Wellington. I’ve been back since Saturday actually, so by now the worst of the jet lag is behind me and it’s time to do a write-up of my doings and dealings down under. Besides NZ, I had the opportunity to pay a quick visit to Australia as well, since I had a stopover in Sydney that lasted from 6am to 6pm – plenty of time to catch a train from the airport to Circular Quay and snap some smug selfies with the famous opera house prominently in the background.

Having the long break between flights in Sydney proved a good decision, because even though the final hop from Sydney to Wellington was a relatively short one, by this point I had already flown seven and a half hours from Dublin to Dubai, followed by a two-hour stopover before the connecting flight to Sydney, which was just shy of fourteen hours. As a result of all this I wasn’t in much of a mood to do any more flying until I was well and truly rid of the stiffness of body and mind that comes from spending 20-plus hours seated inside a cramped aluminium tube in the sky, and a few hours of sightseeing on foot on what turned out to be a pleasantly warm and sunny day helped a great deal in achieving that. Another move I thanked myself for was having purchased access to the Qantas business lounge at Sydney airport, allowing me to enjoy such welcome luxuries as a comfy chair, a barista-made espresso and a nice shower before facing the world outside.

With the combined effect of the flight and transfer times and the 11-hour time difference, I arrived in Wellington near midnight on the evening of Sunday the 9th, having departed from Dublin on Friday evening. Monday the 10th was the first day of the conference, but it was all tutorials and workshops, none of which were particularly relevant to my own research, so I gave myself permission to sleep in and recharge before attempting anything resembling work. In fact the only “conference sessions” I attended on that first day were lunch and afternoon coffee; the rest of the time I spent at the venue I just wandered around Te Papa, exploring the national museum’s fascinating exhibitions on the nature, culture and history of New Zealand.

On the second day I began to feel the effects of jet lag for real, but I thought it was time to be a good soldier and check out some presentations. Although I don’t really do evolutionary computation myself, it has various applications that interest me professionally or personally, so it wasn’t too hard to find potentially interesting sessions in the programme. The highlight of the day for me was a session on games where there was, among others, a paper on evolving an AI to play a partially observable variant of Ms. Pac-Man; being a bit of a retrogaming geek, I found it quite heartwarming that this is an actual topic of serious academic research!

On the third day I forced myself to get up early enough to hear the plenary talk of Prof. Risto Miikkulainen, titled “Creative AI through Evolutionary Computation”. I was especially looking forward to this talk, and I was not disappointed: Prof. Miikkulainen built a good case for machine creativity as the next big step in AI and for the crucial role of evolutionary computation in it, with a variety of interesting supporting examples of successful applications. I am inclined to agree with the audience member who remarked that the conclusions of the talk were rather optimistic – it’s quite a leap from optimising website designs to optimising the governance of entire societies – but even so, a highly enjoyable presentation. Later that day there was a special session on music, art and creativity, which I also attended, but my enjoyment of it was hampered by my being in acute need of a nap at this point.

The fourth and final day of the conference I mostly spent preparing for my own presentation, which was in the special session on ethics and social implications of computational intelligence. This took place in the late afternoon, so the conference was almost over and attendance in the session was predictably unimpressive: I counted ten people, including myself and the session chair. Fortunately, numbers aren’t everything, and there was some good discussion with the audience after my talk, which dealt with wearable self-tracking devices and the problems that arise from the non-transparency of the information they generate and the limited ability of users to control their own data. I also talked about the problems and potential social impact of analysing self-tracking data collaboratively, tying the paper up with the work I’m doing in the KDD-CHASER project.

After the conference I proceeded to have a week’s vacation in NZ, which of course was the real reason I went to all the trouble of getting myself over there. While it’s not a huge country – somewhat smaller than my native Finland in terms of both area and population – I still had to make some tough choices when deciding what to see and do there, and I came to the conclusion that it was best to focus on what the North Island has to offer. I rode the Northern Explorer train service to Auckland and spent three nights there before working my way back to Wellington by bus, stopping along the way to spend two nights in Rotorua. From Wellington I did a day trip by ferry to Picton, a small town in the Marlborough Region (of Sauvignon blanc fame) of the South Island.

On Friday, two weeks after my departure from Dublin, I started my return journey, this time via Melbourne and with no time to go dilly-dallying outside the airport between flights. I boarded my flight in Wellington feeling a little sad to be leaving NZ so soon, but also satisfied that I’d made the most of my time there. I might have been able to fit in some additional activities if I’d travelled by air instead of overland, perhaps even another city, but I like to be able to view the scenery when I’m travelling, and there was no shortage of pretty sights along the train and bus routes. The conference also left a positive feeling: the programme was interesting, the catering was great and the choice of venue just brilliant. Above all, I’m happy to be done with all the flying!

Far side of the world

Things are getting quite busy again, as the project has come to a stage where I need to be producing some publications on early results while also doing implementation work to get more solid results, not to mention thinking seriously about where my next slice of funding is going to come from. Any one of these could consume all of my available time if I allowed it to, and it’s not always easy to motivate yourself to keep pushing when the potential returns are months away at best. What is all too easy, however, is to neglect things that are not strictly necessary – blogging, for example, but I’m determined to write at least one new post each month, even if it’s only because it makes for a welcome respite from the more “serious” work.

One thing that can help a great deal in maintaining motivation is if you have something nice in the not-too-distant future to look forward to, and as it happens, I have quite a biggie: the paper I submitted in January got accepted to the IEEE Congress on Evolutionary Computation, which will be held in Wellington, New Zealand. It’s a bit of a strange event for me to attend; while I do find the field very interesting, my professional experience of it, not counting some courses I took years ago when I was a doctoral student in need of credits, is limited to having been a reviewer for CEC once. However, there is a special session there on the theme of “Ethics and Social Implications of Computational Intelligence”, and this is something I have done actual published work on. It’s also one of the themes I wanted to address in my current project, so that’s that box ticked I guess. Besides, visiting NZ has been on my bucket list for quite a while, so I could hardly pass up the opportunity.

So, a small fraction of my time this month has been spent at the very pleasant task of making travel plans. Wellington lies pretty much literally on the opposite side of the globe from Dublin, so even in this day and age travelling there is something of an operation. It’s not cheap, obviously, but that’s not really a problem, thanks to my rather generous MSCA fellowship budget. The main issue is time: the trip takes a minimum of 27 hours one way, and the “quick” option leaves you with precious little time to stretch your legs between flights. I didn’t exactly relish this idea, so I ended up choosing an itinerary that includes a 12-hour stopover in Sydney on the outbound journey. This should give me a chance to take a shower, reset my internal clock and yes, also go have a look at that funny-looking building where they do all the opera.

It would make little sense to go all that way just for a four-day conference, so after CEC I’m going to take some personal time and spend part of my summer holiday travelling around NZ (even though it will be actually winter there). I still want to spend a couple of weeks in Finland as well, so I have to be frugal with my leave days and efficient in how I use my limited time. Therefore I’m going to be mostly confined to the North Island, although I am planning to take a ferry across Cook Strait to Picton and back – the scenery of the Marlborough Sounds is supposed to be pretty epic. On the North Island I’m going to stop in Auckland and Rotorua before coming back to Wellington; between Auckland and Rotorua, the Hobbiton movie set is a must-see for a Tolkien reader and Lord of the Rings film fan such as myself.

As for the conference, I’m very much looking forward to the plenary talk by my countryman Prof. Risto Miikkulainen on “Creative AI through Evolutionary Computation”. The idea of machines being creative is philosophically challenging, which is part of why this talk interests me, but I’m also intrigued by the practical potential. The abstract mentions techy applications such as neural network architecture design, but personally, I’m particularly interested in artistic creativity – in fact, when I was doing those evolutionary computation courses at my alma mater, I toyed with the idea of a genetic algorithm that would serve as a songwriting aid by generating novel chord progressions. Apart from the plenaries, the conference programme is still TBA, but it’s always good to have a chance to meet and exchange views with people from different cultural and professional backgrounds, and since Wellington is apparently the undisputed craft beer capital of NZ, I’m expecting some very pleasant scholarly discussions over pints of the nation’s finest brews.

Dear Santa

Now that I’ve managed to clear away all of the stressful and/or boring stuff that was keeping me busy, time to do something fun: Christmas shopping! After the break my project is going to be almost halfway through, and although it will be a good while yet before I’m ready to start conducting user tests, it’s time to start getting serious about recruiting participants. After all, the tests are supposed to be about analysing the participants’ data, so they can’t just walk in at their convenience – I need them to spend some time collecting data first, and to do that, they’ll need something to collect the data with.

Our initial idea was to recruit people who are already using a sleep monitor of some kind, and I’m sure we’ll be able to find at least a few of those, but naturally we’ll have a bigger pool of candidates if we have a few devices available to loan to people who don’t have one of their own. Also, it’s obviously useful for me to play with these devices a bit so I can get a better idea of what sort of data they generate and what’s the best way to export it if I want to use it for my research (which I do). Besides, I’m hardly going to spend my entire expense budget on travel even if I go out of my way to pick the most remote conferences I can find to submit papers to.

So I didn’t need to worry too much about what I can afford – one of the many great things about the MSCA fellowship – but that doesn’t mean that the choice of what to buy was straightforward, because the range of consumer products capable of tracking sleep is, frankly, a little bewildering. Some devices you wear on your body, some you place in your bed and some at the bedside, and although I soon decided to narrow down my list of options by focusing on wearables, that still left me with more than enough variety to cope with. Some of these gadgets you wear on your wrist, while others go on your finger like a ring, and the wrist-worn ones range from basic fitness bracelets to high-end smartwatches that will probably make you your protein smoothie and launder your sports gear for you if you know how to use them.

One thing that made the decision quite a lot easier for me is that the manufacturers of fitness bracelets now helpfully include all of their sleep tracking functionality in models that are near the low end of the price spectrum, and since I’m only interested in sleep data, there was no need to ponder if I should go with the inexpensive ones or invest in bigger guns. Also, I had a preference for products that don’t make you jump through hoops if you want to export your data in a CSV file or similar, so I looked at the documentation for each of my candidates and if I couldn’t find a straight answer on how to do that, I moved on. In the end I settled on three different ones: the Fitbit Alta HR, the Withings Steel, and the Oura Ring.

What I particularly like about this trio is that each of these models represents a distinct style of design: the Fitbit is a modern bracelet-style gadget, whereas the Withings looks more like a classic analog wrist watch, and the Oura is, well, a ring. I can thus, to a certain extent, cater for my study participants’ individual stylistic preferences. For example, I’m rather partial toward analog watches myself, so I’d imagine that for someone like me the design of the Withings would have a lot of appeal.

Today’s my last day at work before the Christmas break, and things are wrapping up (no pun intended) very nicely. The orders for the sleep trackers went out last week, this morning I submitted the last of my (rather badly overdue) ethics deliverables to the European Commission, and just minutes ago I came back from my last performance with the DCU Campus Choir for this year. The only thing that may impinge on my rest and relaxation over the next couple of weeks is that there’s a conference deadline coming up immediately after my vacation and I’m quite eager to submit, but I shouldn’t need to worry about that until after New Year. Happy holidays, everyone!

Busy times

With the end-of-year holidays approaching, things tend to get busy in a lot of places, not just in Santa’s workshop. My life in Ireland is no exception: there are five major work-related (or at least university-related) things that I’ve been trying my best to juggle through November, with varying success. Many of these will culminate over the next two weeks or so, so after that I’m hoping it will be comparatively smooth sailing till I leave for my well-deserved Christmas break in Finland. The blog I’m not even counting among the five and I’ve been pretty much neglecting it, so this post is rather overdue, and also a welcome break from all of the more pressing stuff that I should really be working on right now.

One area where I’ve had my hands full is data protection, where it seems that whenever a document is finished, there’s always another one to be prepared and submitted for evaluation. Getting a green light from the Research Ethics Committee was a big step forward, but there’s now one more hurdle left to overcome in the form of a Data Protection Impact Assessment. I’m very much learning (and making up) all of this as I go along, and the learning curve has proved a rather more slippery climb than I expected, but I’m getting there. In fact, I’m apparently one of the first to go through this process around here, so I guess I’m not the only one trying to learn how it works. I hope this means that things will be easier for those who come after me.

Meanwhile, I’ve been preparing to give my very first lecture here at DCU – thankfully, just one guest lecture and not a whole course, but even that is quite enough to rack my nerves. It is a little strange that this should be the case, even after all the public speaking I’ve had to do during my fifteen-plus years in research, but the fact of the matter is that it does still feel like a bit of an ordeal every time. Of course it doesn’t help that I’m in a new environment now, and also I’ll be speaking to undergraduate students, which is rather different from giving a presentation at a conference to other researchers. Still, I’m not entirely unfamiliar with this type of audience, and I can recycle some of the lecture materials I created and used in Oulu, so I think I’m going to be all right.

Speaking of conferences, I’m serving in the programme committee of the International Conference on Health Informatics for the second year running and the manuscript reviewing period is currently ongoing, so that’s another thing that’s claimed a sizable chunk of my time recently. Somewhere among all of this I’m somehow managing to fit in a bit of actual research as well, although it’s nowhere near as much as I’d like, but I guess we’ve all been there. The software platform is taking shape towards a minimum viable product of sorts, and I have a couple of ideas for papers I want to write in the near future, so there’s a clear sense of moving forward despite all the other stuff going on.

So what’s the fifth thing, you ask? Well, I’ve rekindled my relationship with choral singing by joining the DCU Campus Choir, having not sung in a proper choir since school. Despite the 20-year gap (plus a bit), I haven’t had much trouble getting into it again: I can still read music, I can still hit the bass notes, and I don’t have all that much to occupy myself in the evenings and weekends so I have plenty of time to learn my parts (although I’m not sure how happy my neighbours are about it). The material we’re doing is nice and varied, and the level of ambition is certainly sufficient, as it seems like we’re constantly running out of rehearsal time before one performance or other. Our next concert will be Carols by Candlelight at DCU’s All Hallows campus on the evening of Monday the 10th of December, so anyone reading this who’s in town that day is very warmly welcome to listen!

First blood

Time to look at the first results from my project! Well, not quite – the first results are in a literature survey I did immediately after starting the project and made into a journal manuscript. I’m currently waiting for the first round of reviews to come in, but in the meantime I’ve been busy developing my ideas about collaborative knowledge discovery into something a bit more concrete. In particular, I’ve been thinking about one of the potential obstacles to effective collaboration from the data owner’s perspective: privacy.

In the aftermath of the much publicised Facebook–Cambridge Analytica scandal, one would at least hope that people are becoming more wary about sharing their personal data online. On the other hand, with the General Data Protection Regulation in full effect since 25 May, a huge number of people are now covered by a piece of legislation that grants them an extensive set of personal data control rights and has the power to hurt even really big players (like Facebook) if they don’t respect those rights. Of course, it’s still up to the people to actually exercise their rights, which may or may not happen, but after all the GDPR news, emails and “we use cookies” notices on websites, they should be at least vaguely aware that they have them.

The increased awareness of threats to privacy online and the assertion of individuals, rather than corporations, as the owners of their personal data are welcome developments, and I like to think that what I’m trying to accomplish is well aligned with these themes. After all, the collaborative knowledge discovery platform I’m building is intended to empower individual data owners: to help them extract knowledge from their own data for their own benefit. This does not make the privacy issue a trivial one, however – in fact, I wouldn’t be surprised if it turned out that people are more uneasy about sharing a small portion their data with an individual analyst focusing on their case specifically than about using an online service that grabs and mines all the data it can but does so in a completely impersonal manner. The platform will need to address this issue somehow lest it end up defeating its own purpose.

The angle from which I decided to approach the problem involves using a domain ontology and a semantic reasoner, which are technologies that I had been interested in for quite some time but hadn’t really done anything with. As I was doing the literature survey, I became increasingly convinced that an underlying ontology would be one of the key building blocks of the new platform, but it was also clear to me that I would need to start by modelling some individual aspect of collaboration as a proof of concept, so that I would fail fast if it came to that. If I started working top-down to produce a comprehensive representation of the entire domain, in the worst case I might take ages to discover nothing but that it wasn’t a very viable approach after all.

All this came together somewhat serendipitously when I found out that the 2nd International Workshop on Personal Analytics and Privacy (PAP 2018), held in conjunction with the European Conference on Machine Learning and Principles and Practice of Knowledge Discovery in Databases (ECML-PKDD 2018) in Dublin, had an open call for papers. The submission deadline was coming up in a month – enough time to put together some tentative results, though nothing hugely impressive – and coincided rather nicely with the date when I was planning to fly to Finland for my summer holidays. In about two weeks I had the first version of the manuscript ready, with another two left over for revisions.

The ontology I designed is based on the idea of a data owner and a data analyst (or possibly any number of either) using the collaborative knowledge discovery platform to negotiate the terms of their collaboration. Each uses the platform to specify requirements, but from opposing perspectives: the data analyst specifies analysis tasks, which require certain data items as input, while the data owner specifies privacy constraints, which prevent certain data items from being released to the data analyst. The data owners, data analysts, data items, analysis tasks and privacy constraints are all registered as individuals in the ontology and linked with one another such that a reasoner is able to use this information to detect conflicts, that is, situations where a data item is required for a data analysis task but not released by the data owner.

To resolve such conflicts, the data owner and the data analyst may, for example, agree that the analyst receives a version of the dataset from which the most sensitive information has been removed. Removing information reduces the utility of the data, but does not necessarily make it completely useless; finding a balance where the data owner’s privacy preferences are satisfied while the data analyst still gets enough material to work with is the essence of the negotiation process. The ontology is meant to support this process by not just pointing out conflicts, but by suggesting possible resolutions based on recorded knowledge about the utility effects of different methods of transforming data to make it less sensitive.

For the PAP workshop paper, I only had time to design the logic of conflict detection in any detail, and there also was no time to test the ontology in a real-world scenario or even a plausible approximation of one. It therefore hardly seems unfair that although the paper was accepted for a short oral presentation at the workshop, it was not accepted for inclusion in the post-proceedings. Obviously it would have been nicer to get a proper publication out of it, but I decided to go ahead and give the presentation anyway – ECML-PKDD is the sort of conference I might have gone to even if I didn’t have anything to present, and since the venue is a 25-minute walk away from my house, the only cost was the registration fee, which I could easily afford from the rather generous allowance for sundry expenses that came with the MSCA fellowship.

Croke Park may seem like an unlikely place to have a conference, but it is in fact a conference centre as well as a stadium, and seems to work perfectly well as a venue for an academic event – meeting spaces, catering and all. Besides Croke Park, we had Mansion House for the welcome reception and Taylor’s Three Rock for the conference banquet, so can’t complain about the locations. The regular programme was quite heavy on algorithms, which isn’t really my number one area of interest, but I did manage to catch some interesting application-oriented papers and software demos. What I enjoyed the most, however, were the keynote talks by Corinna Cortes, Misha Bilenko and Aris Gionis; there were two others that I’m sure I also would have found very interesting but was unable to attend, because there was a rather important deadline coming up and so I had to zig-zag between Croke Park and DCU to make sure I got everything finished on time.

My own talk went reasonably well I felt, with an audience of about twenty and some useful discussion afterwards on how I might go about modelling and quantifying the concept of utility reduction. On the last day of the conference, which was today, I went to another workshop, the 3rd Workshop on Data Science for Social Good (SoGood 2018), with presentations on how machine learning and data mining techniques can be used to address societal issues such as homelessness and corruption. I especially enjoyed the last one, if enjoy is the right word – it dealt with efforts to combat human trafficking by means of data science, certainly a worthy cause if ever there was one, but also rife with difficulties from the scarcity of good input data to the nigh-impossibility of devising an ethically justifiable experiment when there are literally lives at stake. Plenty of food for thought there, and a fine way to finish off this week of conference activities; on Monday it’s back to business as usual.