Speed test.

Spent this week at the Innotrans premier rail conference in Berlin, which has meant limited time for any extra-curricula computing nerdery but I did test something which turned out to be a bit of a shock.

Some of the stands at this event were works of art - and some were almost the size of small towns, complete with coffee shop, bar, bleacher seating and live entertainment. God knows how much these things cost but they are well received by the attendee's. Anyway a thought came to me while wandering around - there should be a competition for the best stand. To the best of my knowledge there wasn't an official one organised - would probably be far to much effort and just end up cheesing off some stand owners. So I thought I would do my own and try and record it using my new found social media tool set!

Before I go any further I must point out that this survey was NOT scientific in ANY way - entrants were selected simple along my timeline through the event and purely based on my personal 'gut' reaction at the time of passing the stand.

So the plan was, to photograph stands as I wandered around, then select a stand for an award base upon what I had come across. Photo's and award were then Tweeted to #innotrans and then later Storified into an award ceremony in a Storify story! The whole process probably only took me say 5 minutes per award to manage. The compiled and 'published' award ceremony can be fond on the following link;

http://storify.com/grandwizz/innotrans-2012-awards

Well the strange thing was that I started off doing this as a bit of fun and to see if I could generate some 'e-traffic'. Fortunately I kept the awards 'sensible' and 'clean'  - could have taken a completely different route for some of the stands if I had been so inclined believe you me.

Anyway, the 'award ceremony' was carried out on the last day with me Tweeting the final winners and then the link to the Storify site. All done from the Innotrans business lounge - fitting for an award ceremony I thought (what a great place - free wifi and all that). The shocking thing was that within seconds the story had been re-tweeted by @EURAILmag, @OfficialHitachi, @thalesgroup and @LR_Rail to over 6000 potential readers! Only slight panic set in  - until very positive comments came back - phew!

Quite a buzz!

Revelation.....

OK so I've not taken the time to check out some of the web programming tools so far. Too busy trying to get back into the swing or real computing! But got a flea in the ear from one of my trusted advisor's - the Lancaster computing one - and was 'advised' to check out a site called http://www.w3schools.com/ as I was asking some dumb questions on web page design.

Anyway - I did just that one spare lunchtime - what a revelation!

HTML looks just like the old WordStar editor I used to use. Shock, horror, a scripting language Ctrl-B and all that. Well at least I could see myself getting my head around the simple formatting elements of the language. Nothing new under the Sun eh?

So now the situation is 'Cloud computing' looks a lot like an old mainframe setup and HTML turns out to be an old editor. There is hope yet for us ancients!

The w3schools site is pretty useful for all those questions you wanted to ask about the multitude of languages but couldn't be bothered, I'm sure to be using it again!

Information overload ....

This week has been more of a maintenance and upgrade week on the revival path. I am advancing to next level on the computing and social networking fronts.

On the networking front I have discovered Tweetdeck - why didn't someone tell me about this before! This is the dashboard of dashboards that blows your mind with all the information that can be displayed. No doubt our Human Factors team would tell me off for my set-up  - cognitive block and all that. But wow it definitely gives you the feel that you are looking into the networks you have set up. Its also free!!

On the serious computing front I have re-energised the ROBFIT GitHub repo by uploading the next routine BREAD.FOR that is used for reading the raw data - so not that stunning but essential! I have also discovered that you can link GitHub to your LinkedIn profile. LinkedIn is becoming more useful by the day at this rate - could well become the spoke at the centre of all my various meanderings across the web.

Data dump - information reset ....

Communication breakdown.

Progress on the swimming waveform analysis front is grinding to a halt as communication between the various team members has become difficult. A combination of time zone differences (12 hours between the 'thought leader' and the 'development team'), recovery from jet lag and unfamiliarity with the code sharing site have all contributed to the situation.

How best to get a grip on things again?

The main issue has been the way development has had to be carried out using a 'rapid prototyping' approach. Essentially get something up and running and review what it looks like then tweak (sometimes TWEAK) then review then tweak again ..... continue ..... until right answer. Which all worked fine when all parties were together in one place. However, now the review and development cycle has become protracted  the 'thought leader' is struggling seeing the code run and the 'development team' is wondering what happens next.

If you read the text on this software engineering practice everything works seamlessly and Bob's your aunt you end up with the perfect code (sorry 'app' - fully documented too!). We are attempting to use an approved approach that will keep us out of the hacking arena. However, what its not doing is helping much on progressing around the development cycles or on homing in of the final solution. You could end up going round and round and round and round ...... just another variation please.

What we need is a means of facilitating the capture of emerging requirements and or questions from the 'thought leader' that the 'development team' can then work on and reply to. Done in a simple and visible way so that all parties can immediately understand the level of progress, identify any issues, and know who is in the seat for resolving them. Progress around the cycle can then be maintained - hopefully.

Just need to get everyone using Trello properly now then ..... ;)

Languages suck .... computer ones that is ;)

More a though for the day this one....

I have been both impressed and confused over the last few months by the sheer number of software languages that you appear to need to keep abreast of these days. I am easily into double figures on the count and I'm not even trying. What is going on?

In the good old days you would get by with BASIC, FORTRAN and possibly C but only if you were a real geek. Oh and then there was JCL (my god - I'd almost forgotten about that). These days the number has ballooned and careers have been made upon the back of the various mutations of operating systems and their associated languages.

In past blogs - as you can read - even the production of a simple package (sorry 'app') to analyse a waveform has required quite a bit of soul searching on which language to use. Surely what is needed is some overarching operating system of languages to act as a master controller - hey maybe nobody has thought of that one!

With the IoT (Internet of Things) emerging what is the best way forward - or are we doomed to even greater mushrooming of languages.

The balloon (or my mind) must pop at some point.....

Data presented!

Well not much progress last week as holiday return trip home has got in the way - was a long way back!

There was a little bit of movement though - the week was spent checking the code. I was please to note that even with all the new programming language bell's and whistles we still ended up de-bugging using the good old print statement. Which was actually very simple in Python - unlike my memory of Fortran 'WRITE' statements - though I'm sure all that has changed by now - at least I hope so.

Anyway - here is a print out of 5 right (top) and 5 left (bottom) hand pressure waveforms extracted from the first dataset.

The work going forward is to start to analyse the structure of these to try and come up with an optimum shape that will deliver maximum power for the swimmer. A swimmer can then use this information in real time to make adjustments to their technique.

I don't know much about swimming but this is interesting stuff - the appliance of science!

Data extracted!

Well much to my amazement Bambofy has managed to build a code to pull out the swimming pressure data from the hand sensors. Not that I doubted he could do it, just that I didn't think Python was appropriate for doing this extraction. Just goes to show - old dog's and new tricks can happen. 

My view of Python - from looking over the shoulder - is it seems pretty flexible for string manipulation, good for object coding, simple to produce plots (we would still be loading the plotting library in Fortran - Python variant knocked up in 10mins no lie!) and can add up. Not sure what editor is being used to build the code but it puts out a great psychedelic screen for doing the edits!

Not sure how it will get on with the next phase which will involve a bit more complex mathematics - we will see......