Home > SURF > Timing tests, bugs, commenting, reading

Timing tests, bugs, commenting, reading

July 9th, 2009 Stephen Larew

The timing framework I made yesterday ran last night.  Unfortunately, an oversight of mine led to the program crashing with larger data sets.  I have fixed this now and will run the timing framework again tonight.  Results were at least positive.

As said earlier, the maximum number of grid points is about 95×95.  Currently though, this is not true due to another oversight related to transposing a matrix.  I need to change the current CUDA kernel that transposes the distances matrix so that it transposes the array in-place without a second copy to write to.  This is just slightly tricky due to memory coalescing issues.  I will have this working tomorrow morning hopefully.

The code is fully commented now.

Tomorrow I will begin (and maybe finish?) the code to do space-time scans.

Categories: SURF Tags:
Comments are closed.