Some Agenda Items
* - Indicates ones Manchester are prepared to put time in preparing for / implementing.
Relationship with other libraries
Candidates for promotion to VXL. *
mbl_mz_random -> vnl
mbl_priority_bound_queue -> vbl
mbl_lru_cache -> vbl
mbl_cloneable_ptr -> vbl
mbl_gamma -> vnl
mbl_matxvec -> vnl
mbl_matrix_products -> vnl
mbl_chord -> vil or vgl
mbl_thin_plate_spline -> vgl_algo
mbl_index_sort_cmp -> vbl
mbl_stl -> vbl
pdf1d, vpdfl -> vxl/pdf
Get out a release.
This is important from an "encouraging others to use VXL" point of view.
Several people (including as I recall, Bill Hoffman) have complained about the fact that vcl_vector_fixed is non-optimal. A 2 element vector needs 3 elements of storage (1 for n_dims_)
Options include using MTL, TNT, or upgrading VNL.
We would like to retrofit VIL with some of mil's features, e.g.
Merge concepts of planes and channels. (i.e. assert nplanes == 1 || nchannels == 1)
Using pointer arithmetic based addressing in vil_memory_image.
vil_memory_image_impl should know its type at compile time
Addition of standard polymorphic image and world2image transform type. Could be a specialised vcl_pair.
Possiblity of modifying vil to make its interface easily extendable to 3/4/D (with multiple planes)
Is anyone prepared to write some more.e.g. for vcsl and vbl.
The Dart system is great - but it points out that some of our testing coverage is pretty poor.
The current system is difficult for any but the most competent developers. Perhaps some automatic generating scheme might help.