Weapon C: because Weapon X was taken...

As mentioned yesterday, my objectives this week have been a bit of a mess, so I have finally decided to put them into a reasonable path;

1. Component data structure for BH and Grid
• Change my previous implementations to use the same data structure for fairer tests
• Can/Should be able to add to Weapon C with own structures but will not be as fair
2. Finish 'Weapon C'
• Plugin functionalities ( whether using Component or own Data Structure )
• Tests ( edge crossings, angles, edge lengths; to be used ubiquitously )
• Projections ( dependant on speed but finding the best viewpoint for said tests ) 
3. Walshaw Convergence
• Old news now, but change from iteration based to convergence based (before default forces found)
• This should be applied so either iteration or convergence can be used
4. Matching/Clumping
• Finish off the clumping/matching I had started
• User defined sizes; find matching with 'n' vertices
• NB: several ways for this, which gives best results? only one way to find out, EXPERIMENTS!
5. Comparison of algorithms
• testing in Weapon C (testing done entirely by application, increasing params without user input)
6. Comparison of optimised CApprox against Yifan Hu's own results

As a side note; I should remember that using random positions initially can alter results, as vertices can be given a better placement in some scenarios. Dependant on the inconsistency of results, using strict initial positions may be better (or worse), we will see.