Latest Trentham batch analysis
CA Manual Update

Adding batch mode stuff
CurveAlign Test Cases

these are test cases for checking to see if CurveAlign is working
properly. There are cases for many of the various modes allowed by the
software. This also will help to guide the directory structure/naming
conventions that are expected.
Batch process update.

Added information about batch processing
comments

added one comment
Output folder name

Changed output folder name
Rearranging and adding comments

Adding comments to files and getting rid of some non-version controlled
names.
updated comments
Comment update

Need to fix issue with odd image size and alt-clicking. Need to get
release done...
Boundary drawing bug

This came up when images were not square. There was a bug where rows and
columns got mixed up in the image size checks. Just tested to make sure
this works well.
Delete project file

This is not needed
V2.2 Release

64bit PC version, requires MCR 7.17 (2012a)
V2.2 Manual Update

Added info about output files, quick start guide, and output images.
Comment change
Remove curvelets at edge of image

Curvelets near the edge of the images can skew angle distributions.
Changed function name to avoid confusion

This function is used to extract information from the CT_Fire output
database. This change was made to avoid confusion with the CT_Fire tool.
Added option for processing fibers from FIRE in different ways

There are now 3 options for processing FIRE fibers with respect to
boundaries:
1. Process all segments as though there were curvelets.
2. Process fibers (only one segment per fiber is considered, average
fiber angle is assigned to all segments, segments locations are used to
find if fiber is near a boundary).
3. Process fiber ends only (similar to above, just use first and last
portion of the fiber that is close enough to the boundary)
added back function header line
Fix boundary association bug

Make sure the proper location on the boundary is used. There was an
indexing problem before, when we throw away some locations.
Still need to identify which position on boundary is best to use when
analyzing fibers. Currently using the first in the list. this should be
more intelligent.
Merge branch 'master' of https://github.com/uw-loci/curvelets