Thursday, 19 July 2012

Survival

It worries me that I wrote an update for this but instead of being published, it was saved, and I didn't notice - even after checking back here several times.

Nonetheless, a brief update of the past two weeks.

Week A represents the week I participated in the iV2012 conference, and overall, I feel it went well. I met with some other members of the Graph Drawing community and discussed some of the problems weve been having and are dealing with at the moment (primarily, designing a structure for dynamic graphs where positions of finer vertices can be used to update coarser vertices in the multilevel structure).

The session itself flopped at the start with no chair turning up. By popular demand (of 2 people) I chaired the session myself (titled Application of Graph Theory) which again went well - I was even thanked afterwards, which although customary, was a confidence boost.

The presentation also went well, with a good response from the audience. Though questions related more to the measuring of aesthetics than the algorithm. No fires, no murders and no horrible hangovers, overall, a good week.

Week B representing this week so far, has so far entailed my return to the technical report which, like everything else I do, has taken forever. Thankfully the conference has given my a little boost to finally finish this piece of work and move on to the bigger problem. Previously, results collected regarding the multi-matching showed a massive increase in runtime with MGF taking almost 4 times as long as the QT - contrary to the single edge contraction implementation.

This has since been fixed and now results are as expected (or not so if the data is correct - which I will explain another time). Unfortunately the edge crossings have now increased to a similar ration (4x) though some results show a decrease to normal levels for matchings of more than 3 vertices. The cause is being investigated.

Week C representing future work: GETTING THIS DONE ASAP! Thats all for now though, see you next time readers.

No comments:

Post a Comment