Saturday, 22 August 2015

W/c 17th August: Curves, KATs and more curves

This image pretty much sums up my week. For the most part, I've stared at LabVIEW graphs of curves being fitted: and that's about it. There are good reasons for this, though I won’t give out too much detail, since we'll need to hold that back for the publications. And a lot of it has been debugging code and rethinking models.

I had a particularly nasty bug where LABVIEW fitted a lovely curve, but returned a denominator which would always be zero in the output spreadsheet. I went through the code time and again. It all seemed right. When I tried it on one file at a time (writing output to the screen) it worked fine. Process a batch in one go and the summary spreadsheet returned the same impissible zeroes. Loads of them. Not all the time, but a lot. Yet some results matched perfectly with the individual runs.

And the solution, of course, was trivial: I'd set LabVIEW to write the spreadsheet to 3 decimal places. So 0.0006 showed up as 0.001 (close enough), but 0.0004 showed up as 0 - not 0.000, just 0. One character replaced and the problem was solved.

It was worth it, though - it all seems to be coming together, and after weeks of investigating and rethinking, we are (to quote my colleague Mark Mon-Williams) "on the verge of something big".

It was a week where I did little else. But just as you have some weeks where you do much but get little done, the payoff is that you get some weeks where you do little, but get a lot done! So, revised electronics for FATKAT are finished and tested (and they work!), a prospective avenue for taking some Bayesian analysis into oilfield corrosion (a door I've been pushing on for a little while now) has opened up, and I had a very productive meeting with JCM seating on the postural front. So there's lots of good news this week.

Not every week can be like that, of course, but I'm hopeful that next week will see some important developments. Stay tuned!

Friday, 14 August 2015

w/c 10th August: Curve Fitting, Coding and Commercialisation

It's been a short week this week, since I've been off two days providing childcare during the summer holidays, but there's been a lot of progress. The week kicked off with a meeting with Brian Henson and visiting researcher Miyong Lee to look into some experiments on weight perception using FATKAT. This is exciting - having actually made the system, it's good to be getting as much use out of it as we can! I also had a meeting with Will Shaw to discuss the priorities for his upcoming studies, particularly in terms of the new version of FATKAT we're building. I have a couple of priorities for rebuilding the electronics next week, so Will's study can get underway, whereas the new casings we've designed can wait. All good stuff.

I also had a productive meeting with our Research and Innovation Services chaps and external consultants about commercialising some of Ian Flatters' work. Again, very exciting - but also hush hush, since we don't want to give details away.

But most of the week has been spent writing and debugging LabVIEW code for fitting Gaussian peaks to velocity profiles for reach-to-grasp actions. As to why, I'll explain in due course - but suffice to say there's been an awful lot of building and rebuilding code to make it more modular, teasing out why particular bugs crop up (missing markers return a value of 37, 000, 000, 000, 000, 000, 000, 000, 000, 000. Put that as a step change through a butterworth filter, and you get some very bizarre results.  Then there's breaking the actual reach-to-grasp movement down into its component parts - how do we differentiate where feedforward ends and feedback kicks in? Anyway, it's mostly done now - the technical bits are in place: next week I can focus on the actually analysing data. Hurrah!

Sunday, 9 August 2015

Week in Review : 3rd August

It's been a funny old week this week. I've done much, but finished little. That's largely because I've dedicated most of my time to data analysis on old reach-to-grasp experiments. That's meant a lot of debugging code, picking through data to see where problems have arisen, and refreshing my knowledge of curve fitting and Gaussian functions. On the one hand, I don't have anything concrete to show for it. On the other, I've overcome a bunch of technical hurdles and I'm in a position to do more constructive work this week - touch wood.

Of course, there's been more than that - PhD supervision, teaching is back on my agenda, so timetables have been debated, handouts sent for printing, and project outlines prepared. And I've been steadily assembling parts for the next FATKAT. Of course, I'm only in three days next week - so I may be writing an exciting update, or reporting more delays.

   It's also been a year since we took Button Bash to Breeze on Tour for Playday! Happy times. I'm sad not to be doing anything for it this year - but given how things worked out, I'm also rather glad. But next year... who knows?

Thursday, 6 August 2015

End of an era: stepping down as Product Design Programme Manager

This is my first blog post of the 2015/16 academic year, and my first as ex-Programme Manager for the MDes, BSc Product Design course here in Mechanical Engineering at the University of Leeds. This is less dramatic than it sounds: I haven't changed jobs, I'm still teaching the same modules and the same tutorial groups, and the same dissertation projects. In fact, the students who aren't Student Reps won't notice a lot of difference. But it's a big deal for me, so I wanted to pause and reflect on what it means, what I've learned, and where I (and Product Design) go next.

My First Big Commission

Being a Lecturer in the School of Mechanical Engineering is the only job I've ever had (if you don't count an industrial placement year and summer work at Knoll Pharmaceuticals in my pre-doctorate days). I started the post in September 2005 at the tender age of 26, before I'd even completed my PhD: the first lecturer appointed uniquely to the Product Design course. There had already been a Professor (Pat Jordan) and teaching fellows appointed: but still, I was the first lecturer. Product Design (affectionately known as PDES after its course code) was still young: it had started in 2003, and wouldn't graduate its first students until the end of my first year in post. It was a faculty-wide initiative, involved staff from all the in the Faculty of Engineering, and staff from other faculties to boot. It was an unusual mix of art and engineering - most design courses are either engineering-focused with some art, or art-focused with some engineering. Our USP was to aim straight down the middle - an even balance of both, and an investigation of the links between them. The goal wasn't to drawn in engineers, but to address the shortage of technical skills by providing a route for those from a more creative background to acquire them. We were feeling our way in the early days - rapidly iterating, finding out what worked and what didn't. Getting new resources. I was almost immediately given the job of looking after PDES admissions, running open days, reading UCAS forms, making decisions on borderline cases. Just less than two years later, in August 2007, I was made Programme Manager for Product Design, stepping in to fill the shoes of Alison McKay, who had steered the course through its inception and its first full round of graduates. The course was bedding in, the rapid evolution slowing down, and the time had come to rotate the leadership, and the job fell to me. In two years, I'd gone from an inexperienced and unqualified teacher to leading the Programme. It was the most responsibility I'd ever been given - and in my professional capacity, it still is.

Times of Change

My greatest fear was that I would somehow shipwreck the course. I didn't - it's still here, it's topped the Guardian League table for Product Design, and I've seen more than 250 students right through from recruitment to graduation in my time as Programme Manager, with a student satisfaction rate of over 90%, and student employment rates that are on a par with our engineering courses. I reckon I've done okay and while managing a degree programme is never easy, it's fascinating how things I once found daunting (chairing a theme team, managing a budget, responding to student feedback) are now things I take fro granted.
   It hasn't all been plain sailing though, and the course has had to evolve a lot in that time. When we had our tenth anniversary celebration, bringing in graduates new and old to talk about their time on the course and beyond, I reflected on how the course we taught in 2013 was very different from the one set up in 2003. I think there are only about five modules on the whole programme that have stayed the same during my tenure as Programme Manager. Then again in 2023, the course will look different again. It has to: times change, and academia is all about adaptation.
   My time in charge has been characterised by the need to adapt. You might recall that 2007 was just before the world economy fell off a cliff, and budgets had to be cut - in 2010, the University shed 10% of its staff, and 20% of its non-staff budgets. That meant a lot of rationalisation. What do we really, really need to teach? Not what's cheap - what's the best use of our money? Then £9k fees arrived, core and margin recruitment, the need to tighten entry standards, and run a smaller course of high-calibre students.
   Most significantly, as I came into the role, the course was moved from being one that was Faculty wide, to one housed within Mechanical Engineering. The difference to the students was cosmetic, but administratively, it meant aligning budgets, software needs, teaching practices, the staff student forum, exam boards - we've gradually aligned modules, shifted from buying in modules elsewhere to delivering them ourselves, so we could ensure their suitability for our students.
   If I have one achievement of which I'm most proud, it's that I've moved the course from being an anomaly, an outsider, to an integrated part of the department, without losing its distinctive feel. That's not been easy, and the credit can't go to me alone - we're a good team, and we've been blessed with some good managers during the transition. Martin Levesley, as Director of Student Education during most of my run and the biggest period of change; Dave Barton as Head of School; Mark Wilson as the admissions tutor during the turbulent recruitment changes; and Victoria Price as our marketing director - all were hugely supportive in keeping PDES as a design course, rather than trying to water the vision down into "engineering with a bit of design".

 Goodbye Yellow Brick

So why go now? There are a few good reasons. One of them is that eight years is a long time to do a single role. It provides continuity, and I don't think I could have stepped down sooner without leaving a lot of loose ends in the whole integration. But that's done now, and there's a danger of getting too wedded to your own changes. Also, a fresh perspective is always helpful, and the challenges facing the course are changing. Its no longer about stability, and rationalisation, and integration - it's about how we move forwards, and how we engage with the new opportunities presented by university initiatives such as the Discovery Themes (the new approach we take to deliver electives). Lots of exciting opportunities, but I think we'll benefit from having a fresh pair of eyes looking at them. Also, the programme has been run by an engineer for the last eight years, and we've sorted out the engineering side of it - the opportunities now are about the creative side, and someone from a design background is far better place than I to do that. So the course feels like its at a natural turning point, a good time to transition, rather than starting new initiatives.
   Then, of course, there's FATKAT (the Finger and Thumb Kinetic Assessment Tool, in case you don't keep tabs on what I'm doing) and all the grip and posture research. I had exactly one Phd student when I started as Programme Manager. Now I have seven, in varies stages of their degrees. I have a commercialisation project under way - that takes time. Links with Born in Bradford, with JCM seating - they all need to be cultivated. We have models that need to be developed and explored if we're to publish them in time for the next REF. And FATKAT needs nurturing at the moment - it's ready to use, but funders want to see results, and more development before they'll put money into it. We have to speculate to accumulate, as it were, and I can't give FATKAT and PDES the attention they both deserve. So, again, it's a natural time for me to shift gears, so while it's not off to pastures new, it's the end of one era, and the dawn of another.
   I'm excited. Strangely, I'm not sure I'll miss running PDES - I feel like I achieved what I set out to do with it, and now is a time to end on a high note, rather than set myself new goals for the course. It's a natural time to go, and with the inestimable Dan Trowsdale taking over, I know the course is in good hands.

The Best Laid Plans

Of course, I didn't get quite the end I'd hoped for. My recent illness meant that for the last three months of my tenure, Dan was already de facto manager for PDES. So, my hopes for a stirring speech at our exhibition or graduation, didn't come to pass. Indeed, looking back through my emails, I see that my final official pronouncement as programme leader was "Yup, looks good to me!". Ah well, such is the way of things. And of course, I haven't actually gone anywhere - it's not like I've changed jobs. I have just one regret; that I didn't finish steering PDES through the accreditation process. There's a raft of documentation that's been sat on my desk for six months, as ill-health chipped into my time, and higher priority matters took up the time I had left. Still, you can't do everything: I'm better, I'm steadily ramping up my hours (75% of full time and counting!), and my focus for the immediate future is everything grip related. Product Design is in safe hands, so here's to a FATKAT future!