Archived entries for

Subclipse not working after Sourceforge SVN migration

Today Yesterday we’ve had a really busy day fixing obscure bugs in order to prepare the next release of the Contract core components. What we didn’t know was that the Sourceforge.net SVN migration was scheduled for yesterday. 12 hours of read-only access has been really painful, mainly concerning concurrent development.

However, after the migration finished, I still couldn’t commit the huge amount of changes I had done through the day. In fact, it was giving me the same error as during the whole day:

svn: Commit failed (details follow):
svn: Commit failed (details follow):
svn: MKACTIVITY of ‘/AgentWS/!svn/act/f371347b-0541-0410-8082-ddb3ab739141′: 403 Forbidden (https://ist-contract.svn.sourceforge.net/svnroot/ist-contract)

I even checked with a different SVN client and I could perfectly commit with no problem. Looking for a solution in Google didn’t help very much and I started panicking over the idea of having to check everything out in a separate project (or workspace) and remake all the changes. My sources in Eclipse didn’t even get updated with the changes I had made with the SVN client.

But then, the miracle. After checking out in a blank workspace, I switched back to the faulty one to start checking which files were changed. I don’t know exactly why, but I tried updating a project… and it worked!!!

Don’t ask me how and why these things happen, or if it’s even something only related to Subclipse. I am too tired right now to think on a logical conclusion. Probably it has to do with the host certificate or something like that but, in any case, these things can really spoil a mood in case of bad luck or a solution misleading. Anyway, software developing wouldn’t be so interesting without this kind of nonsense problems, would it?

Just kidding.

The intelligent i-Walker

In the same office we work at, we have the SHARE-it guys. The main purpose of this project is to design and implement AI systems that help people with disabilities, as the acronym indicates: Supported Human Autonomy for Recovery and Enhancement of cognitive and motor abilities using Information Technologies.

This definition, as always, seems quite abstract, but they are already showing stuff that will be really useful. The underlying IA system will allow for the creation of intelligent software and hardware to assist disabled people, specially elders.

SHARE-it IA infrastructure

One of these devices is the i-Walker, an intelligent walker that is location-aware, and assists the patient in moving, for example, through a house or a hospital. The user can interact with an interface plugged into the walker using verbal commands, and its levels of autonomy can be adjusted for a better experience. The same concepts will be applied to a wheelchair.

Other devices that will be built on top of the IA system include an RFID bracelet which collects information about the movements made and the objects around the user. With this information, a PDA will be able to act as a personal agenda, predicting the needs of the user and the recommended actions to take (e.g. it’s time to take the pills).

This running project not only looks good from the research perspective but also seems to have real useful application. In fact, along with one of its leaders, Ulisés Cortés, SHARE-it has started to have a deserved media exposure.



Copyright © 2004–2009. All rights reserved.

RSS Feed. This blog is proudly powered by Wordpress and uses Modern Clix, a theme by Rodrigo Galindez.