Tuesday, April 12, 2011

Papers presented at JURSE 2011

I'm presenting two papers at this year's Joint Urban Remote Sensing Event being held in Munich this week. The proceedings are not yet available on IEEE Xplore, but I have made preprints available on my website.

  • P.T.B. Brett and R. Guida. Bright line detection in COSMO-SkyMed SAR images of urban areas. In Joint Urban Remote Sensing Event 2011 (JURSE 2011), pages 253-256, 11-13 April 2011. [Preprint]
  • R. Guida and P.T.B. Brett. A SAR image-based tool for prompt and effective earthquake response. In Joint Urban Remote Sensing Event 2011 (JURSE 2011), pages 213-216, 11-13 April 2011. [Preprint]

Saturday, March 26, 2011

Weekly News Stash

There have been a large number of blog posts and news stories over the last week that I found interesting, but I didn't have time to blog on each of them individually. Instead, here are the highlights. I've probably missed a bunch of relevant stuff, so please feel free to point them out in the comments.

Libya and Wikileaks

Tom Watson (MP for Bromwich West) posted on his blog to assert that the UN and allied intervention in the Libyan insurgency (or uprising or civil war, depending on your perspective) constitutes "the first Wikileaks war".

Understandably, this development blows the minds of liberals who have stoically supported WikiLeaks as an innovative new international information movement that would almost certainly deflate the interventionist and imperialist tendencies of the big western powers… the smartest pro-transparency analysts have always realized that the revelations the U.S. cables represented would almost certainly lead to unforeseen consequences, if not armed conflict.

I'm not sure I entirely agree that one can entirely lay the blame for the situation at the door of Wikileaks. I believe that the rise of social networking (especially Twitter and Facebook) as well as citizen journalism via blogging and video sharing sites such as YouTube have played as much as an enabling role — or perhaps even more so.

In related news, Bradley Manning, the US serviceman accused of being responsible for the leaking of large amouts of classified US embassy cables (among other materials) has now been incarcerated in solitary confinement and and subjected to routine psychological torture for over 300 days. Whether or not you consider him a criminal and deserving of punishment, I believe that "no-touch torture" is still torture, torture is barbaric and should never occur in a country that considers itself civilised, and that Bradley's rights both to a speedy trial and to be considered innocent until proven guilty have both been brutally violated. Loz Kaye, leader of the Pirate Party UK, gave a very well received speech on the subject at last Sunday's protest outside the US Embassy in Grosvenor Square.

Engagement with the Liberal Democrats

Loz also was recently invited to take part in a panel session on "Who controls the Internet?" at the Liberal Democrat party conference, and subsequently contributed a blog post on the Pirate Party perspective to the Lib Dem Voice blog.

Both his article and the comments are worth a read. In particular, they demonstrate that even within the Lib Dems, opinion is heavily divided on the issues of Internet governance and intellectual property policy and enforcementt. A microcosm of this, of course, can be seen in Parliament; contrast the behaviour Lord Clement-Jones in the Lords and Julian Huppert, MP for Cambridge, in the Commons.

In academia

There have been several interesting news stories from academic research in the last week.

Firstly, a paper from Joel Waldfogel, an economist at the University of Minnesota. He carried out some research into claims by the recording industry that copyright infringement was stopping new music or new artists coming to market, and published a paper on his results, whimsically entitled "Bye, Bye, Miss American Pie?" Not only was he unable to find any evidence that the rise of Napster and peer-to-peer filesharing have resulted in an impact on either, but he also found that there has been a significant shift from the major labels to independent labels in the releasing of new music. (More coverage from Michael Geist, TorrentFreak and Techdirt).

The 1709 blog reported on a talk given by Professor Paul Heald entitled "Do bad things happen when works fall into the public domain?". In particular he debunked both the assertion that falling into the public domain will lead to underusage of works, and that it will result in the devaluation of works. I note that he's published on the subject, and I'm going to try to get hold of his papers, as they sound like they will be interesting reading.

From the London School of Economics there came a highly critical report on the deservedly-maligned Digital Economy Act 2010, called "Creative Destruction and Copyright Protection." In particular, it has this to say:

The DEA gets the balance between copyright enforcement and innovation wrong. The use of peer-to-peer technology should be encouraged to promote innovative applications. Focusing on efforts to suppress the use of technological advances and to protect out-of-date business models will stifle innovation in this industry.

Another article critical of the DEA has been published by William Dutton at the University of Oxford. Called "Aiming at Copyright Infringers and Hitting the Digital Economy", it argues strongly that the Act will not only not achieve its stated objectives, but will in fact have several negative effects. The article actually mentions the Pirate movement, and quotes from the PPUK manifesto!

It's nice to see academia providing some objective criticism of the oft-repeated claims of the copyright industries — claims which so far no independent research has been able to substantiate or reproduce, despite how often they crop up.

In the courts

The High Court hearings for the judicial review of the aforementioned Digital Economy Act are currently taking place. They started last Wednesday, and are expected to conclude sometime next week. Will Tovey has posted some commentary on the Pirate Party UK blog. Summary: no matter what the outcome, the result is almost certain to be appealed, and it's quite likely to go all the way to the European Court of Justice, meaning that we could be looking at a couple of years before the final outcome is decided.

The big headline his week is that a selection of record labels are suing the company behind the Limewire filesharing software for a total of 75 trillion US dollars (to be precise, $ 7.5x1013) in statutory damages. To put that into perspective, the GDP of the entire world is only $75.5 trillion, and the global money supply is only approx. $50 trillion. It would therefore be accurate to say that Limewire is being sued for all the money in the world. I consider this excellent evidence for the fact that the statutes are wrong. This Slashdot comment was the best take on the ridiculous situation that I've read so far.

Now how in the hell does that promote "progress of the arts and sciences"? Answer: it doesn't, it is simply a way for a "leecher class" to make eternal checks off locking up the entire culture of a race. How many works have already been lost simply because nobody could legally make a copy and the copyright holders couldn't figure out a way to "monetize the IP" and just let it rot?

That's it for this week. Hopefully next week there won't be quite so many items that I'm desperate to share with the world!

Wednesday, March 23, 2011

Survey on "Open Standards in the Public Sector"

The Cabinet Office is currently carrying out a survey on "Open Standards in the Public Sector". The widespread use of open standards in government would be a major step forward for the UK, both in terms of stimulating innovation in the IT sector by lowering barriers for entry in the public sector, and in terms of ensuring that everybody is able to use and interact with UK government online services without being required to use a particular software platform or limited set of platforms.

Two areas of the survey were of particular interest to me: the opening section on defining what exactly an "open standard" is, and the section on standards that are being evaluated for computer workstations. The survey, however, covers a huge array of areas for possible standardisation in IT (for example, content syndication, e-voting, web services and VoIP), and there's lots of scope for people with domain-specific knowledge to contribute on the areas that they're most familiar with.

I encourage everyone who is interested in seeing increased adoption of open standards in governmental IT procurement to take part in this survey — and in particular, to encourage the UK to standardise on PDF and OpenDocument rather than Microsoft's bought-and-paid-for non-standard, Office "Open" XML.

What is an open standard?

The survey outlines five conditions for an open standard that the government proposes:

1. Open standards are standards which result from and are maintained through an open, independent process.

Open standards need not necessarily result from an open and independent process -- as a classic example, the Internet Protocol and Transmission Control Protocol (TCP/IP) on which the Internet is based were developed behind closed doors by a small working group at Stanford in the early 1970s. However, I would agree that the success of TCP/IP as an open standard has very much depended on the fact that it has been maintained by an open and independent organisation (the IETF).

2. Open standards are standards which are approved by a recognised specification or standardisation organisation, for example W3C or ISO or equivalent.

There are two sources of concern with this condition. Firstly, it is unclear who maintains the list of "recognised" specification or standardisation organisations, nor how such an organisation can become "standardised", and greater clarity would be appreciated. Secondly, the ISO in particular operates extremely slowly, and waiting for ISO standardisation of an already-widely-used open standard may well hamper flexibility and responsiveness in government procurement. However, in principle this condition seems a sensible one.

3. Open standards are standards which are thoroughly documented and publicly available at zero or low cost.

This is an essential condition. If a standard's documentation cannot be be easily and inexpensively obtained, it provides a serious barrier to individuals, small companies and community organisations that wish to implement and use that standard.

4. Open standards are standards which have intellectual property made irrevocably available on a royalty free basis.

This condition is important in order to avoid the risk that corporations with intellectual property interests in a standard wait until the standard has widespread adoption before introducing or substantially increasing royalties.

5. Open standards are standards which as a whole can be implemented and shared under different development approaches and on a number of platforms.

This is the key condition, and cuts to the heart of the reason open standards are needed. Some standards organisations require at least two independent, full implementations of a standard to exist before adopting the standard, and I would commend this approach to the Government.

Standards for computer workstations

Many of the standards listed in this section of the survey are sadly nothing of sort were not open, and many of them weren't standards either. Highlights that I particularly enjoyed included:

  • The presence of .doc, .xls and .ppt files as a "standard", and inclusion of Microsoft's Office Open XML, which is hardly "open".
  • HTML as an document format for presentations and spreadsheet data.
  • A section on video/animation formats that included no open standards whatsoever, and included .swf files (neither open nor standardised) twice.
  • It was heartening, however, to see Open Document Format listed, along with Unicode and UCS (although why Unicode isn't already mandatory is beyond me).

Thursday, March 17, 2011

Beef shin hotpot

The cheesecake I described in my last blog post was absolutely delicious!

I enjoy eating beef, but the most well-known cuts are quite expensive. Shin is a less-commonly used cut (you probably won't find it in Sainsbury's), but is still delicious in stews and hotpots as long as you cook it correctly! Ask for it at the butcher or at a farmers' market. Here's a shin hotpot I enjoy making — this recipe serves 4-6.

  • 450 g shin of beef, boned and diced
  • 2 tbsp sherry vinegar
  • 1 tbsp plain flour
  • 6 pork sausages
  • 450 g potatoes
  • 1 dessert (eating) apple
  • 2 tomatoes
  • 1 onion
  • 450 ml beef stock

Put the beef and vinegar in a bowl, and cover with clingfilm. Marinate for an hour, stirring occasionally. This softens and tenderises the meat.

Pre-heat the oven to 160 °C. Thinly slice the potatoes, apple, tomatoes and onion, and cut the sausages into chunks.

Drain the beef, and (optionally) pat it dry with paper towels. Toss the sausage and beef pieces in the flour.

In a large casserole dish, start building the hotpot with layers of sliced vegetables and meat:

  1. 1/3 of the potatoes
  2. 1/2 of the apple, tomato, and onion
  3. 1/2 of the sausages and beef
  4. 1/3 of the potatoes
  5. The rest of the apple, tomato and onion
  6. The rest of the meat
  7. A top layer of potatoes (make sure you keep enough back from the previous layers to cover the casserole fully!

Give the dish a little shake to help the casserole settle, and add the stock (it should come about halfway up the casserole).

Cover and cook in the oven for 2 1/2 hours. For the last 10-15 minutes, take the lid off and turn the oven up to 200 °C to allow the top layer of potatoes to crisp up.

Serve in bowls, with plenty of the stock. Leftovers keep really well in the fridge!

Wednesday, February 23, 2011

Seattle Cheesecake recipe

Thanks to one of my colleagues, here's the cheesecake recipe I'm going to try to bake this evening. I've converted the units to metric, scaled the quantities, and added ingredients for a British-style base and an apricot topping.

Start by greasing a 20 cm spring-form tin and lining the base with a round of greaseproof paper. Pre-heat the oven to 160 °C.

Biscuit base

  • 12 digestive biscuits
  • 60 g unsalted butter

Crush the biscuits to the consistency of fine breadcrumbs. Melt butter and mix into crushed biscuits. Gently press mixture into bottom of tin using the back of a spoon to form a level base. Bake for 10-15 minutes until lightly browned and just set. Set aside for at least 5 minutes.

Bottom layer

  • 625 g cream cheese (not reduced fat, premium brand strongly recommended)
  • 140 g caster sugar
  • 3 large eggs
  • 15 ml/1 tbsp vanilla essence

Mix all the ingredients together thoroughly, and pour onto the base. Bake in the oven for about an hour. Time needed depends on atmospheric conditions, but when done the top will start to crack. When done, remove from oven and cool on a cooling rack for 30 minutes. (The cooling rack is important, as you need to get airflow underneath the cake).

Top layer

  • 330 ml sour cream
  • 30 g caster sugar
  • 15 ml/1 tbsp vanilla essence

Turn up the oven to 220 °C. Once the bottom layer is cool, mix the top layer ingredients together, and pour on top. Then return to the oven for a further 10 minutes.

Topping

  • 1/2 jar apricot preserve
  • 3-4 fresh apricots

Slice apricots. Heat jam in microwave for about 45 seconds, until runny, and spread over top of cheesecake. Arrange apricots on top.

I'll update this post later with the results!

Update: This worked out really well! The only slight problem was that the tin didn't come away from the sides totally cleanly, but the cake still looked excellent and tasted delicious!

Tuesday, July 06, 2010

Open Source in schools — not an idle fantasy

One of the policies in the Pirate Party UK's general election manifesto this year was:

We will encourage the adoption of open source software in schools, so that children won't be reliant in the future on buying a particular software package from a particular company.

Here in the UK, I still get odd looks when I say I use Linux almost exclusively on my computers. A widely-held perception seems to be that Linux is an esoteric operating system that isn't capable of doing a lot of widely-needed tasks. Certainly many of my friends would never consider running it on their own computers (despite the fact they're almost certain to have at least box running Linux in their house — but I digress).

Open Source in schools is a particularly controversial concept. 'But how will school leavers be able to function in the Real World if they haven't been taught to use the "industry standard" software?' the detractors cry, referring of course to Microsoft Office.

The fact is, though, that Linux has been widely deployed in schools all around the world. The biggest deployment is in Brazil, where the Ministry of Education has installed Linux in labs used by 52 million schoolchildren nationwide — yes, that's fifty-two million — and it's been a great success. Not only does the 'Linux Educacional' distribution, installed in tens of thousands of school computer labs, fulfil the day-to-day needs of school ICT and computer science teaching, but has lead to a growing market for OEM Linux computers in Brazil. And no, their school leavers seem to have no difficulty whatsoever in adapting their IT skills for use in the 'real world' (whatever that is), as Brazil continues to have the strongest IT industry in South America.

Aaron Seigo mentioned this and other (huge!) educational Linux deployments in his keynote speech at this year's Akademy, the KDE developer conference. It seems to me that Linux — not to mention other great Open Source software such as OpenOffice.org, Firefox, Blender, Audacity and Inkscape — have already proven their suitability for use in schools.

Maybe it's time for British schools to step out of the muddy rut of using Microsoft everywhere 'because everybody uses Microsoft', and follow the lead of so many other countries in trying something new, exciting, and in the long run quite possibly both better and cheaper.

Friday, March 12, 2010

Blog migration

Since Blogger are discontinuing FTP and SFTP publishing at the beginning of May, I've now migrated my blog to being hosted by a Blogger "custom domain", http://blog.peter-b.co.uk.

Fortunately, I've been able to use a .htaccess file to add a mod_alias Redirect directive that ensures that old links to http://peter-b.co.uk/blog/ will continue to work. So that makes it a lot less of a hassle!

What was a hassle was figuring out the CSS to disable the Blogger navbar, since it completely destroyed the harmony of my site design. It's hard to believe that it's almost seven years old! I should probably break out the text editor and update it at some point, but after this long I can hardly remember how to use CSS and HTML; I've got a lot of catching up to do.

Banana and walnut cake

A cake recipe that I've had some success with recently is this rather delicious banana and walnut cake. It's dead simple, and takes very little time to make. There's one in the oven right now!

  • 450 g ripe bananas (weighed before peeling), mashed
  • 125 g unsalted butter
  • 150 g caster sugar
  • 2 large eggs
  • Half tsp vanilla extract
  • 50 g walnuts, chopped
  • 250 g self-raising flour
  • Pinch of salt

Pre-heat oven to 180 °C. Lightly butter a 25x10 cm loaf tin. Cream butter and sugar together until smooth and pale.

Add eggs one at a time, beating well. Fold in mashed bananas, vanilla and walnuts. Sift in flour and salt and fold in.

Spoon mixture into loaf tin, and bake for one hour or until a knife pushed into centre of cake comes out dry. Cool in tin for at least 20 min before turning out.

My chocolate brownies have also been popular recently, this time with the University of Surrey Mountaineering Club!

Saturday, February 20, 2010

GTK+ no longer supports Windows, apparently

When writing computer programs, I try to ensure that they are portable enough to run on as many different platforms as possible without modifying the source code. This becomes tricky when I'm writing in C and I want to provide a vaguely-modern-feeling user interface. Since about 2006, I've relied on GTK+, the basis of the GNOME desktop environment, as my GUI library of choice. A good example of a piece of GTK+-based software for which I'm a member of the development team is the gEDA project, a collection of tools for electronics design.

One of the attractions of GTK+ for me has always been its ability to be used on both X Window System-based operating systems (e.g. Linux and BSD) and on Microsoft Windows. Unfortunately, it seems that Windows support has now been discontinued.

Back in September, GTK+ 2.18 was released. Unfortunately, it contained a large regression which has caused some headaches for people working with GTK+ on the Windows platform (essentially, GTK+ applications would be completely unusable in some cases). Furthermore, a rewrite of some core GTK+ code inbetween 2.16 and 2.18 left the GTK+ on Windows infested with a host of other minor but annoying bugs.

Now, what normally happens when an Open Source program upon which literally thousands of applications and millions of users depend has a major stable release containing a large regression on one of the major supported platforms? Well, in most such cases, the software's developers figure out a workaround as quickly as possible and make sure that those affected know about it, and then make haste to track down the source of the bug, fix it, test the fix, and issue a point release or set of patches with which their users can obtain a working version.

Apparently not so in the case of GTK+. Four months later, GTK+ 2.18.x is still pretty much unusable on Windows, and the general consensus is to use 2.16.x. Dominic Lachowicz, a GTK+ developer, has is still warning people not to use 2.18.x on Windows:

Look before you leap. GTK 2.18 on Windows is very buggy.

The attitude of the maintainer of the Windows port, Tor Lillqvist, has been quite alarming. In comments on the GNOME bugtracker, he gave no impression of any intention of resolving the issues himself, saying:

You want ot use some new API present only in 2.18? Please then consider helping in actually debugging and fixing the problems in GTK+ 2.18 on Windows.

... perhaps you should just use the version of software as it was before the "introduction" of the bug? I mean, nobody promised you there would be any updates of Windows-specific functionality, or otherwise, in GTK+, right? So just use GTK+ as it was before "somebody broke it".

It's becoming distressingly clear that there is no-one in the current GTK+ development team with any particular commitment to keeping the Windows support in working order. Furthermore, it seems clear to me that the hostile and confrontational attitude of people like Tor will tend to drive away any new developers interested in taking the work on. It's already hard enough to get patches into GTK+ as it is -- even complete and tested patches tend to hang around in the GNOME bugtracker for weeks or months before being dealt with.

Going forward, I think that I'll need to find an alternative set of libraries that I can use for cross-platform GUI programming and get a well-integrated 'look and feel' with. The Qt toolkit has a good reputation for documentation and support, but doesn't seem to support applications written in C. Are there any other alternatives I've missed?

Monday, February 01, 2010

Project Postcard

I recently wrote a blog posting for the Pirate Party UK website about my latest publicity initiative: Project Postcard!

The election is fast approaching, and the time has come to really press on with raising our profile. All our members need to be doing their part if we're going to make an impact on the UK political landscape. I personally have been aiming to do something meaningful & constructive for the party every day -- and I recommend to you all to make a similar commitment. Even little things can make a real difference.

One way you might be able to help is to get involved with my 'Project Postcard' initiative. I'm shortly going to be ordering a few thousand professionally-produced postcard-like flyers, printed with information on who we are and what we stand for, as well as details of how to find out more.

Read the full article on the PPUK blog.